ath0 pain on visiting network

From: Randy Bush (randy_at_psg.com)
Date: 10/24/05

Next message: FreeBSD Tinderbox: "[head tinderbox] failure on amd64/amd64"

Previous message: Doug Poland: "Re: Regression in device ath between BETA5 and RC1?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Sun, 23 Oct 2005 15:05:08 -0700
To: FreeBSD Current <freebsd-current@freebsd.org>

current of today on thinkpad t41

this puppy is stable at home on 11G talking to a kinksys wrt54gs

it was stable yesterday at a starschmucks

here i am at nanog talking to a cisco 1200

# ifconfig ath0
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.35.165.22 netmask 0xfffffc00 broadcast 192.35.167.255
        ether 00:05:4e:48:ce:66
        media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/18Mbps)
        status: associated
        ssid nanog-arin channel 40 bssid 00:12:d9:81:64:40
        authmode OPEN privacy OFF txpowmax 28 bintval 100

wpa turned off, dhclient on

64 bytes from 147.28.0.39: icmp_seq=1814 ttl=54 time=66.783 ms
64 bytes from 147.28.0.39: icmp_seq=1815 ttl=54 time=66.028 ms
64 bytes from 147.28.0.39: icmp_seq=1816 ttl=54 time=66.838 ms
64 bytes from 147.28.0.39: icmp_seq=1817 ttl=54 time=64.952 ms
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
64 bytes from 147.28.0.39: icmp_seq=1824 ttl=54 time=71.564 ms
64 bytes from 147.28.0.39: icmp_seq=1825 ttl=54 time=66.459 ms
64 bytes from 147.28.0.39: icmp_seq=1826 ttl=54 time=64.684 ms
64 bytes from 147.28.0.39: icmp_seq=1854 ttl=54 time=179.757 ms
64 bytes from 147.28.0.39: icmp_seq=1855 ttl=54 time=64.828 ms
64 bytes from 147.28.0.39: icmp_seq=1856 ttl=54 time=64.832 ms
64 bytes from 147.28.0.39: icmp_seq=1857 ttl=54 time=64.619 ms
64 bytes from 147.28.0.39: icmp_seq=1858 ttl=54 time=65.722 ms
64 bytes from 147.28.0.39: icmp_seq=1859 ttl=54 time=65.102 ms
64 bytes from 147.28.0.39: icmp_seq=1860 ttl=54 time=64.681 ms
64 bytes from 147.28.0.39: icmp_seq=1861 ttl=54 time=74.158 ms
64 bytes from 147.28.0.39: icmp_seq=1862 ttl=54 time=73.650 ms
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
64 bytes from 147.28.0.39: icmp_seq=1868 ttl=54 time=72.364 ms
64 bytes from 147.28.0.39: icmp_seq=1869 ttl=54 time=74.804 ms
64 bytes from 147.28.0.39: icmp_seq=1870 ttl=54 time=64.819 ms
64 bytes from 147.28.0.39: icmp_seq=1871 ttl=54 time=64.824 ms
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
64 bytes from 147.28.0.39: icmp_seq=1878 ttl=54 time=73.062 ms

forever

when down, it looks like

# ifconfig ath0
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:05:4e:48:ce:66
        media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/6Mbps)
        status: no carrier
        ssid nanog-arin channel 40
        authmode OPEN privacy OFF txpowmax 28 bintval 100

kill dhclient and it looks like

64 bytes from 147.28.0.39: icmp_seq=8 ttl=54 time=65.202 ms
64 bytes from 147.28.0.39: icmp_seq=9 ttl=54 time=71.260 ms
64 bytes from 147.28.0.39: icmp_seq=10 ttl=54 time=71.252 ms
64 bytes from 147.28.0.39: icmp_seq=11 ttl=54 time=64.790 ms
64 bytes from 147.28.0.39: icmp_seq=12 ttl=54 time=64.702 ms
64 bytes from 147.28.0.39: icmp_seq=13 ttl=54 time=65.214 ms
64 bytes from 147.28.0.39: icmp_seq=14 ttl=54 time=67.787 ms
64 bytes from 147.28.0.39: icmp_seq=16 ttl=54 time=4563.685 ms
64 bytes from 147.28.0.39: icmp_seq=17 ttl=54 time=3565.347 ms
64 bytes from 147.28.0.39: icmp_seq=18 ttl=54 time=2587.202 ms
64 bytes from 147.28.0.39: icmp_seq=19 ttl=54 time=1609.266 ms
64 bytes from 147.28.0.39: icmp_seq=20 ttl=54 time=524.803 ms
64 bytes from 147.28.0.39: icmp_seq=21 ttl=54 time=64.635 ms
64 bytes from 147.28.0.39: icmp_seq=22 ttl=54 time=64.708 ms
64 bytes from 147.28.0.39: icmp_seq=23 ttl=54 time=65.819 ms
64 bytes from 147.28.0.39: icmp_seq=24 ttl=54 time=65.554 ms
64 bytes from 147.28.0.39: icmp_seq=25 ttl=54 time=64.597 ms
64 bytes from 147.28.0.39: icmp_seq=26 ttl=54 time=64.661 ms
64 bytes from 147.28.0.39: icmp_seq=29 ttl=54 time=79.498 ms
64 bytes from 147.28.0.39: icmp_seq=31 ttl=54 time=4568.477 ms
64 bytes from 147.28.0.39: icmp_seq=32 ttl=54 time=3568.110 ms
64 bytes from 147.28.0.39: icmp_seq=33 ttl=54 time=2575.396 ms

until it loses the lease, of course :-)

randy

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

Next message: FreeBSD Tinderbox: "[head tinderbox] failure on amd64/amd64"

Previous message: Doug Poland: "Re: Regression in device ath between BETA5 and RC1?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

cant ssh back into 10.242; host seen as Down
... PING 10.242: 56 data bytes ... ping: sendto: Host is down ... 10 packets transmitted, 0 packets received, 100% packet loss ...
(freebsd-questions)
Re: wireless help
... PING 192.168.1.254: 56 data bytes ... ping: sendto: Host is down ... packets transmitted, 0 packets received, 100% packet loss ...
(freebsd-questions)
wi0 not there on FreeBSD 4.9 w/ Netgear MA401RA
... ping any other machines on my LAN. ... ping: sendto: No route to host ...
(comp.unix.bsd.freebsd.misc)
Routing problem
... I am running a 5.4 box as a gateway server / firewall / mail relay at ... Example of a ping to another 5.4 box connected directly to one of the ... ping: sendto: No route to host ...
(freebsd-questions)
Wireless NIC in FreeBSD 6.0 ?
... Back to FreeBSD 5.4, my wireless card just works, but not in FreeBSD 6.0. ... but when i try to ping some IP which definitely should be connected ... ping: send to: No route to host ...
(freebsd-questions)