Date: Mon, 16 Jan 2012 01:08:09 +0000 From: khatfield@socllc.net To: up@3.am, owner-freebsd-isp@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Suddenly IP aliases don't work from rc file? Message-ID: <201882339-1326676090-cardhu_decombobulator_blackberry.rim.net-2038766906-@b1.c15.bise6.blackberry> 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
Are the alias IP's as part of the same subnet? For example, in one subnet? It's a little concerning your primary subnet mask is of a /23. Are you actually assigning all 512 IP's to one server or set / vlan? It is likely there is a gateway issue. The other alternative is the routes were missing. Based on what you're listing in the example, you have 512 IP's assigned to this one singular system primary IP? I'd double check the gateways and the netmasks. If a reboot breaks again after those are verified, send us a netstat -nr with some more detail. Not sure this is the exact forum for this question but you're welcome to email me directly and I can try to assist. I am not representative of the FreeBSD team however I do have a lot of experience with it / extensive use. Otherwise, maybe someone else can provide a more probable answer. (Also ensure you have rl and re compiled in the kernel - it's possible you may still have a driver issue) Best of luck! -----Original Message----- From: up@3.am Sender: owner-freebsd-isp@freebsd.org Date: Sun, 15 Jan 2012 19:00:35 To: <freebsd-isp@freebsd.org> Subject: Suddenly IP aliases don't work from rc file? A dedicated server that I rent has a primary IP and 6 alias IPs. Everything was working ok with the rc.conf configured like this: ifconfig_rl0="inet primary.ip.address netmask 255.255.254.0" The primary IP above comes up fine. I then have: ifconfig_rl0_alias0="inet second.ip.addr netmask 255.255.255.255" ifconfig_rl0_alias1="inet third.ip.addr netmask 255.255.255.255" and so on. This worked fine until we had an Ethernet card go bad. It was replaced and I had to use a different driver, but none of the alias IPs worked. They showed up in ifconfig, but they couldn't be reached from outside the localhost. So, 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 rebooting each time. I messed around with this for a while and finally just removed the alias IPs using the manual "ifconfig rl0 second.ip.addr netmask 255.255.255.255 -alias" and re-adding it the same way. That got those IPs working again. The only thing I can think of is that this server does have an onboard Attansic 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. We 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. One thing that makes me wonder about the other Ether is that "netstat -rn showed "link#2" for the alias IPs. However, it still shows that after deleting and re-adding them, which fixed it. Any ideas? It's working now but any kind of reboot is going to cause havoc. _______________________________________________ freebsd-isp@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-isp To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201882339-1326676090-cardhu_decombobulator_blackberry.rim.net-2038766906->