On the console, change the appropriate interface IP to your chosen range using the menu.

Ja, ja, ja! (laughing in Spanish) Sorry I'm a noob on the way to becoming a Guru.

Thanks mhab, but I was looking for an easier way to shutdown. I have a on/off switch on my modem. Thanks dotdash, sounds like a great idea.

@ktims: Script looks good to me, my only suggestion is that you add a couple seconds delay between setting the interface down and back up. I know the Intel hardware is well-behaved here, but I've seen other cards where the PHY doesn't reset properly or at all (link maintained) if you bring the state back up too soon. Updated script.  Good call.  That might save me on a couple of clients where I scraped together a firewall with crappy NICs.

No.

Ah now i get it ^^" Updated the wiki to include the link perry posted :)

Oooppps, sorry, I just figured it out, I forgot to change the traffic shaping download value(2mbps to 5mbps). Just very  recently, my ISP upgraded my 2mbps connection to 5mbps.

Just seen this happen again on my Net5501 box, seems to be once a month here Martin

Thank you  :) I must backup every log files every days. I don't want to let it truncate log file before backup.

I've used a USB ethernet adapter for my WAN link for some time and it seems to work OK. The adapter is USB 1 (max speed of 12Mbps). Since my broadband link never seems to report higher speeds than 6Mbps download and 1Mbps upload I doubt the USB speed limitation is ever a problem.

I got it! I had to configure it for PPPoE not DHCP. Now it is working great!

Please use the search function.  This question has been asked and answered several times already.

Load balancing works for me like a miracle but I really can't make failover work. When I try to remove 1 / 3 of my WANs sometimes I still can access the Internet sometimes I can't. What could be wrong? I set up monitor IPs correctly, I'm pretty sure. I have three modems from the same ISP and I use my ISP's DNS servers for monitor IPs for all the three modems, they are different from each other.

T3 timeouts are usually an indication of ingress or noise on the return path on Comcast's plant. The ingress also can be in your house as well as your neighbors. Some T3 timeouts are normal, but you have many. I would advise a tech visit. Do you experience packet loss as well?? Normal upstream S/N is 28db or better and minimum 32 or better for Downstream C/N. You can ping Comcast's CMTS(if responds to pings) overnight and see if you have sporadic pings or packet loss.

I've also noticed something weird…if i set the server to use dhcp for one of the ip's it allows me to connect to it from the wifi subnet, if i don't it wont.. What's weirder still is that lets say i set static dhcp to give ip 192.168.1.14 to the server and then manually set 192.168.1.15 and 192.168.1.16 as alias ips I can connect to those ip's no problem, but as soon as i set the server to manually connect via normal static ip none of the ip's work from the wifi subnet (which is 192.168.2.0/24) i'm totally stumped...i've put allow rules for all on both lan and wifi under wifi i have wifinet * * * * lannet * * * * under lan i have the same....what do i need to do to make this work.