So I have a ATT uverse router.
It is set up to IP pass through so I get a WAN IP at the Mikrotik. WAN IP 75.77.55.xxx
Now the issue is I need to have some devices still pull an IP from the ATT Router 192.168.1.0/24
So
WAN Feed
ATT Router — Mikrotik Set up to get a WAN IP
Cable Boxes need to get an IP from the ATT router.
The rest of the network should get IPs from the Mikrotik (10.1.10.0/24)
So I plugged the Cable boxes into the ATT router and they get IP addresses from the ATT router.
The issue is that we are dealing with managed switches and I would like a switch port on a far switch to bascially pass on a VLAN right down to the ATT uverse.
Better switches and I would have plugged the ATT into one side of the switch and the Mikrotik into the other. Then untagged or slaved ports as needed. I am not familiar with the switch on site so I am trying to force this at the mikrotik.
So what I really need to do is tag a VLAN.
Then have that VLAN get IP addresses from the ATT Box’s DHCP server while the Mikrotik keeps getting a WAN IP that is routes for the main network.
I’m assuming the physical connection looks like this:
[ATT Router] → Mikrotik —> switch
And there are some other devices on “lan” ports of the Mikrotik as well, right?
Okay - so on the switch, set the port to the Mikrotik as a trunk, with the LAN as the untagged VLAN so that you don’t have to make a whole bunch of changes. Then create a VLAN (say, vlan 10) in the switch, and allow it tagged on the trunk interface to the Mikrotik, and untagged on whatever ports need to be on the “outside” network.
Then in the mikrotik, create a bridge interface “wan” and a vlan interface called wan-vlan with vlan-id=10 and interface = whatever port is connected to the switch.
Then in /interface bridge ports menu, connect the outside interface (connected to att router) and the wan-vlan interfaces to the bridge as ports.
Finally, move your wan IP / dhcp client / pppoe client (whatever type of configuration it’s using) to the wan bridge interface, and update all of your firewall rules, changing all instances of the physical interface to be the wan bridge interface instead.
That should get you rolling.
I tried simply bridging 2 ports on the router yesterday. Tech on site said the network went down. I was frustrated as I had a different site to get too. I also felt that I was having to accommodate his bad hard ware choices.
I wanted to take a feed from the Tik and a feed from the ATT and run them to different interfaces. Then slave things as needed or use the vlan switch settings.
But someone picked these switches because the manufacture “is such a bunch of nice guys.”
Who cares when stuff doesn’t work???
Ended up running a second feed to the Tik from the ATT on port 5.
Added Vlan20 on Ether2.
Bridged Vlan20 to Ether5.
Packets passed.
Once they figured out their switch and turned of IGMP snooping… started working.