[ietf83-tech] Can't reach routers from ietf-hotel network

Bjoern A. Zeeb bzeeb-lists at lists.zabbadoz.net
Tue Mar 27 22:52:57 PDT 2012


On Wed, 28 Mar 2012, Bill Fenner wrote:

> One of the failure modes that I've consistently experienced through
> the week has returned this morning:
>
>
> dhcp-6704% ping -c 10 130.129.64.1
> PING 130.129.64.1 (130.129.64.1): 56 data bytes
>
> --- 130.129.64.1 ping statistics ---
> 10 packets transmitted, 0 packets received, 100% packet loss
> dhcp-6704% ping -c 10 130.129.64.2
> PING 130.129.64.2 (130.129.64.2): 56 data bytes
>
> --- 130.129.64.2 ping statistics ---
> 10 packets transmitted, 0 packets received, 100% packet loss
> dhcp-6704% ping -c 10 130.129.64.3
> PING 130.129.64.3 (130.129.64.3): 56 data bytes
>
> --- 130.129.64.3 ping statistics ---
> 10 packets transmitted, 0 packets received, 100% packet loss
>
>
> I switched to the Concorde wireless and went through the portal and am
> getting *great* network.
>
> netdisco tells me that I am on 10.215.6.56, which is attached to
> 10.215.7.219 port 15 (sadly, that last bit I had to drag out of the
> database, since netdisco's device view requires symmetrical CDP to
> display where an AP is attached and the APs don't do CDP).  I thought
> maybe the switch's MAC address table was full, or something, but the
> vlan 2 fdb is way smaller than the vlan 1 fdb.  I don't really have
> any other brilliant ideas...

It is interesting that this is also seen with hotel APs, which is a
clue as well.  I am not sure how different this is from my IPv6
experiences given I had seen packets coming to me on the monitor port
on the last switch...

-- 
Bjoern A. Zeeb                                 You have to have visions!
          Stop bit received. Insert coin for new address family.


More information about the ietf83-tech mailing list