Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
Date: Thu Jun 06 2013 - 18:09:05 CDT
I recently updated from 5.2 to 5.3 and one ethernet port got broken.
The port connected to a cable modem and was configured for DHCP. With
5.3, the DHCP assigned address is getting lost when I add an alias.
The alias and a route table addition give the LAN a way to communicate
with the modem's web interface which is fixed at 192.168.100.1. My
hostname.em2 contents are:
dhcp rdomain 1
alias 192.168.100.2 255.255.255.0
!route -T 1 add 192.168.100.0/24 192.168.100.2
I also have a DSL modem on em1 with fixed IP that should not be
affected by the DHCP response, so my implementation used a separate
routing table for the two WAN ports.
/etc >> sh /etc/netstart em2
DHCPREQUEST on em2 to 255.255.255.255 port 67
DHCPACK from 18.104.22.168 (00:01:5c:33:0e:01)
bound to 22.214.171.124 -- renewal in 5572 seconds.
route: writing to routing socket: File exists
add net 192.168.100.0/24: gateway 192.168.100.2: File exists
/etc >> ifconfig em2
rdomain 1 mtu 1500
media: Ethernet autoselect (1000baseT full-duplex,master)
inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255
I would have expect to see two inet lines, one with the DHCP assigned
address and another with the alias. As it is, the LAN can't get to the
cable modem and the LAN can't route through the DHCP-assigned gateway.
Removing the alias solves the routing problem but not the cable modem
management access. Any thoughts or suggestions for how to fix this, or
an alternate solution ?