Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Mar 1998 16:19:06 -0800
From:      brian@worldcontrol.com
To:        freebsd-current@FreeBSD.ORG
Subject:   machine no longer appears via its primary ethernet interface
Message-ID:  <19980309161906.A372@top.worldcontrol.com>

next in thread | raw e-mail | index | archive | help
I have a P5-90 running -current from Mar 8th.  Every other
day or so its stops responding to its .161 address, but will respond
to others.  It's been acting this way for a month or so.

Its de0 interface is setup as:

de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet xxx.yyy.zzz.161 netmask 0xffffffc0 broadcast xxx.yyy.zzz.191
        inet xxx.yyy.zzz.162 netmask 0xffffffff broadcast xxx.yyy.zzz.162
        inet xxx.yyy.zzz.163 netmask 0xffffffff broadcast xxx.yyy.zzz.163
        inet xxx.yyy.zzz.164 netmask 0xffffffff broadcast xxx.yyy.zzz.164
        inet xxx.yyy.zzz.165 netmask 0xffffffff broadcast xxx.yyy.zzz.165
        inet xxx.yyy.zzz.166 netmask 0xffffffff broadcast xxx.yyy.zzz.166
        ether 00:80:c8:2b:db:08 
        media: 10baseT/UTP status: active
        supported media: autoselect 10base5/AUI manual 10baseT/UTP <full-duplex> 10baseT/UTP

It is setup that way via

ifconfig_de0="inet xxx.yyy.zzz.161 netmask 255.255.255.192 media 10baseT/UTP"
in /etc/sysconfig

and 
/sbin/ifconfig de0 alias xxx.yyy.zzz.162 netmask 255.255.255.255
/sbin/ifconfig de0 alias xxx.yyy.zzz.163 netmask 255.255.255.255
/sbin/ifconfig de0 alias xxx.yyy.zzz.164 netmask 255.255.255.255
/sbin/ifconfig de0 alias xxx.yyy.zzz.165 netmask 255.255.255.255
/sbin/ifconfig de0 alias xxx.yyy.zzz.166 netmask 255.255.255.255

in /etc/rc.local


It is primarily used by via its .161 address.   Sometimes it
disappears (no longer responds to its .161 address).

For example:  (I am out on the general internet)

brian@top> ping xxx.yyy.zzz.161
[ping just sits there, and will do so for as long as I have waited]

In another window issue the command:

brian@top>ping -c 1 xxx.yyy.zzz.163 
PING xxx.yyy.zzz.163 (xxx.yyy.zzz.163): 56 data bytes
64 bytes from xxx.yyy.zzz.163: icmp_seq=0 ttl=242 time=3888.267 ms

--- xxx.yyy.zzz.163 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3888.267/3888.267/3888.267/0.000 ms

Then immediately the first ping begins to respond:
(note that 65 packet have previously been lost)

brian@top>ping xxx.yyy.zzz.161
PING xxx.yyy.zzz.161 (xxx.yyy.zzz.161): 56 data bytes
64 bytes from xxx.yyy.zzz.161: icmp_seq=66 ttl=242 time=4573.434 ms
64 bytes from xxx.yyy.zzz.161: icmp_seq=67 ttl=242 time=3602.600 ms
64 bytes from xxx.yyy.zzz.161: icmp_seq=68 ttl=242 time=4383.136 ms
64 bytes from xxx.yyy.zzz.161: icmp_seq=69 ttl=242 time=4273.397 ms
64 bytes from xxx.yyy.zzz.161: icmp_seq=70 ttl=242 time=3293.190 ms
64 bytes from xxx.yyy.zzz.161: icmp_seq=71 ttl=242 time=2333.278 ms
64 bytes from xxx.yyy.zzz.161: icmp_seq=72 ttl=242 time=1344.112 ms
64 bytes from xxx.yyy.zzz.161: icmp_seq=73 ttl=242 time=343.187 ms
...

When it is in this "odd" state it does not respond via .161 to machines
on the same LAN either.

It has fallen into this behavior at least once every two days for
the past few weeks.

The machine is connected to a Cisco switch of some sort.  I think it
said Cisco 2000.  It is the only machine connected into the providers
network via the Cisco 2000, so I worry the problem may be related
to the switch.

Any ideas?

I'm going to ask the provider to connect me before the switch to
eliminate that as a possible cause.

--
Brian Litzinger <brian@litzinger.com>

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



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