[mt300n-v2] Wifi bridge without repeater

Hi,

I found this setup repeater bridge, but I would like to have a bridge without repeater, means I would like
connect 2 PC’s to both ports (wan/lan) and make a bridge via wifi to my (internet) router. The mt300n-v2 should not be a repeater, means it shouldn’t send the ssid and should not allow in connecting devices via wifi (except my internet router…).

Is this possible, if yes, how?

Thx,
Patrick

For MT300N-V2, you need to set up WDS (actually not really WDS and it works with any AP). When setting up WDS, leave LAN IP blank. DO NOT use static IP.

You can turn off the AP of MT300N-V2.

By default, WAN and LAN doesn’t bridged. If you want to do this, need to set up in LUCI. Need to remove WAN and edit LAN’s physical interface to eth0.0 and eth0.1

Thank you. I bought the router today via amazon. When I have it, then I come back!

thanks very much! Please let me know if you have any problems.

I have a problem. Everything done acc. your description. Router is accessible via WLAN (and also with connected PC via LAN/WAN port). Router can check firmware, can download packages, but the connected pc has no internet connection if dhcp is enabled (checked the received gateway and dns, is the ip from my main router which is connected to internet). If I disable dhcp and enter everything manually, then I have a internet connection. So what is wrong? Main router has dhcp running…

Thank you!

It is normal if you use bridge mode. On bridge mode, it should be disabled dhcp server, so the pc will gain ip from upstream router(Your main router), in this case, mt300n-v2 act as repeater.

No you misunderstood,

If I connect the pc to the mt300n and use static ip on the pc(!) I have internet connection, but when I get the ip (and gateway and dns) via DHCP on the pc(!) I have no internet connection on the pc. But everything looks the same on the pc connection (correct ip, gateway and dns received).
So what is wrong?

You can just give the IP info in this two different scenarios so that we can check the info. Now there is no way to tell what is wrong.

I use a Win10 64bit, here the output of ipconfig /all:

Ethernet-Adapter Ethernet 3:
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physische Adresse . . . . . . . . : AC-87-A3-00-ED-B9
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 192.168.0.3(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Mittwoch, 28. März 2018 17:49:35
   Lease läuft ab. . . . . . . . . . : Donnerstag, 29. März 2018 17:49:35
   Standardgateway . . . . . . . . . : 192.168.0.241
   DHCP-Server . . . . . . . . . . . : 192.168.0.241
   DNS-Server  . . . . . . . . . . . : 192.168.0.241
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

and here with manual assigned IP:

Ethernet-Adapter Ethernet 3:
       Verbindungsspezifisches DNS-Suffix:
       Beschreibung. . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
       Physische Adresse . . . . . . . . : AC-87-A3-00-ED-B9
       DHCP aktiviert. . . . . . . . . . : Nein
       Autokonfiguration aktiviert . . . : Ja
       IPv4-Adresse  . . . . . . . . . . : 192.168.0.88(Bevorzugt)
       Subnetzmaske  . . . . . . . . . . : 255.255.255.0
       Standardgateway . . . . . . . . . : 192.168.0.241
       DNS-Server  . . . . . . . . . . . : 192.168.0.241
       NetBIOS über TCP/IP . . . . . . . : Aktiviert

Working route (pc without dhcp):

IPv4-Routentabelle
    ===========================================================================
    Aktive Routen:
     Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
          0.0.0.0          0.0.0.0    192.168.0.241     192.168.0.77    291
        127.0.0.0        255.0.0.0   Auf Verbindung         127.0.0.1    331
        127.0.0.1  255.255.255.255   Auf Verbindung         127.0.0.1    331
      127.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
      192.168.0.0    255.255.255.0   Auf Verbindung      192.168.0.77    291
     192.168.0.77  255.255.255.255   Auf Verbindung      192.168.0.77    291
    192.168.0.255  255.255.255.255   Auf Verbindung      192.168.0.77    291
        224.0.0.0        240.0.0.0   Auf Verbindung         127.0.0.1    331
        224.0.0.0        240.0.0.0   Auf Verbindung      192.168.0.77    291
      255.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
      255.255.255.255  255.255.255.255   Auf Verbindung      192.168.0.77    291
    ===========================================================================
    Ständige Routen:
      Netzwerkadresse          Netzmaske  Gatewayadresse  Metrik
          0.0.0.0          0.0.0.0    192.168.0.241  Standard
    ===========================================================================

Not working (with dhcp on pc):

    IPv4-Routentabelle
    ===========================================================================
    Aktive Routen:
         Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
              0.0.0.0          0.0.0.0    192.168.0.241      192.168.0.4     35
            127.0.0.0        255.0.0.0   Auf Verbindung         127.0.0.1    331
            127.0.0.1  255.255.255.255   Auf Verbindung         127.0.0.1    331
      127.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
          192.168.0.0    255.255.255.0   Auf Verbindung       192.168.0.4    291
          192.168.0.4  255.255.255.255   Auf Verbindung       192.168.0.4    291
        192.168.0.255  255.255.255.255   Auf Verbindung       192.168.0.4    291
            224.0.0.0        240.0.0.0   Auf Verbindung         127.0.0.1    331
            224.0.0.0        240.0.0.0   Auf Verbindung       192.168.0.4    291
      255.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    331
      255.255.255.255  255.255.255.255   Auf Verbindung       192.168.0.4    291
    ===========================================================================
    Ständige Routen:
      Keine

I cannot see any difference?!

Thx for your help!

seems no difference to me as well. How about just reboot the router when using DHCP?

It works now, it was the DHCP of the router. But this was/is funny, because my main router has a wireless mac filter and dhcp has restriction for allow only known MAC addresses.

So on the mt300n-v2 I can see:

root@GL-MT300N-V2:~# ifconfig
apcli0    Link encap:Ethernet  HWaddr E6:95:6E:03:E4:A7
          inet6 addr: fe80::e495:6eff:fe03:e4a7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-lan    Link encap:Ethernet  HWaddr E4:95:6E:43:E4:A7
          inet addr:192.168.0.104  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::e695:6eff:fe43:e4a7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:993 errors:0 dropped:0 overruns:0 frame:0
          TX packets:379 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:227014 (221.6 KiB)  TX bytes:94151 (91.9 KiB)

eth0      Link encap:Ethernet  HWaddr E4:95:6E:43:E4:A7
          inet6 addr: fe80::e695:6eff:fe43:e4a7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1295 errors:0 dropped:3 overruns:0 frame:0
          TX packets:2002 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:301618 (294.5 KiB)  TX bytes:605571 (591.3 KiB)
          Interrupt:5

eth0.1    Link encap:Ethernet  HWaddr E4:95:6E:43:E4:A7
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1208 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1370 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:260434 (254.3 KiB)  TX bytes:419941 (410.0 KiB)

eth0.2    Link encap:Ethernet  HWaddr E4:95:6E:43:E4:A7
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:618 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:175309 (171.2 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

So there are two mac addresses which I have to add to the wireless filter E4:95:6E:43:E4:A7 which is the MAC printed on the label of the router, and this E6:95:6E:03:E4:A7 which is apcli0 and belongs to WWAN.

And when I add this two mac’s to the dhcp and give static ip’s, I can see this devices in the list (note the two E6:95:6E:03:E4:A7:


and

It is working now, but why I have two same ip’s with this two mac addresses (one is always the WWAN)?

What happens if I delete the WWAN?

Regards
Patrick

That is bridge. Don’t delete it.

You can try if you want to know what will happen. You can reset the router if you have problems.

1 Like