[Rack] Monkeybrains link seems to be dead.
Andy Isaacson
adi at hexapodia.org
Sun Jun 20 21:21:00 UTC 2010
> > > As far as monkeybrains goes just power cycled both gorilla and the AP,
> > > no fix. I'd debug this more right now but don't have time.
> >
> > I've asked MB if they know what's up; I'll swing by tomorrow to try and
> > debug from our end. (First question is, has anybody checked the
> > antenna?)
Monkeybrains saw a bit of packet loss last night at 1:40, but the
link is up. I checked the radio on the roof; it is present, correctly
installed and aligned, does not seem to have been modified / stolen /
hacked, and has both ethernet and wifi link lights. Their smokeping
is green, but we still can't pass traffic.
from gorilla I see the following:
gorilla:/root>netstat -rn
uRouting tables
Internet:
Destination Gateway Flags Refs Use Mtu Prio Iface
default 192.168.188.1 UGS 0 8560 - 8 sis1
172.30.0/22 link#1 UC 5 0 - 4 sis0
192.168.188/24 link#2 UC 1 0 - 4 sis1
192.168.188.1 00:15:6d:e5:ba:fa UHLc 2 47 - 4 sis1
gorilla:/root>ping 192.168.188.1
PING 192.168.188.1 (192.168.188.1): 56 data bytes
64 bytes from 192.168.188.1: icmp_seq=0 ttl=64 time=2.510 ms
64 bytes from 192.168.188.1: icmp_seq=1 ttl=64 time=1.188 ms
--- 192.168.188.1 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.188/1.849/2.510/0.661 ms
gorilla:/root>traceroute 4.2.2.2
traceroute to 4.2.2.2 (4.2.2.2), 64 hops max, 40 byte packets
1 192.168.188.1 (192.168.188.1) 1.891 ms 1.691 ms 1.363 ms
2 192.168.188.1 (192.168.188.1) 3002.150 ms !H 3002.216 ms !H 3002.33 ms !H
gorilla:/root>ifconfig sis1
sis1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:00:24:c0:fd:49
priority: 0
groups: egress
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::200:24ff:fec0:fd49%sis1 prefixlen 64 scopeid 0x2
inet 192.168.188.138 netmask 0xffffff00 broadcast 192.168.188.255
gorilla:/root>arp -an | grep 192
? (192.168.188.1) at 00:15:6d:e5:ba:fa on sis1
That looks to me like it's working correctly and the VLAN is working and
we are getting packets across the wifi link, so I'll forward this info
to MB to verify their end of the config is right.
If someone could verify the VLAN config and check the MACs to make sure
I'm not getting fooled by a too-smart switch, I'd appreciate it.
-andy
More information about the Rack
mailing list