Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Aug 2001 11:44:37 -0500 (CDT)
From:      Alex Charalabidis <alex@wnm.net>
To:        Marius Kirschner <marius@agoron.com>
Cc:        Gabriel Ambuehl <gabriel_ambuehl@buz.ch>, <questions@FreeBSD.ORG>
Subject:   RE: Host unable to  ping/access its own IPs
Message-ID:  <20010817114220.S37120-100000@earth.wnm.net>
In-Reply-To: <NEBBKGPPOLDBPJPLMKDIMEFCGHAA.marius@agoron.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Aug 2001, Marius Kirschner wrote:

> I have the same problem with a FreeBSD box.  I can access/ping the IP/domain
> from anywhere but the box that is hosting it.  I've been pulling my hair for
> over a week now trying to figure out what's going on.  Strangely it only
> affects one IP while all others are working just fine.
>

Try setting the netmask for the problem address to 0xffffffff since it's
not the primary one on the interface.

-ac

-- 
===================================================================
Alex Charalabidis                           Worldspice Technologies
5050 Poplar Ave.         Memphis, TN, USA           +1 901 432 6000
Opinions expressed are mine alone but may be yours for a small fee.
===================================================================


> >
> > Hello questions,
> > I've there got a REALLY strange problem with one of my servers:
> > rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >         inet XXX.YY.62.126 netmask 0xfffffff8 broadcast 195.49.62.127
> >         inet6 fe80::200:e8ff:feec:aaa8%rl0 prefixlen 64 scopeid 0x1
> >         inet XXX.YY.33.19 netmask 0xffffff80 broadcast 195.49.33.127
> >         inet XXX.YY.62.125 netmask 0xfffffff8 broadcast 195.49.62.127
> >         inet XXX.YY.33.29 netmask 0xffffff80 broadcast 195.49.33.127
> >         ether 00:00:e8:ec:aa:a8
> >         media: Ethernet autoselect (100baseTX <full-duplex>)
> >         status: active
> > lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
> > faith0: flags=8000<MULTICAST> mtu 1500
> > gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
> > gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
> > gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
> > gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
> > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
> >         inet6 ::1 prefixlen 128
> >         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
> >         inet 127.0.0.1 netmask 0xff000000
> > ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
> > sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
> >
> >
> > Now from localhost, I can ping .126 and .19 but not .125 or .29:
> >
> > root@gamma 18:20:40 ~/scripts # ping XXX.YY.62.126
> > PING 1XXX.YY.62.126 (XXX.YY.62.126): 56 data bytes
> > 64 bytes from XXX.YY.62.126: icmp_seq=0 ttl=64 time=0.089 ms
> > 64 bytes from XXX.YY.62.126: icmp_seq=1 ttl=64 time=0.055 ms
> >
> > root@gamma 18:23:01 ~/scripts # ping XXX.YY.33.29
> > PING XXX.YY.62.125 (XXX.YY.33.29): 56 data bytes
> > ping: sendto: Host is down
> > ping: sendto: Host is down
> >
> > (the same goes for the other two IPs).
> >
> > Now a host on the same switch is able to ping all FOUR IPs:
> > root@alpha 18:25:01 ~ $  ping XXX.YY.33.29
> > PING XXX.YY.33.29 (XXX.YY.33.29): 56 data bytes
> > 64 bytes from XXX.YY.33.29: icmp_seq=0 ttl=64 time=0.358 ms
> > 64 bytes from XXX.YY.33.29: icmp_seq=1 ttl=64 time=0.178 ms
> > 64 bytes from XXX.YY.33.29: icmp_seq=2 ttl=64 time=0.171 ms
> >
> >
> > This machine is running on FreeBSD  4.3-STABLE FreeBSD 4.3-STABLE
> > #13:
> > Tue Jul 10 21:59:49 CEST 2001     root@gamma:/mnt/a/obj/usr/src/sys/
> >




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010817114220.S37120-100000>