Help bridging VZW MiFi Jetpack to home network router

solley

Reputable
Oct 11, 2015
2
0
4,510
Want to serve my house with 4g LTE from the Verizon MiFi 6620L, but I've got myself completely confused on IP addressing schemes, DHCP, etc.

Intended setup would look like this:

Verizon internet via 4G LTE to MiFi Jetpack
MiFi Jetpack wireless to TP-Link TL-WA801ND Wireless N Access Point in Bridge Mode
TL-WA801ND wired to WAN port (?) of TP-link AC1750 router (model Archer C7)
AC1750 to rest of home network devices (TiVos, Rokus, phones, laptops, etc.) via both wired and wireless.

Would like to keep the "home" side of the router unchanged, if possible.

Right now, router is connected to cable company modem with LAN IP address of 192.168.1.1. DHCP is enabled and the WAN IP address is assigned dynamically.

I've really got myself spinning over what settings I need for the Mifi and the Bridge...IP addresses, DHCP settings, Gateways, etc.

Please let me know what other details you may need to get me straightened out.

THANKS!
 
Solution
Your problem likely is with the tplink AP device. You have the design basically correct. You must be very careful there are 2 forms of bridge mode. The one you want is called client-bridge. In addition there are couple of forms of client-bridge. The most common you see uses a protocol called WDS which is not actually a part of the 802.11 standard but everyone uses it. Most mobile broadband hotspots do not support WDS.

Now having WDS on the bridge end but not the hotspot does not hurt as long as the bridge does not have a restriction that it will not go into client-bridge mode without it.

So you need to get the tplink to run client-bridge mode...preferably without WDS.

The problem with not using WDS is bridge must either...
Your problem likely is with the tplink AP device. You have the design basically correct. You must be very careful there are 2 forms of bridge mode. The one you want is called client-bridge. In addition there are couple of forms of client-bridge. The most common you see uses a protocol called WDS which is not actually a part of the 802.11 standard but everyone uses it. Most mobile broadband hotspots do not support WDS.

Now having WDS on the bridge end but not the hotspot does not hurt as long as the bridge does not have a restriction that it will not go into client-bridge mode without it.

So you need to get the tplink to run client-bridge mode...preferably without WDS.

The problem with not using WDS is bridge must either establish the wireless session using the routers mac or it must translate the router mac to the bridge mac. All this stuff including WDS is related to fact that the mac addresses are used as part of the encryption keys in the wireless session. Using a bridge of any kind in effect is bypassing the mac level security and is why it is so messy.

If all else fails I think that tplink can run third party firmware like dd-wrt. dd-wrt has more option than factory firmware.
 
Solution

Latest posts