And then it all went tits up…

So it was all going fine then just after midnight the wireless connection was grinding to a halt. Looked at the box and for an embedded kernel it seemed to be doing an awful lot of disk writing. So after a reboot it was now dead and wouldn’t restart, failing to mount the root file system. By the look of something there was some corruption and it fried.

So, there I was until 4AM burning blasted CD’s with pfSense on and trying to find a CDROM drive that wouldn’t fail while reading them. Every time I got pfSense up and running again though and restored the backup it would fry. The backup was taken from the developer version though. So in the end I just had to leave it.

This morning I decided to take the XLS of the old backup and merge it with a new XLS backup, thankfully this worked and saved me reconfiguring the whole thing again from scratch.

It was until a few minutes ago very stable and stayed up for around 14 hours, then just now it kernel panicked and rebooted. I was playing around with netbios type stuff at the time though so may be that’s a clue. My windows netbook is still having an issue doing the name resolve so I think there still may be a firewall problem to solve, but I can access the share using the IP address no problem.

In other news I spent the day on AAC codec’s and got it to decode and work fine, I’m now working on the encoder bit.

Went to the gym and did two home checks for Hollyhedge. I’m now fairly knackered so still no wine, but I’m going to call it a night.

Well, it’s now live…..and crashing

So I took the plunge and unhooked the old Draytek and put the cable into the pfSense LAN port. It’s reset itself multiple times, this may be because I’ve been running the latest developer version, so I’ve gone back to the last ‘stable’ release. So far, so good. Also got the remote logging to work, so it’s now sending all it’s log stuff back to the servers syslog and into it’s own nice little log file.

I also found an RS232 (yes they are still used) extension cable, so connected the UPS to the server and configured NUT. It appears to be working, but I haven’t tried a power down test yet. Need to configure that and may be get it to send a mail with the power outage.

Work wise, well, did a bit on the mobile game, then it was back to Apple Lossless. Apart from a major tidy up of the file handling libs (for MP4), it’s all working. Next job is to add in ALC which uses yet another library, when that’s done I can strip down finally all the bloaty file libs.

Right, now it must be time for salad (going for a wine free week again….)

pfSense, well you had a break

Ok, so this morning woke up early, decided that wasn’t a good way to start the day so went back to sleep. Got up later, had breakfast, drank espresso then took the dog for a two and a half hour walk. Came back, mowed the lawn, hung the washing out. Had lunch (boiled eggs on Sunday) then spent 3 hours digging out the hedge. Which is now finished, just needs some serious raking before I can seed it. So that’s a job well done.

Then retired to my lair… dug out the netbook and connected it to the service port. Added all the Wan1 inbound rules, doesn’t appear to have caused any problems. Then added the gateways for the load balancing. Decided to connect the Wan2 port to the existing local lan, this is on the same subnet as the new lan local lan subnet. To cut a very long firewall log short, it wasn’t happy. So dug through my junk box and found a long network cable. I then connected the Virgin router directly to Wan2 and behold load balancing actually appeared to start working. The final straw to resolve was accessing the web interfaces of the two routers, the Virgin router played ball straight away and I could access it’s web page. The Draytek on the other hand is not being quite so nice, I’ve found a bit of a tutorial on how to solve it, but part way through testing it I managed to kill all connectivity, so decided to call it a night.

Jamie is off ‘fapping’ to blue people. Time for me to drink a nice glass of white and have a bath. I think I’ll have the new pfSense thing all running by the end of the week.

It’s all about tea

Well, makes a change from pfSense I guess. Only breifly twiddled with that today to sort out a problem with Courier SSL certificates. Spent the bulk of the day working on these damn m4a files for Apple Lossless. Got a bit of a breakthrough, in now I actually have one that plays. Even managed to add the metadata to it, so it has a track name. Don’t think there’s too many more problems to go on it, so hopefully wrap it up soon.

Went off to the gym and did BodyPump, also did 40 minutes of running. I’m now breaking my no wine rule, by, well, having some wine. But hey, I’ve managed over 1200 calories today in exercise. So now it’s wine o’clock and bath time.

Here’s a little something Jamie found on an old backup. It was recorded for one of his podcasts about five years ok. It’s me ranting about my Mothers tea making skills. (Warning, contains a terrible Bristolian accent and bad language).

TeaBags

pfsense – well almost there

So finally getting there. I gave up on trying to get it to work with public facing IP’s on the server. So reconfigured the server to use port forwarding with a couple of IP’s from the local subnet. Got this working with a few fixups on postfix, courier and amavis. Then used my old Draytek to port forward. All worked fine provided you are outside the local then. Inside you get lots of nat reflection problems. Rather than piss about I decided just to move over to the pfSense box.

So, deleted the old bridges and created one bridge which contained the FLAN (fixed lan), WLAN and DMZ. After loads of rule fiddling I finally got the whole thing to work. Same problem with nat reflection, but thankfully pfSense has a couple of options to get round that, so after more fiddling it now all works inside and outside the local lan.

