Trouble setting up wifi ad hoc hotspot - cannot connect to internet

user0x12 · 08 Jul 2015

Running Win 7 64-bit. -Running two routers. 1st router is ISP facing, which is connects via wireless bridge to a second Linksys WRT (don't remember exact model atm) to extend range in my house. Either way, I get the same problem when connecting host machine to either router. When I am connected to downstream 2nd router (via wireless bridge) my default gateway points to the first router. I think under normal conditions the first router acts as DHCP server (second one disabled?)

Basically, I want to set up host machine as ad hoc wifi hotspot via Windows wizard. I set up the virtual wifi hotspot and it seems to work (followed these instructions: How To Turn Your Windows 7 Laptop Into a WiFi Hotspot).

I then try to connect with the client machines to newly created ad hoc wifi hotspot by selecting wireless network and entering password, and the process fails, saying DHCP lookup failed.

I open cmd.exe and run "arp -a" and see that APIPA addressing is active in lieu of dynamic IP address and that the client machine does have an APIPA address, yet I cannot access internet.

Is it a DNS issue? I notice that when I run ipconfig /all on host machine it shows DNS servers as hexademical values (MAC addresses?). I was under the impression that in the absence of DHCP, which the host machine cannot serve to client, APIPA will kick in thus giving address to host machine. But it seems like I can't get onto internet with this machine. I mean, how does the client access DNS tables when it is in APIPA mode?

Does it have to do with my wireless bridge dual router set up upstream or some DNS issue at the ad hoc wifi hotspot host machine level?

I realize that setting a static IP on the client machine is an option but I'd rather get DHCP/APIPA working instead.

Another point:

The ad hoc set up works when I run a program called Connectify Hotspot 2015 (and when host machine is connected to either router), but not when I use Windows' built in function.

I'd appreciate any insight. Thank you!

GokAy · 08 Jul 2015

APIPA (Automatic Private IP Addressing - 169.254.0.0) means you couldn't discover any DHCP servers. I don't have much experience in wireless routing but if in bridge mode I guess router 2 was supposed to be somewhat transparent. Normally (shouldn't be the case while bridged) DHCP protocol can't be routed, would need a DHCP proxy set up at the 2nd network segment.

Hmm, to not complicate things, can your host machine connect to the wireless network (normal private IP address)? And if so, to the Internet?

When connected to the 2nd router, in cmd (copy paste):

Code:

ipconfig -all | clip

It won't show anything but copy info to clipboard automatically, paste here.

user0x12 · 08 Jul 2015

GokAy said:

APIPA (Automatic Private IP Addressing - 169.254.0.0) means you couldn't discover any DHCP servers. I don't have much experience in wireless routing but if in bridge mode I guess router 2 was supposed to be somewhat transparent. Normally (shouldn't be the case while bridged) DHCP protocol can't be routed, would need a DHCP proxy set up at the 2nd network segment.

Hmm, to not complicate things, can your host machine connect to the wireless network (normal private IP address)? And if so, to the Internet?

When connected to the 2nd router, in cmd (copy paste):

Code:

ipconfig -all | clip

It won't show anything but copy info to clipboard automatically, paste here.

Okay, the set up does not work regardless of whether I connect to router 1 or 2.

The host machine in question can normally connect to either wireless routers with no problem.

I even tried this set up with another host machine with the same results.

GokAy · 08 Jul 2015

Try in cmd: ping 8.8.8.8

If you get replies back, then it is a DNS issue.

Also try to ping your Internet (Public) IP - What's My IP Address? - Obsolete Browser Page to quickly learn