Access the GUI of a bridged modem with PPPoE and VLAN
-
I just removed the external modem/router and added a modem in bridged configuration to avoid the double NAT.
My provider needs a VLAN within the PPPoE access.
So I configured the VLAN on the WAN physical port, linked this VLAN under WAN interface under MLPPP and all works fine.My pfsense is under 192.168.1.x, the modem keeps a 192.168.100.0 gateway from the ISP and my bridged modem is 192.168.150.1.
But I can't access the modem GUI and I think because of VLAN; infact my other modem (bridged LTE 4G modem with 192.168.200.1 IP) is reachable without issues.
I found this guide Accessing a modem - pfSense Documentation but I don't know if it is applicable to my configuration because it refers to a virtual PPPoE but my VLAN is linked to the physical interface.
-
What is the IP of your 'real' WAN ?
If your modem doesn't do 'DHCP' you could set the WAN to a static IP, like
192.168.150.2 mask /24
and from then on your pfSense knows where to find 192.168.150.1 (it's in the 192.168.150.0/24 network rachable on WAN) just like your LTE.@valepe69 said in Access the GUI of a bridged modem with PPPoE and VLAN:
because it refers to a virtual PPPoE but my VLAN is linked to the physical interface.
Is applicable.
Look at the physical NICs on pfSense. None can be labeled as the pppoe interface. Like VLAN, pppoe is transported over one of these NICs (the WAN typically) so like a VLAN, pppoe can be seen as virtual. -
@Gertjan
I have a dynamic IP from my ISP and the WAN interface must have to set to PPPoE so I can't set a static IP.Anyway I think that the problem is within the VLAN that is needed to instaurate a connection to the ISP.
Infact the other modem ha a DHCP configuration but I can reach its GUI without issues even if its assigned IP is not on the same subnet of the gui. -
@valepe69 said in Access the GUI of a bridged modem with PPPoE and VLAN:
I have a dynamic IP from my ISP and the WAN interface must have to set to PPPoE so I can't set a static IP.
Look at your interface list. Show it ?
You have a WAN and a VLAN interface and a pppoe interface, right ? The latter will get it's IP settings from the ISP. Not your WAN - so you can set WAN to your needs using DHCP ? or static.Btw : why not : a physical WAN, 'in' which you create a VLAN, and then a pppoe is based upon this VLAN.
-
@Gertjan
I'm not at home now but I followed this guide: PPPoE with VLANIn the dropdown I must choose PPPoE
-
@valepe69 said in Access the GUI of a bridged modem with PPPoE and VLAN:
but I followed this guide: PPPoE with VLAN
Ah, ok, get it.
As on WAN you had to select pppoe as the "IPv4 Configuration Type" you can't select something else.In this case : Accessing a CPE/Modem from Inside the Firewall is the way to go - what you've already mentionned above.
My suggestion : the situation "a router behind a router" which implies that you might have to create one or two NAT rules on your ISP router - or using the bridge mode == using pppoe on pfSense, I would go for the first (NAT) solution.
pppoe is old and speed limited.
Keeping the pfSense WAN setup as simple as possible (using default WAN DHCP) is an advantage.NATting isn't really special, we've all being doing this since it was invented (before 1980), and NAT will fade out as IPv6 is what's left (not any time soon, I agree, but we will all see it happening).
-
@Gertjan
Thanks -
Yes you should be able to access it be just assigning the VLAN parent interface and setting it in the same subnet as the modem admin page. As long as that doesn't conflict with any existing subnet on the firewall.
