Slack drops 'route' after reboot. Manual config required - but why?
Here is my situation:
My Slackware 10.1 box has been 'fat and happy' for the past 200 days or so. I changed the network it was on from 192.168.1.x to 192.168.50.x, thus the default gateway changed from 192.168.1.1 to 192.168.50.1. I thought I had it figured out by changing the IP address on the NIC with "ifconfig" and then using 'route': route delete default route add default gw 192.168.50.1 eth0 Everything works well until a reboot (every 200 days or so) when it fails to connect to the public. I can get into it from my LAN, but from outside my network it is unreachable until I execute the 'route' commands as listed above. Is this a problem with slack or is there a .conf file I need to put the new information in? |
quite possibly. put it in /etc/rc.d/rc.inet1.conf (after all the eth0, eth1, etc. there's an entry for gateway). sometimes i have to restart rc.inet1 a couple times for it to take effect.
|
All times are GMT -5. The time now is 12:58 AM. |