Community discussions

MikroTik App
 
jtuttle
newbie
Topic Author
Posts: 32
Joined: Sun Jun 26, 2005 9:51 pm

PC behind mikrotik wireless client unable to ping gateway

Wed Dec 01, 2021 4:41 am

Hello, we have a very basic configuration:

Internet >> Mikrotik FW >> Ubiquiti AP >> Mikrotik as wireless client >> PC NIC (DHCP) + Printer NIC (DHCP)

We had a PC (DHCP) connected wirelessly to the Ubiquuiti AP with no issues.
We now need to connect a cabled printer at the same location as the wirelessly connected PC.
The printer AND the PC both successfully obtain an IP address via DHCP on the cabled connection to the Mikrotik as wireless client but NEITHER can ping the Mikrotik FW or 8.8.8.8.
The Mikrotik as wireless client CAN ping the Mikrotik FW and 8.8.8.8.

I feel this is a MAC address multiplexing issue.
I've searched and hacked but no success.
All equipment is at latest firmware versions.

Ideas?

Many thanks to all.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11584
Joined: Thu Mar 03, 2016 10:23 pm

Re: PC behind mikrotik wireless client unable to ping gateway

Wed Dec 01, 2021 6:48 pm

What you're after is L2-transparent bridge over wifi and can't be done in standard way, it only works reliably when both wireless devices are from same vendor. More expkanation in this article: https://wiki.mikrotik.com/wiki/Manual:W ... tion_Modes
 
User avatar
bpwl
Forum Guru
Forum Guru
Posts: 2993
Joined: Mon Apr 08, 2019 1:16 am

Re: PC behind mikrotik wireless client unable to ping gateway

Wed Dec 01, 2021 8:44 pm

Pfffff .... this can give you quite some headache pain.

Some suggestions :

1; use a Mikrotik AP as link distributor to the Mikrotik wireless client device (call this the MT client).
Then the link can be "AP bridge" on the MT AP, and "station bridge" on the MT client. You get one transparant bridged L2 network to use.

2: as MKX suggested use the MT client as "station pseudo bridge". The pseudo-bridge will do MAC translation. IP addresses behind the pseudo-bridge can reach the FW and 8.8.8.8
Initial access to the devices behind the pseudo-bridge may not be possible. (switch MAC table, or bridge hosts-table must first be populated).
DHCP servers can be disturbed by the missing MAC entry, and might not reach the client device with the IP address offer.
(DHCP lease is offered, and then disappears instead of reaching "bonded" state)
Experience on DHCP varies.

3. Use one MT client per device. (e.g. a hAP Lite or other low cost device).

4. Make a tunnel between the Mikrotik FW and the MT client. The "MT client" is in mode "station". Tunnel used for this (in PtP examples) is either EoIP or for better performance MPLS/VPLS. I assume other L2 tunnels could be used as well. You again have one L2 bridged network.

5 Not sure if WDS between Ubiquiti and "MT client" would work. Security is one potential problem. But WDS even without security is vendor specific.

Who is online

Users browsing this forum: No registered users and 19 guests