Date: Sun, 15 Jan 2012 19:36:49 -0500 From: Chris Buechler <cbuechler@gmail.com> To: up@3.am Cc: freebsd-isp@freebsd.org Subject: Re: Suddenly IP aliases don't work from rc file? Message-ID: <CAOmxWMVQ5VWSCgisX=wP23yZQuE-hhu1w8_X89o1n-XBxLYHuA@mail.gmail.com> In-Reply-To: <fa682ba7a64b504ed493468612a27ba9.squirrel@ssl.pil.net> References: <fa682ba7a64b504ed493468612a27ba9.squirrel@ssl.pil.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 15, 2012 at 7:00 PM, <up@3.am> wrote: > A dedicated server that I rent has a primary IP and 6 alias IPs. =A0Every= thing was > working ok with the rc.conf configured like this: > > ifconfig_rl0=3D"inet primary.ip.address netmask 255.255.254.0" > > The primary IP above comes up fine. =A0I then have: > > ifconfig_rl0_alias0=3D"inet second.ip.addr netmask 255.255.255.255" > ifconfig_rl0_alias1=3D"inet third.ip.addr netmask 255.255.255.255" > > and so on. =A0This worked fine until we had an Ethernet card go bad. =A0I= t was > replaced and I had to use a different driver, but none of the alias IPs w= orked. > They showed up in ifconfig, but they couldn't be reached from outside the > localhost. =A0So, I had them put in an identical Realtek s before, change= the driver > back as above but the problem persisted. > > I tried moving the ifconfig lines from the end of the rc file to near the > beginning, right after the main IP ifconfig, but still no go after reboot= ing each > time. =A0I messed around with this for a while and finally just removed t= he alias > IPs using the manual "ifconfig rl0 second.ip.addr netmask 255.255.255.255= -alias" > and re-adding it the same way. =A0That got those IPs working again. > > The only thing I can think of is that this server does have an onboard At= tansic > Ether that the GENERIC kernel sees...we actually used it yesterday after = the first > Realtek died and it worked fine for a while, then would just crap out > intermittently. =A0We went back to Realtek and that fixed the connection = crappiness, > but that's when the alias problems began...all I had done was change the = driver > letters. =A0One thing that makes me wonder about the other Ether is that = "netstat > -rn showed "link#2" for the alias IPs. =A0However, it still shows that af= ter > deleting and re-adding them, which fixed it. > > Any ideas? =A0It's working now but any kind of reboot is going to cause h= avoc. Are you sure it's the reboot that causes havoc? Sounds like you may have been fighting an ARP cache upstream that either timed out or got updated in the process of mucking around with the IPs. I also wouldn't touch a server with Realtek NICs in it, probably the worst NIC hardware ever built.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOmxWMVQ5VWSCgisX=wP23yZQuE-hhu1w8_X89o1n-XBxLYHuA>