connecting to access point
Page 1 of 1

Author:  amitko [ Thu Jun 20, 2013 8:21 pm ]
Post subject:  connecting to access point


My pc has a wireless network adapter that is connected to an AP which connects to the router.
for some reason i cannot connect a router from GNS3 to the AP nor to the router.

lets say a fresh project.
i put in a router and a cloud. i configured the cloud so the NIO is the wireless adapter im using on my pc.
connect them with a fastethernet cable.
set the port on the router to dhcp. but i get nothing.

if i set the ip manually, i can ping from that port as source to my pc. but i cannot ping the AP or the router.
from what i understand, my adapter should be transparent and i should not be able to ping it (or at least ping it when packets goes through the router).

anyone has any idea?

Amit K.

Author:  claydon_dan [ Fri Jun 21, 2013 10:03 am ]
Post subject:  Re: connecting to access point

FAQ and Known Issues wrote:
Why my Wireless adapter doesn't work to connect to the real world?

Wireless NIC are known to have some problems with Winpcap and libpcap, those library being used by GNS3 for bridging with NICs. Workarounds exist on Windows and Linux, please see Bridge with a Wireless NIC on Windows.

Bridge with a Wireless NIC on Windows

Author:  amitko [ Sat Jun 22, 2013 3:08 pm ]
Post subject:  Re: connecting to access point


ive tried to use Loopback Manager.cmd i got with gns3 and created a loopback interface.
ive bridged it with the wireless adapter and assigned that bridge interface to the cloud.
the router in dhcp get the same ip address as my wireless adapter and no communication after that interface.
if i set a different address of the same subnet i can ping the bridge/wireless adapter but not after.

do you think using dynagen and winpcap will make any difference?

Author:  claydon_dan [ Sun Jun 23, 2013 11:29 am ]
Post subject:  Re: connecting to access point

I have just spent some time playing with a Network Bridge myself and was able to recreate the issue you have. The issue is caused by the Physical Adapter not entering 'promiscuous mode', this causes it to drop any packets with a MAC Address that it doesn't recognise (e.g it's own).

To resolve the issue:
Microsoft Support wrote:
To work around this behavior, force the adapter into Compatibility mode:

1. At a command prompt, type netsh bridge show adapter.
2. Locate the identification number of the NIC that is not responding.
3. If the NIC is not in Compatibility mode, you can change it manually if you type the following command, where 1 is the number of the NIC that is displayed in the first step:
netsh bridge set adapter 1 forcecompatmode=enable
Run the netsh bridge show adapter command again to verify that the ForceCompatabilityMode field for the NIC is displayed as Enabled.

After using the above, a router in GNS3 connected to the Loopback Adapter was then able to ping the rest of the network.

Author:  amitko [ Wed Jun 26, 2013 4:45 pm ]
Post subject:  Re: connecting to access point


thanks a lot.
i can ping the rest of my network now.
though i cant understand, if i can ping my AP and my router that means i can get to the router and back. than why cant i ping anything outside my network?

Author:  claydon_dan [ Wed Jun 26, 2013 5:34 pm ]
Post subject:  Re: connecting to access point

Are you trying to ping from router connected to the cloud in GNS3? (e.g from an interface within your network)

If yes, does the router have a default route set (show ip route)

If your trying to ping from an address other than your local lan you'll need to either route to this or perform NAT

Author:  amitko [ Thu Jun 27, 2013 5:44 pm ]
Post subject:  Re: connecting to access point

i need a face palm smiley :p
forgot the static route.

thanks for the help.
much appreciated.

Page 1 of 1 All times are UTC
Powered by phpBB® Forum Software © phpBB Group