Date: Thu, 9 Aug 2001 14:56:40 +0100 (BST) From: Darkcyde <jk@dac.org> To: freebsd-isp@freebsd.org Subject: Re: (OT) Re: another ip as alias on NIC doesn't work properly [read, heed, and hopefully kill this thread] Message-ID: <Pine.BSF.4.21.0108091441470.56764-100000@phoenix.shells.co.uk> In-Reply-To: <20010807184317.Q1013@marius.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 7 Aug 2001, Marius Strom wrote: > Can this thread be clobbered until we get some realistic troubleshooting > information here? I think 99.9% of people on this list do agree that > ethernet address aliasing does work on FreeBSD, and let's leave it at > that. I saw this thread appear and die a couple of months back but didn't jump in as I thought alexus had managed to sort his stuff out, yet it's getting painful now. Personally running several boxes with single NICs w/ multiple IPs it's frustrating to see this thread go on and on.. We all know it works, heh. Binding to aliased interfaces is also a non-issue and has been working in various ircii and derived source trees for moons, just the syntax for using them is a little different. (some use environment variables such as IRCHOST and/or command line switches..) bleh I think the obvious answer is that FreeBSD is /NOT/ broken and neither are the clients. As for proving it.. A simple bit of netcat [/usr/ports/net/netcat] will prove out the client as either being broken or working. ie; on some random box, nc -vlp 6667.. leave running in another terminal/whatever on the box with the "problem" - BitchX -H 1.2.3.4 nick otherbox.com [note that I'm fairly sure that if you specify a hostname with BitchX and the dns lookup fails, it will fallback to the default interface as opposed to not connecting at all. Try with the IP first, if that works then check your forward dns..] Anyway, sit back after smacking return on the client box and observe the originating IP address seen on stderr on the listening netcat. If it's coming from the default interface then there may be a problem with the aliased address. I've seen all sorts of "try this netmask, try that netmask". I'm sure most people will agree that the way of doing things usually is simply with an all-255's netmask in an ifconfig_de0_alias0=... type entry. If you want to do this on the fly; ifconfig de0 inet 1.2.3.4 netmask 255.255.255.255 alias up Should do the trick. (Please hold fire on the deprecated 'up', I'm being lazy..) Also, I would traceroute/ping your aliased addresses from outside the network some and make sure that you can actually reach them from elsewhere, otherwise this entire exercise has been pointless throughout.. HTH and all that bidniz. Regards, J. -- Darkcyde (jk@dac.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0108091441470.56764-100000>