Short description of what actions I did on client that maps to entries
in attached file tcp_dump_host:
00:33:38, ifconfig ral0 up
00:33:41, dhclient ral0
00:37:09, ifconfig trunk0 trunkproto failover trunkport fxp0 trunkport ral0
subsequent ping to 192.168.0.1 gave the same error as described in my
first mail.
pre trunk:
# ifconfig -M ral0
ral0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:13:f7:2a:f4:ab
media: IEEE802.11 OFDM54 mode 11g hostap (autoselect mode 11g
hostap)
status: active
ieee80211: nwid himmet_wlan chan 11 bssid 00:13:f7:2a:f4:ab 100dBm
lladdr 00:13:f7:1e:a7:86 114dB 54M cache
inet6 fe80::213:f7ff:fe2a:f4ab%ral0 prefixlen 64 scopeid 0x1
inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
post trunk:
# ifconfig -M ral0
ral0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:13:f7:2a:f4:ab
media: IEEE802.11 OFDM54 mode 11g hostap (autoselect mode 11g
hostap)
status: active
ieee80211: nwid himmet_wlan chan 11 bssid 00:13:f7:2a:f4:ab 100dBm
lladdr 00:02:a5:b8:71:b5 115dB 54M cache
lladdr 00:13:f7:1e:a7:86 113dB 54M short_preamble assoc
inet6 fe80::213:f7ff:fe2a:f4ab%ral0 prefixlen 64 scopeid 0x1
inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
Second lladdr looking good. But still it won't work.
Then I tried this
# ifconfig fxp0 delete
# ifconfig ral0 delete
as suggested by Simon Westphahl and I can now ping 192.168.0.1 but ping
192.168.1.1 give same error as before. However, the tcp_dump at the host
now got interesting (attached file tcp_dump_host_2). Unfortunately, I'm
not sure what to do with it :/
/Markus
Reyk Floeter wrote:
> On Tue, Nov 07, 2006 at 11:50:16PM +0100, Markus Bergkvist wrote:
>> Reyk Floeter wrote:
>>> the trunk will use the mac address of it's primary trunkport, which is
>>> fxp0 in your case. as soon as you add ral0 to the trunk it will also
>>> use the trunk mac address (00:02:a5:b8:71:b5 from fxp0) for ethernet
>>> and 802.11 traffic. this should trigger a new authentication and
>>> association to the accesspoint using the new mac address.
>> I noticed that at some point too. Good to know that is the correct
>> behaviour.
>>
>>> if you use anything like mac address filters on your ap, please
>>> whitelist fxp0's address and try it again.
>>>
>> Nope, no address filtering on the ap.
>
> hmmm, interesting. can you monitor the auth/assoc state on the ap?
> for example, if your ap is an openbsd box, you can use ifconfig -M to
> list the client nodes and tcpdump -y ieee802_11_radio to monitor the
> wireless traffic.
>
> reyk
00:33:38.638059 802.11: probe request, <radiotap v0, chan 11, 11g, signal 105dB>
00:33:38.638108 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:33:40.655754 802.11: probe request, <radiotap v0, chan 11, 11g, signal 116dB>
00:33:40.655794 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:33:40.755738 802.11: probe request, <radiotap v0, chan 11, 11g, signal 117dB>
00:33:40.755763 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:33:40.785510 802.11: probe request, <radiotap v0, chan 11, 11g, signal 116dB>
00:33:40.785533 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:33:40.893294 802.11: probe request, <radiotap v0, chan 11, 11g, signal 114dB>
00:33:40.893319 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:33:40.905866 802.11: probe request, <radiotap v0, chan 11, 11g, signal 114dB>
00:33:40.905890 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:33:40.982252 802.11: probe request, <radiotap v0, chan 11, 11g, signal 114dB>
00:33:40.982276 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:33:41.106428 802.11: authentication request, <radiotap v0, chan 11, 11g,
signal 114dB>
00:33:41.106453 802.11: authentication response, <radiotap v0, chan 11, 11g>
00:33:41.107283 802.11: authentication request, <radiotap v0, chan 11, 11g,
signal 114dB>
00:33:41.373264 802.11: association request, <radiotap v0, chan 11, 11g, signal
114dB>
00:33:41.373299 802.11: association response, <radiotap v0, chan 11, 11g>
00:34:08.535801 802.11: data: truncated-ip - 234 bytes
missing!192.168.1.32.bootpc > 255.255.255.255.bootps: xid:0x73789c77 ether
0:13:f7:1e:a7:86 [|bootp] [tos 0x10], <radiotap v0, chan 11, 11g, signal 113dB>
00:34:08.535853 802.11: data: truncated-ip - 234 bytes
missing!192.168.1.32.bootpc > 255.255.255.255.bootps: xid:0x73789c77 ether
0:13:f7:1e:a7:86 [|bootp] [tos 0x10], <radiotap v0, chan 11, 11g>
00:34:08.539915 802.11: data: truncated-ip - 234 bytes
missing!192.168.1.1.bootps > 192.168.1.32.bootpc: xid:0x10c9d52 secs:6
Y:192.168.1.32 S:192.168.1.1 ether 0:13:f7:1e:a7:86 [|bootp] [tos 0x10],
<radiotap v0, chan 11, 11g>
00:34:08.541859 802.11: data: truncated-ip - 234 bytes
missing!192.168.1.1.bootps > 192.168.1.32.bootpc: xid:0x73789c77 Y:192.168.1.32
S:192.168.1.1 ether 0:13:f7:1e:a7:86 [|bootp] [tos 0x10], <radiotap v0, chan
11, 11g>
00:34:08.577397 802.11: data: arp who-has 192.168.1.32 tell 192.168.1.32
(0:13:f7:1e:a7:86), <radiotap v0, chan 11, 11g, signal 113dB>
00:34:08.577425 802.11: data: arp who-has 192.168.1.32 tell 192.168.1.32
(0:13:f7:1e:a7:86), <radiotap v0, chan 11, 11g>
00:37:09.079479 802.11: probe request, <radiotap v0, chan 11, 11g, signal 114dB>
00:37:09.079527 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:37:09.090046 802.11: probe request, <radiotap v0, chan 11, 11g, signal 114dB>
00:37:09.090069 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:37:11.814167 802.11: probe request, <radiotap v0, chan 11, 11g, signal 115dB>
00:37:11.814207 802.11: probe response, ssid (himmet_wlan), rates, ds, tim,
erp, xrates, <radiotap v0, chan 11, 11g>
00:37:54.184294 802.11: authentication request, <radiotap v0, chan 11, 11g,
signal 117dB>
00:37:54.184319 802.11: authentication response, <radiotap v0, chan 11, 11g>
00:37:54.549011 802.11: authentication request, <radiotap v0, chan 11, 11g,
signal 117dB>
00:37:54.693868 802.11: association request, <radiotap v0, chan 11, 11g, signal
115dB>
00:37:54.693906 802.11: association response, <radiotap v0, chan 11, 11g>
00:48:13.540021 802.11: data: 192.168.0.35 > ungoliant.himmet: icmp: echo
request, <radiotap v0, chan 11, 11g, signal 116dB>
00:48:14.541675 802.11: data: 192.168.0.35 > ungoliant.himmet: icmp: echo
request, <radiotap v0, chan 11, 11g, signal 117dB>
00:48:15.551697 802.11: data: 192.168.0.35 > ungoliant.himmet: icmp: echo
request, <radiotap v0, chan 11, 11g, signal 116dB>
00:48:29.108782 802.11: data: 192.168.0.35 > ungoliant.himmet: icmp: echo
request, <radiotap v0, chan 11, 11g, signal 117dB>
00:48:30.112564 802.11: data: 192.168.0.35 > ungoliant.himmet: icmp: echo
request, <radiotap v0, chan 11, 11g, signal 116dB>
