Date: Mon, 16 Jan 2012 14:50:38 -0500 (EST) From: khatfield@socllc.net To: "Chris Buechler" <cbuechler@gmail.com> Cc: freebsd-isp@freebsd.org, up@3.am Subject: Re: Suddenly IP aliases don't work from rc file? Message-ID: <1326743438.72677849@apps.rackspace.com> In-Reply-To: <CAOmxWMVQ5VWSCgisX=wP23yZQuE-hhu1w8_X89o1n-XBxLYHuA@mail.gmail.com> References: <fa682ba7a64b504ed493468612a27ba9.squirrel@ssl.pil.net> <CAOmxWMVQ5VWSCgisX=wP23yZQuE-hhu1w8_X89o1n-XBxLYHuA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I think I missed Chris' response prior to replying to this but I agree as i= t could have just been an ARP issue but if it fails on reboot then that sho= ws it's something else.=0A=0AAssigning 255.255.255.255 would assume each IP= is assigned to the primary IP. However, the subnet for the primary is a /2= 3 subnet. Either the company you're renting from has horrible methods of ma= naging the way IP's are issued or it's incorrect in itself.=0A=0AI would ve= rify all of the information is indeed what they have set upstream. If it is= , I cannot fathom the amount of arp spam your box is getting anyway.=0A=0AA= lso with Chris' statement: RealTek is generic enough that works and it work= s on just about anything. However, they offer no real tuning or much suppor= t community-wise when it comes to getting the best throughput or even troub= leshooting. The idea is that it should 'just work'. My personal opinion is = if they have an Intel card lying around, ask them to stick an Intel (1000) = card in there and at least you guarantee no driver issues and really the be= st out-of-the-box performance.=0A=0AOf course, that would be the last resor= t as you're wanting to simply fix the problem right now. However, if all of= the above fails - change the card. You would be surprised when it comes to= tons of trash traffic how some cards can be flakey or cause the system's C= PU's to actually do more work than would be required with a higher-end NIC.= =0A=0A-----Original Message-----=0AFrom: "Chris Buechler" <cbuechler@gmail.= com>=0ASent: Sunday, January 15, 2012 7:36pm=0ATo: up@3.am=0ACc: freebsd-is= p@freebsd.org=0ASubject: Re: Suddenly IP aliases don't work from rc file?= =0A=0AOn Sun, Jan 15, 2012 at 7:00 PM, <up@3.am> wrote:=0A> A dedicated se= rver that I rent has a primary IP and 6 alias IPs. =C2=A0Everything was=0A>= working ok with the rc.conf configured like this:=0A>=0A> ifconfig_rl0=3D"= inet primary.ip.address netmask 255.255.254.0"=0A>=0A> The primary IP above= comes up fine. =C2=A0I then have:=0A>=0A> ifconfig_rl0_alias0=3D"inet seco= nd.ip.addr netmask 255.255.255.255"=0A> ifconfig_rl0_alias1=3D"inet third.i= p.addr netmask 255.255.255.255"=0A>=0A> and so on. =C2=A0This worked fine u= ntil we had an Ethernet card go bad. =C2=A0It was=0A> replaced and I had to= use a different driver, but none of the alias IPs worked.=0A> They showed = up in ifconfig, but they couldn't be reached from outside the=0A> localhost= . =C2=A0So, I had them put in an identical Realtek s before, change the dri= ver=0A> back as above but the problem persisted.=0A>=0A> I tried moving the= ifconfig lines from the end of the rc file to near the=0A> beginning, righ= t after the main IP ifconfig, but still no go after rebooting each=0A> time= . =C2=A0I messed around with this for a while and finally just removed the = alias=0A> IPs using the manual "ifconfig rl0 second.ip.addr netmask 255.255= .255.255 -alias"=0A> and re-adding it the same way. =C2=A0That got those IP= s working again.=0A>=0A> The only thing I can think of is that this server = does have an onboard Attansic=0A> Ether that the GENERIC kernel sees...we a= ctually used it yesterday after the first=0A> Realtek died and it worked fi= ne for a while, then would just crap out=0A> intermittently. =C2=A0We went = back to Realtek and that fixed the connection crappiness,=0A> but that's wh= en the alias problems began...all I had done was change the driver=0A> lett= ers. =C2=A0One thing that makes me wonder about the other Ether is that "ne= tstat=0A> -rn showed "link#2" for the alias IPs. =C2=A0However, it still sh= ows that after=0A> deleting and re-adding them, which fixed it.=0A>=0A> Any= ideas? =C2=A0It's working now but any kind of reboot is going to cause hav= oc.=0A=0AAre you sure it's the reboot that causes havoc? Sounds like you ma= y=0Ahave been fighting an ARP cache upstream that either timed out or got= =0Aupdated in the process of mucking around with the IPs. I also wouldn't= =0Atouch a server with Realtek NICs in it, probably the worst NIC=0Ahardwar= e ever built.=0A_______________________________________________=0Afreebsd-i= sp@freebsd.org mailing list=0Ahttp://lists.freebsd.org/mailman/listinfo/fre= ebsd-isp=0ATo unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebs= d.org"=0A=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1326743438.72677849>