This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
networking:router:mikrotik_sw_vs_bridge [2016/11/09 08:12] gcooper |
networking:router:mikrotik_sw_vs_bridge [2016/11/09 08:22] (current) gcooper |
||
---|---|---|---|
Line 54: | Line 54: | ||
===== Software (CPU) bridging ===== | ===== Software (CPU) bridging ===== | ||
- | In this case, switch groups | + | In this case, traffic between |
< | < | ||
/interface bridge | /interface bridge | ||
add name=bridge-local | add name=bridge-local | ||
- | port add interface=eth1 bridge=bridge-local | + | port add interface=ether2 |
- | port add interface=eth6 bridge=bridge-local | + | port add interface=ether6 bridge=bridge-local |
+ | port add interface=sfp1 | ||
</ | </ | ||
- | NOTE: don't forget to assign an IP address to the bridge and, if you're using DHCP server on Mikrotik, change its interface to bridge-local as well. | + | < |
< | < | ||
/ip address add interface=bridge-local address=192.168.1.1/ | /ip address add interface=bridge-local address=192.168.1.1/ | ||
- | /ip dhcp-server add interface=bridge-local address-poll=[name of your address pool] | + | /ip dhcp-server add interface=bridge-local address-pool=[name of your address pool] |
</ | </ | ||
===== Patch Cord ===== | ===== Patch Cord ===== | ||
- | Just connect any port from group 1 (ether1-5) to any port in group 2 (ether6-10). | + | While rarely done, you //can// just connect any port from group 1 (ether2-5) to any port in group 2 (ether6-10). |
+ | |||
+ | Generally, we suggest using the first option (bridging). |