Subject: Re: ifconfig alias routing problems...
To: Herb Peyerl <firstname.lastname@example.org>
From: Jan-Hinrich Fessel <email@example.com>
Date: 10/19/1995 13:08:19
In message <199510171936.NAA21669@sidney.novatel.ca>you write:
> Peter Seebach <firstname.lastname@example.org> wrote:
> > I have an interface (le0) configured as 188.8.131.52. I then
> > ifconfig le0 alias 184.108.40.206
> > ...This seems fine. I can't ping the address .9, but
> I've noticed this with a machine I have serving N web-domains. It can't
> see any of its aliases even though the rest of the world can.
I can get through just fine, thoug that maybe because my router knows me:
zappa# ifconfig ed0
inet 220.127.116.11 netmask 0xfffffff8 broadcast 18.104.22.168
zappa# ping -c 1 22.214.171.124
PING 126.96.36.199 (188.8.131.52): 56 data bytes
64 bytes from 184.108.40.206: icmp_seq=0 ttl=254 time=4.357 ms
--- 220.127.116.11 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 4.357/4.357/4.357 ms
zappa# traceroute 18.104.22.168
traceroute to 22.214.171.124 (126.96.36.199), 30 hops max, 40 byte packets
1 un-net.unna.ping.de (188.8.131.52) 3.734 ms 2.606 ms 2.513 ms
2 oskar.isdn.xxxxx.de (184.108.40.206) 3.961 ms 3.691 ms 3.65 ms
> > route add 220.127.116.11 localhost
> > fixes that.
> That seems like the wrong answer... I suspect you'd get all kinds of
> weirdness happening as a result of that.
This should be the right answer, at least as long as the routing is stupid
eough not being able to figure out localhost routes for itself, i.e. there is
a "route add <ipaddress> localhost" in any of the system startup files...
Tragbar ist, was nicht herunterfaellt.