AccessFromWAN being ignored by OBI202??

<< < (2/2)

Shale:
When using Wireshark, you will need to have each device that you want to watch connected to a hub that is not a switch. http://wiki.wireshark.org/HubReference Don't be surprised to pay more for a dumb hub than for a smarter switch.

I bought a used Netgear 104 for that purpose.

xzaphod:
Thank you. The layer 2 network hub is a possible solution on a wired network and would work well if all your devices are reasonably co-located. I've used this solution before.

Another solution on a wired network is to bridge layer 3 traffic from all the ports on a VLAN (including the WLAN) onto a single port where your Wireshark computer is plugged in. Of course, you have to have a router that can do this link aggregation without suffering bandwidth overload.

My network is wireless and the OBI202 problem occurred when my router's WiFi configurationwas set to broadcast two different SSIDs; the problem seems purely related to WiFi so I need to see the network packets on the wireless side. Wireshark partners to offer a solution. Please see the URL http://www.riverbed.com/products-solutions/products/performance-management/wireshark-enhancement-products/Wireless-Traffic-Packet-Capture.html This nifty capability is a WiFi USB dongle (not unlike OBI's WiFi dongle) operating in promiscuous mode and software for your Windows box. The two combine to sniff the air for all WiFi traffic the dongle's antenna can grab. All the packets are aggregated onto the USB port and delivered to Wireshark or other capture & analysis software. [Note, one could do something similar with a Bluetooth dongle and appropriate software that understood Bluetooth packets.]

The Wireshark/Riverbed solution comes in three flavors. The more upscale flavors include the ability to inject packets into the WiFi etherverse. You'd want (need!) a pretty fast computer to determine what to inject and to create and inject the packets fast enough to make a difference. I'd be happy with the $200 packet capture device. I had a wired network packet capture & injection capability many years ago. It can be quite interesting to watch, or alter, the traffic on a network.

Full disclosure: I neither have connection to Wireshark or Riverbed nor am I advocating any nefarious activity. The capability exists to help solve problems.

I still don't understand why having my router's WiFi radio broadcasting two SSIDs on the same MAC is confusing the OBI202 when none of my other devices seemed to have a problem. I wonder if it's a bug in the OBI202 support for WiFi via OBI's USB dongle?

Navigation

[0] Message Index

[*] Previous page