Router issues...

[AntiVirus]

 /cheers

[Joe]

Oh. That's cheating. :P

[Sidoh]

iago, have you considered putting dd-wrt on your router?  There's a feature that allows you to do scheduled reboots.

[iago]

Yeah, I've considered it. But I don't like running unofficial software like that in a production-type environment. My biggest concern is that dd-wrt has all kinds of vulnerabilities found on a regular basis.

That being said, it might be a good option. Buying a better router might be a better option. :)

[MyndFyre]

I'm getting ready to offer to host it on the same server where jinxbot.net lives.  Geez.

I think you missed the part where I'm out of town. It's hard to fix something like a broken router without physical access.

Bad luck happens. You'll get over it! :)

I knew you were out of town.  But since the site always happens to go offline whenever you're out of town, I thought you might be amicable to hosting it somewhere that's not dependent on your hardware.

[iago]

I'm getting ready to offer to host it on the same server where jinxbot.net lives.  Geez.

I think you missed the part where I'm out of town. It's hard to fix something like a broken router without physical access.

Bad luck happens. You'll get over it! :)

I knew you were out of town.  But since the site always happens to go offline whenever you're out of town, I thought you might be amicable to hosting it somewhere that's not dependent on your hardware.

Well, it's just bad luck. We'll see what happens next time I go away (I'm half considering going to DC in February.. dunno if that'll actually happen :) ).

[Camel]

My non-54g WRT has reboot.

Then again, it has DD-WRT on it, too.

[Joe]

When you restructure your Virtual Machines, I'd recommend (on no educational basis) using the host operating system for two functions: A router, and a VM host. That way, next time something bad happens, SSH into the host machine, issue a "reboot now", and then cleverly written boot scripts restart all your VMs and whatnot.

Opinion?

[Sidoh]

Yeah, I've considered it. But I don't like running unofficial software like that in a production-type environment. My biggest concern is that dd-wrt has all kinds of vulnerabilities found on a regular basis.

That being said, it might be a good option. Buying a better router might be a better option. :)

Do something so it doesn't die when you go out of town.  I think the forums are doing poorly enough as it is. :P

[Armin]

I can't imagine x86 on a server not run by iago.

[iago]

When you restructure your Virtual Machines, I'd recommend (on no educational basis) using the host operating system for two functions: A router, and a VM host. That way, next time something bad happens, SSH into the host machine, issue a "reboot now", and then cleverly written boot scripts restart all your VMs and whatnot.

Opinion?

I used to do that. The problem is, my current connection is PPPoE, and drops pretty regularly. My Linksys router is pretty good at re-establishing the connection quickly, Linux might not be so good. My friend used to use Linux for PPPoE, and he got a lot of nasty crashes.

[Sidoh]

whatever it is, it needs fixing.  FIX IT.

how do I recommend you do that?  it's a simple, three step plam:

1) FIX IT
2) FIX IT
and finally, 3) FIX IT.

[Lead]

whatever it is, it needs fixing.  FIX IT.

how do I recommend you do that?  it's a simple, three step plam:

1) FIX IT
2) FIX IT
and finally, 3) FIX IT.

You forgot 4) ????? and 5) Profit.

[Blaze]

whatever it is, it needs fixing.  FIX IT.

how do I recommend you do that?  it's a simple, three step plam:

1) FIX IT
2) FIX IT
and finally, 3) FIX IT.

I have a simple 1 step plan:

1) Succeed.

If you follow the plan, you're golden.

[Camel]

My Linksys router is pretty good at re-establishing the connection quickly, Linux might not be so good. My friend used to use Linux for PPPoE, and he got a lot of nasty crashes.

WRT-54G is Linux, so that's a pretty bad argument :)

When I lived in the Fraternity house, I set up a Gentoo box to serve as a gateway/NATing router. Before we spent the money on the dedicated machine, I tried several different flavors of firmware for WRT-54G (we got three of these so we could get WiFi almost everywhere in the house), and none of them could scale to the ~50 computers on the network. They simply didn't have enough ram to persist that many connections.

We also bought two 20-something-port 100MBit/2-port gigabit switches, which we planted in the attic. It took about a month for me and one other person to finish wiring every room (2 singles, 14 doubles, 2 triples). It's been 4 years, and the system only gone down once in that entire time, due to the power going out.

In going with this solution, I realized how crippled these little boxes really are. As switches, they are fine, but the minute you start relying on a limited-RAM machine to perform NAT, you're pretty screwed. Aside from the obvious benefit of not having to reboot the WRTs six times a day, the internet-bound latency dropped significantly, and WiFi connections stopped dropping.