Accessing modem only

sebus · Sat Mar 14, 2020 7:41 pm

I am trying to get to Zyxel VMG3925-B10B / VMG1312-B10A in Bridge/Modem Only mode from LAN driven by Mikrotik router

So the setup is client (wired or wireless) --> Mikrotik Eth1 --> single cable to VMG3925-B10B Eth1

From LAN client (192.168.88.1) I can ping the newly created Vlan2 interface on Mikrotik (192.168.2.1), but not the home networking/group interface on Zyxel (192.168.2.10)
Vlan2 is "attached" to Mikrotik Eth1 (which is used for PPPoE connection to Zyxel Eth1)

I have followed

1 - login to UI of zyxel
2 - select networks -> vlan groups
3 - add group called bridge set vlan id to 2, tick the include box on the lan port you want to use (one used for wan)
4 - select networks -> interface grouping and assign bridge vdsl port to same lan port.
Note you may have already done steps 3 and 4 when setting up the bridge.
5 - now select networks -> home networking
6 - in group name box default is preselected, change this to bridge
7 - make a note of the ip address shown, change if you want to. (to keep things simple change it to 192.168.2.10

If I add ie Eth4 to Vlan Group on Zyxel (point 2 above), then connecting directly on that Eth4 I can access Zyxel unit via that IP, so it does work (just not the two together, yet)
I can not ping Zyxel from Mikrotik itself either

[admin@MikroTik] > ping 192.168.2.10
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                  
    0 192.168.2.10                                            timeout                                                                                                 
    1 192.168.2.10                                            timeout                                                                                                 
    2 192.168.2.1                                84  64 982ms host unreachable                                                                                        
    3 192.168.2.10                                            timeout                                                                                                 
    sent=4 received=0 packet-loss=100%

Help appreciated

jvanhambelgium · Sat Mar 14, 2020 8:52 pm

Your Microtik is having an active PPPoE connection then ? This goes THROUGH the Zyxel straight to your ISP. This that configured & up/running ??
If so, then it is understandable that you cannot ping the LAN-side of Zyxel

1) What about NAT on the Microtik ? It will inject all traffic into its default-gateway, the PPPoE session to internet
2) Your Zyxel does not know about 192.168.88.x => Did you add route on the Zyxel for that ? Sure you can ping the direct-connected Mikrotik interface 192.168.2.1 but as soon as you ping Zyxel 192.168.2.10 it wants to reply to your PC on 192.168.88.1 but without any route.....

EDIT : I read you tried from the Mikrotik itself and you cannot reach 192.168.2.10 neight. Firewall-policy ? I think the first question others will give : can you give the full config (without sensitive info)

sebus · Sat Mar 14, 2020 9:22 pm

Directly connected VLANs should not need firewall policy and/or routing (unless one wants to disable access between)
Hence I would expect to get a reply at least from withing Mikrotik console itself

Anyway, nothing from Zyxel to Mikrotik either, must be something to do with Vlan setup (most likely)

ZySH> ping
BusyBox v1.20.1 (2019-05-06 17:42:59 CST) multi-call binary.

Usage: ping [OPTIONS] HOST

Send ICMP ECHO_REQUEST packets to network hosts

        -4,-6           Force IP or IPv6 name resolution
        -c CNT          Send only CNT pings
        -s SIZE         Send SIZE data bytes in packets (default:56)
        -t TTL          Set TTL
        -I IFACE/IP     Use interface or IP address as source
        -W SEC          Seconds to wait for the first response (default:10)
                        (after all -c CNT packets are sent)
        -w SEC          Seconds until ping exits (default:infinite)
                        (can exit earlier with -c CNT)
        -q              Quiet, only displays output at start
                        and when finished

ZySH> ping -4 192.168.2.1
^Ccommon_ping: hostname 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes

--- 192.168.2.1 ping statistics ---
11 packets transmitted, 0 packets received, 100% packet loss
ZySH> ping -4 -I 192.168.2.10 192.168.2.1
^Ccommon_ping: hostname 192.168.2.1
PING 192.168.2.1 (192.168.2.1) from 192.168.2.10: 56 data bytes

--- 192.168.2.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

sebus · Sun Mar 22, 2020 3:50 pm

OK, that was easier than expected after all. Used this as a pointer: https://blog.dical.org/?p=22

On Zyxel still created Interface Group & Home Networking new IP address assigned to this Group, but there is no need for Vlan settings (as no Vlans are involved)
Then ofcourse on Mikrotik one needs to add correct route, and the same on Zyxel (for the new address & Mikrotik as destination)

sebus46 · Sat Jun 17, 2023 8:11 pm

The updated link is here:

https://blog.dical.org/how-to-reach-ppp ... -mikrotik/

Accessing modem only

Accessing modem only

Re: Accessing modem only

Re: Accessing modem only

Re: Accessing modem only

Re: Accessing modem only

Who is online