Mikrotik bridge handling DHCP and wireless - 10.0.0.253/24
Mikrotik ether1 WAN used to talk to ADSL router - 192.168.2.2/24
ADSL router handling PPPoE only - 192.168.2.1/24
bridge-local is as per default - ether2 + wlan1
ports 3-5 are slaves of port 2
ether1 WAN going straight to my ADSL router
Never done it personally, but basically you would put the ADSL modem into bridge mode… then setup a PPPoE client on “ether1” on the mikrotik. Then just utilize “PPPoE” interface as your “gateway” interface instead of ether1.
When you have PPPoE client on RouterOS and bridged the ADSL router, then the ADSL router act as a modem only.
Then you have only 1 NAT, and that is on RouterOS.
Youl may have DNS of your provider or use 8.8.8.8 as primary and 8.8.4.4 as secondary
If you setup DHCP server on you LAN side you can put there and DNS.
If you are not use DNS in DHCP server (in Network tab), the clients on your lan uses the DNS of IP-DNS settings
Open “New Terminal” and type “export”
Then copy and paste it here. Change critical information like “PPPoE” username and password etc.
So I’ve got the mikrotik dialing out PPPoE and my ADSL router in bridge mode.
Everything works, EXCEPT I can not ping or access the ADSL router (192.168.2.1) from my LAN since I made the change and put PPPoE on my Eth1-Gateway port
I CAN however ping it from the mikrotik, so I know it’s up (also the internet works )
I believe there is some additional NAT rule that I need from digging around the forums, but I’ve not found anything that can help me yet… Any ideas how to access the ADSL router?
but ether2 is bridged with my wlan. the bridge has the ip 10.0.0.253/24
your external router should always be on a different subnet than your LAN. The routes ive got set up should normally let me access the 192168.2.x subnet fine. It’s only since I added the PPPoE interfact on Eth1 that I’m unable to get to 192.168.2.1 (adsl router)
Your external router is act only as a modem right now and not as a router.
Technically speaking, you don’t have any problem to have two different subnets on the same interface (bridge)
And yes, the NAT to 192.168.2.0/24 was missing for ether1-gateway.
So far so good