View Single Post
Old 17th May 2008
JMJ_coder JMJ_coder is offline
VPN Cryptographer
 
Join Date: May 2008
Posts: 464
Default

Hello,

Quote:
Originally Posted by anomie View Post
Ok. I don't know what to suggest. Sounds like you've perhaps diagnosed the issue, though.
O.K., I got it working. Here is what I added to my rc.conf:

Code:
IP=`ifconfig nfe0 | grep -E 'inet.[0-9]' | awk '{print $2}'`
if [ "$IP" = "192.168.1.64" ]; then
        ifconfig nfe0 inet 192.168.1.63 netmask 255.255.0.0
fi
ifconfig nfe0 inet 192.168.1.64 netmask 255.255.0.0
I found out that you can't assign an alias with the same IP address as the one the interface currently has, so I had to check to see if it was the same and if it was, change it (it was going to change anyway) to set the alias properly. Alias is set and all is peachy keen.

Only two side effects of this -

1) for that half-minute to minute while the modem is finishing up all its loose ends, you can't reach the internet (big deal!).
2) when it runs through the if statement and assigns 192.168.1.63 and 192.168.1.64 becomes the alias - when the IP address if finally set, it makes 192.168.1.64 the IP address and the address from DHCP becomes the alias. I don't know why, but it still works the same.



I am still getting the dhclient error, but I have no clue as to why. I guess I just have to redirect the error message someplace else.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14)
Reply With Quote