Hello,
at the end, posting in misc, I've found out that the problem with iwn hanging is very common, at least with the 5100 nic. I solved it with a script that brings the nic down and up every time it detects there's no connection. Hopefully it will be solved for 4.6 (I don't think I'm very fit to run -current).
Now the problem with trunk0:
actually I posted this already but in a thread with another title, so I think it's better to repeat it here, since it's a problem only with trunk.
The problem is, wireless works just fine, and if I plug in the ethernet cable trunk switches to it, but it has no connection.
What could the reason be?
Here are my settings:
Code:
$ cat hostname.em0
up
Code:
$ cat hostname.iwn0
up chan 6 nwid mylan wpa wpapsk mykey
Code:
$ cat hostname.trunk0
trunkproto failover trunkport em0 trunkport iwn0 192.168.1.102 netmask 255.255.255.0
ifconfig wireless:
Code:
$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33204
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr macaddress
priority: 0
trunk: trunkdev trunk0
media: Ethernet autoselect (none)
status: no carrier
inet6 fe80::21f:16ff:fe1f:dae3%em0 prefixlen 64 scopeid 0x1
iwn0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr macaddress
priority: 0
trunk: trunkdev trunk0
groups: wlan
media: IEEE802.11 autoselect (OFDM12 mode 11g)
status: active
ieee80211: nwid mylan chan 6 bssid macaddress 240dB wpapsk <not displayed> wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip
inet6 fe80::222:faff:fef5:62fa%iwn0 prefixlen 64 scopeid 0x2
enc0: flags=0<> mtu 1536
priority: 0
trunk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr macaddress
priority: 0
trunk: trunkproto failover
trunkport iwn0 active
trunkport em0 master
groups: trunk egress
media: Ethernet autoselect
status: active
inet 192.168.1.102 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::21f:16ff:fe1f:dae3%trunk0 prefixlen 64 scopeid 0x5
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33204
priority: 0
groups: pflog
Code:
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.159 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=5.205 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.170 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.157 ms
with ethernet plugged in:
Code:
$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33204
priority: 0
groups: lo
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr macaddress
priority: 0
trunk: trunkdev trunk0
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet6 fe80::21f:16ff:fe1f:dae3%em0 prefixlen 64 scopeid 0x1
iwn0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr macaddress
priority: 0
trunk: trunkdev trunk0
groups: wlan
media: IEEE802.11 autoselect (OFDM18 mode 11g)
status: active
ieee80211: nwid mylan chan 6 bssid macaddress 240dB wpapsk <not displayed> wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip
inet6 fe80::222:faff:fef5:62fa%iwn0 prefixlen 64 scopeid 0x2
enc0: flags=0<> mtu 1536
priority: 0
trunk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr macaddress
priority: 0
trunk: trunkproto failover
trunkport iwn0
trunkport em0 master,active
groups: trunk egress
media: Ethernet autoselect
status: active
inet 192.168.1.102 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::21f:16ff:fe1f:dae3%trunk0 prefixlen 64 scopeid 0x5
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33204
priority: 0
groups: pflog
Code:
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Code:
$ ping -v -c 1 -w 1 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
--- 192.168.1.1 ping statistics ---
1 packets transmitted, 0 packets received, 100.0% packet loss
very puzzled
