# ifconfig ath0 down # ifcondig ath0 up ksh: ifcondig: not found # ifconfig ath0 up # dhclient ath0 ath0: DHCPREQUEST to 255.255.255.255 ath0: DHCPACK from 192.168.0.1 (00:00:24:cd:c6:01) ath0: bound to 192.168.0.22 -- renewal in 21600 seconds # ping 18.104.22.168 PING 22.214.171.124 (126.96.36.199): 56 data bytes 64 bytes from 188.8.131.52: icmp_seq=0 ttl=60 time=130.032 ms 64 bytes from 184.108.40.206: icmp_seq=1 ttl=60 time=163.518 ms ^C --- 220.127.116.11 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 130.032/146.775/163.518/16.743 ms # dmesg | grep ath0* mpath0 at root scsibus0 at mpath0: 256 targets ath0 at pci2 dev 0 function 0 "Atheros AR5212" rev 0x01: apic 1 int 17 ath0: AR5424 10.3 phy 6.1 rf5424 10.2 eeprom 5.3, WOR2W, address 00:19:7e:43:c6:6b
On Sun, Apr 15, 2018 at 11:12 PM, Z Ero <zerotetrat...@gmail.com> wrote: > Amd64. Fat fingers... > > On Sun, Apr 15, 2018 at 11:10 PM, Z Ero <zerotetrat...@gmail.com> wrote: >> Hello, >> >> I experience an intermittent issue with my Atheros wifi card or the >> OpenBSD driver for it on 6.2. >> >> What happens is that it seems to drop out of the network ocassionally. >> I am sitting in the same room as the access point so it can't be a >> signal problem. >> >> I have found that bringing the interface down and them back up and >> renewing the DHCP lease seems to solve the problem. >> >> Also, OpenBSD does not seem to realize the problem is solved until I >> test the link with a ping. >> >> E.g even after the interface is toggled on/off and the lease is >> renewed firefox will still be waiting for a page to load until I ping. >> >> That seems strange. >> >> I wonder if it is a hardware / thermal problem with the card. The area >> the card is in in my machine is pretty hot. >> >> This is a pretty minor issue and I could try another wifi card sometime... >> >> I am just wondering if anyone has any insight into other possible causes. >> >> Thanks.