Hi There,
I’m trying to set up a simple bridging scheme using NeoRouter Mesh trial. I’m sharing below my battle plan (is there white board wallpaper in heaven?). The end goal is to control everything on the right side of the diagram from the client PC, through the 4G connection. This would be most awesome, and I’ll certainly buy this service if we can make it work.
Attachment:
mesh battleplan.JPG [ 549.39 KiB | Viewed 9994 times ]
In this current setup, the “client” PC can talk to the “gateway” PC through NeoRouter just fine, as long as the bridge is disabled. But, when I enable the bridge (NeoRouter to Local Area), the pings stop working, and I lose all access.
When I have the gateway ping itself, it responds:
Reply from: 192.168.1.3: Destination host unreachable. (I think this is the bridge replying)
When I have the client ping the gateway:
Reply from 192.168.1.101: Destination host unreachable. (This is the client itself responding?!)
The client retains its ability to ping itself whether or not the bridge is active.
I forced promiscuous mode as instructed. NETSH BRIDGE SHOW ADAPTER now shows: Forced Compatibility Mode “Enabled” for both “NeoRouter Connection” and “Local Area Connection” (the latter being the fixed cable leading to my mini AP).
Feature.ini, located in C:\Users\All Users\ZebraNetworkSystems\NeoRouter
“
[Default]
NetworkBridge=1
LANSegment1=192.168.1.0-192.168.1.50,192.168.1.120
UdpOnly=1
P2P=1
LangId=1033
“
I think the bridge should now become a client with NeoRouter IP 192.168.1.120, yes? Am I supposed to see it in the client list? (There's nothing there).
Please let me know what else I can do / test.
cheers,
Zauberkugel