So now it’s up and running with the old Draytek running on the Virgin line and running my main lan and pfSense running on the pfSense box running my server. So at the moment they arn’t linked. Next step is to add more firewall rules to the incoming lan (the Virgin one can all be blocked). Then add the second wan to the pfSense box and do all the routing for load balancing. So, all a bit of a mess, but I think it’s finally getting there.

Went to the gym and ran far too much.

pfSense – when is a bridge not a bridge

Started the day with far too many postman and couriers turning up. Why can’t Jamie get his arse out of bed for once. My new sunglasses turned up anyway, they look cool. Lost another pound in weight, that’s 10 pounds now, keep it up for the holiday.

Been working on mobile game which made a nice change, finished the bulk of it by lunchtime, so moved back to the M4A codec thing. I’ve managed to produce an M4A file, it just doesn’t play, but the binary is close, so I guess it’s getting there. And avoided most conversations about anti-aliasing.

So started back on pfSense again. Got the new ethernet modem out. That actually had a later firmware on than available on the support site, which makes a change. Modem worked fine, unlike pfSense.

Spent a couple of hours buggering about with it, managed to get normal routing to work eventually. Couldn’t get a peep out of the server though. Went to gym, ran lots. Came back and gave it another couple of hours. By the look of it, bridges confuse it. Especially if you have the same interface bridged twice. In the end I couldn’t get DHCP on the server or anything. I think what I’ll have to do is delete it all down and start again one step at a time from scratch, with multiple reboots in between. Anyway, it’ll keep me busy and off the wine for a few more evenings I’m sure.

And now I’m dreaming about pfSense firewall rules…

Spent most of the day trying to write out an m4a file, which is more problematic than it first seemed. M4A/MP4 is one of those lovely encapsulation formats designed by the mpeg people. Which means is very complex, over engineered but very flexible.

Ended up using a massive lib that supports stuff like album cover art. I’ll get it all to work first then strip all the crap out. Tomorrow I’ve got some work on another mobile project to do.

Walked the dog, fed the dog, which is considerably more than Jamie ever manages.

Decided to play with pfSense again before I went to the gym. I now have (hopefully) all the firewall rules set up, plus all the gateways and the load balancing stuff. Reset the DHCP server and now ready for some live testing I guess. Next step is to set up the Draytek on PPoE and see what works (probably not much). By the time I finished piddling about I left late for the gym, so only did half an hour, but still got out the house.

Again a wine free evening, but I did have some cake.

And oh yes, last night I did dream about firewall rules, sad isn’t it.

pfSense – yet again

So today was mainly taken up with scaling GUI’s, not the most exciting thing in the world. I did eventually move back on to my codec’s and now got the m4a Apple Lossless codec working on PC.

Went to the gym and did combat. The guy behind me looked like he’d been in a swimming pool by the end of it. I’d hardly broken into a sweat, which means I’m either extremely fit or I’m just not trying hard enough.

Then moved back to pfSense. What I wanted to test was connecting the server to the DMZ and then the WAN (well local LAN) to WAN1. Therefore hoping that the two routed public IP’s would go across my bridge. To cut a long story short I couldn’t see anything from my public IP’s on the firewall logs until I rebooted the server. Then magically it all started working. I need to do a few more tests to make sure all rules are working correct and broadcast traffic isn’t going to the WAN.

No wine tonight, just lots of tea.

pfSense – round 67 (Or that’s what it feels like)

So the day started well, I took the woof for a two hour walk. Weather started out miserable but I started sweating buckets as the sun finally decided to show it’s face. It defo wasn’t woolly hat weather.

Got back and did the garden poo run, emptied the kitchen compost and refilled the bird table. I then preceded to have the standard Sunday lunch of two boiled eggs, while I read the paper.

Then it was time to venture out to the front garden again. I’m slowly trying to clear a hedge. Slowly being the operative word. I had a tree stump in my path and three hours later it was finally out.

Then on to the next job….pfSense firewall. Well this one’s been on going for a while. So after the strange firewall error from last time I decided to reinstall from scratch. First thing I did was set up one of the spare NIC’s as a backup emergency access for when I inevitably locked my self out of the web config. This time I set up all the bridged lans as ‘none’ and then created the bridge and assigned that to LAN. After some playing with the server firewall it all actually started working. So I’ll leave it there for this evening. Next job is to create a proper set of firewall rules.

And now bath time (I’m already on the wine, but digging was hard work), then I’m going to watch the Olympics closing ceremony.

You need to go at my ass like your mining gold

Now I receive some odd text messages, but that one is quite strange. I suppose it’s also technically wrong as you pan for gold and mining is more for coal. Although ‘you need to go at my ass like your mining for coal’ probably doesn’t have the same ring to it.

Work wise, spent the morning on m4a (mp4) codec again, this time added the missing alac support (Apple Lossless), so now go to the stage where it can be passed to the decoder. Then got dragged off to look at some PS3 stuff. Ended up looking at an odd font problem, which turns out that scaling whole pixels by odd numbers is never really a good idea.

Car still holding together which is good. And what the fuck is the weather doing? I’m stuck in a room surrounded by computers and a PS3 that keeps over heating. Never mind I’m sure it will be back to rain soon enough.