On Thu, Jun 06, 2013 at 07:09:05PM -0400, gpon...@spamcop.net wrote: > 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.
Mixing dhcp and aliases is not supported in 5.3 as we search for a consistant and reliable way to accomplish it. dhclient will always remove all addresses present on the interface when applying the lease. .... Ken > 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 73.70.192.1 (00:01:5c:33:0e:01) > bound to 98.207.205.23 -- 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 > em2: > flags=28b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6> > rdomain 1 mtu 1500 > lladdr 00:24:81:7f:ee:0b > priority: 0 > media: Ethernet autoselect (1000baseT full-duplex,master) > status: active > inet 192.168.100.2 netmask 0xffffff00 broadcast 192.168.100.255 > /etc >> > > 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 ? > > GP
