Hi,There is no need to make VLANS to establish multiple EoIP tunnels as long as you specify unique tunnel-ids.
Hi Thanks for your reply.No, bridge is not required for EoIP to function. And of course you will not be able to add one physical interface to multiple bridges.
You can easily put in one bridge all EoIP tunnels and one physical interface. Or maybe I just misunderstood what you want to achieve.
you have to set ip address of the other end of eoip tunnel and tunnel-id that is all
if you want to establish eoip tunnel from A-------B then on A you have to set up ip address of B and vice versa on B
when you create tunnel it is as if it is normal Ethernet interface.
all the routing and bridging apply to these tunnels, it wont miraculously guess what you want to bridge with what.
you have to configure it yourself. It is layer 2 tunnel. that is it, no magic involved
Thanks. I understand that. But if its a multicast traffic, EoIP+Bridge which is at layer 2 (cannot differentiate between multicast and broadcast) will flood all EoIP tunnels connecting to the same bridge. Is that true ?if you truly want to pass broadcasts and bridge the two networks you shouldnt place any IP address on the EoIP tunnel itself (other than its outside endpoints) and just bridge those interfaces to the LANs on each side. Both sides can then use the same subnets.
192.168.1.0/24 (LAN A)--->10.10.10.1/24 (WAN A)---eoip--> 10.10.10.2/24(WAN B)---->192.168.1.0/24(LAN B)
Or make as follow:if you truly want to pass broadcasts and bridge the two networks you shouldnt place any IP address on the EoIP tunnel itself (other than its outside endpoints) and just bridge those interfaces to the LANs on each side. Both sides can then use the same subnets.
192.168.1.0/24 (LAN A)--->10.10.10.1/24 (WAN A)---eoip--> 10.10.10.2/24(WAN B)---->192.168.1.0/24(LAN B)
see how fast time passes by. eight years later today, i still find this topic fascinating..Or make as follow:if you truly want to pass broadcasts and bridge the two networks you shouldnt place any IP address on the EoIP tunnel itself (other than its outside endpoints) and just bridge those interfaces to the LANs on each side. Both sides can then use the same subnets.
192.168.1.0/24 (LAN A)--->10.10.10.1/24 (WAN A)---eoip--> 10.10.10.2/24(WAN B)---->192.168.1.0/24(LAN B)
192.168.1.0/22 (LAN A)--->10.10.10.1/24 (WAN A)---eoip--> 10.10.10.2/24(WAN B)---->192.168.2.0/22(LAN B)
Depends on the configuration but at HQ:
- Each EoIP tunnel needs a unique "remote address" and unique "Tunnel ID"
- In firewall, input chain, allow GRE protocol (if using public ip address [remember traffic is not encrypted] else if using internal ips check if the transport tunnel is running [ex if using ipsec])
Supposing I've understood what you actually wanted properly, make a bridge and make eth2 and all the EoIP interfaces member ports if that bridge:Now what i want to know is : how to pass all the 24 tunnels through the Eth2 ?
Dear Sindy,Supposing I've understood what you actually wanted properly, make a bridge and make eth2 and all the EoIP interfaces member ports if that bridge:Now what i want to know is : how to pass all the 24 tunnels through the Eth2 ?
/interface bridge
add name=eoip-bridge
/interface bridge port
add bridge=eoip-bridge interface=ether2
add bridge=eoip-bridge interface=eoip1
..
add bridge=eoip-bridge interface=eoip24
Because to me, "pass all 24 tunnels through ether2" would mean the transport packets of the tunnels should be routed via ether2, but your previous posts suggest that you want to bridge ether2 with the payload of the tunnels.
Yes, exactly, as suggested above. Add-ons can be applied:Now, to make client traffic passing through Eth2 at HQ, do i have to bridge all 24 EoIP interface with the Eth2?
It's clear for me now.Yes, exactly, as suggested above. Add-ons can be applied:Now, to make client traffic passing through Eth2 at HQ, do i have to bridge all 24 EoIP interface with the Eth2?
- if the client eventually wants each BO site to be reachable via a different VLAN at ether2 of the HQ site, you would activate vlan-filtering on the bridge and make the individual EoIP interfaces access ports of the individual VLANs
- if the client eventually wants all sites in the same LAN segment but he wants the traffic to pass only between ether2 of the HQ site and a particular BO site but not between two BO sites, you can use the bridge horizon function.
It's well noted.To prevent traffic from being forwarded between two ports of the same bridge, set the same horizon value for both. E.g.:
/interface bridge port set [find where interface~"eoip[23]"] horizon=1
will prevent traffic forwarding between eoip2 and eoip3.
Dear sindy,[*]if the client eventually wants all sites in the same LAN segment but he wants the traffic to pass only between ether2 of the HQ site and a particular BO site but not between two BO sites, you can use the bridge horizon function.[/list]