Posted 17 August 2012 - 13:08
And from that sniff I don't see 1 packet from anything other than that machine itself. So your bridge is clearly not sending anything.
Did you set the box to static 2.101 for a bit of time? This seems out of place with all the other 169.254 and dhcp requests
92 12:43:30 PM 8/16/2012 301.1296240 192.168.2.101 192.168.2.255 NbtNs NbtNs:Query Request for BRW00225878B66E Workstation Service {UDP:12, IPv4:11}
Unless the browser service still thought its IP address was that? What machine is BRW00225878B66E
And this sure looks like an arp from your router asking for 2.100 (bridge box)
114 12:46:41 PM 8/16/2012 492.4190621 192.168.2.1 192.168.2.100 ARP ARP:Request, 192.168.2.1 asks for 192.168.2.100
Other than that strange arp, I don't see anything from any other machine - so bridge clearly not sending packets down the wire. That sniff does not show mac addresses -- can you change it to that. That is much easier to rad what came from where, etc.
Did you set your wireless card to forcecompatmode=enable ? Do you have other devices connect to your router network? If so you should of seen lots of broadcast traffic. See how your box was sending out requests for WPAD and SSDP (UPnP) And announcing
UPSTAIRS 169.254.255.255 BROWSER BROWSER:Domain/Workgroup Announcement, MachineGroup = WORKGROUP, serverName = UPSTAIRS {SMB:3, UDP:2, IPv4:1}
94 12:43:37 PM 8/16/2012 308.0699348 System UPSTAIRS 169.254.255.255 BROWSER BROWSER:Local Master Announcement, ServerName = UPSTAIRS {SMB:3, UDP:2, IPv4:1}
You should of seen those from your bridge box at least.