I am setting up an eoip tunnel between two data centers. I then attempt to bridge the internal lan of each data center with the eoip interface on each router.
As soon as I enable the bridge, I lose connectivity to the internal ip address assigned to the router.
I then assign the internal ip to the bridge interface instead of the nic, however I still have no connectivity to this ip from the internal lan.
Add to bridge local and EoIP interfaces, check if the MAC-addresses for the EoIP tunnels are not the same.
Could you ping computers from the router, they are connected to ?
After creating the bridge, I have a total of 4 interfaces on each router:
External
Internal
Bridge1
EOIP-Location1
External
Internal
Bridge1
EOIP-Location2
The bridge for each router contains the Internal and EOIP interfaces.
I can ping Router1 from Router2 but can not ping any computers connected to the same lan Router1 is conencted to from Router1. The same is true for Router2.
Maybe there is another way to do what I’m trying to do?
I need to allow servers in InternalLAN1 connect to servers in InternalLAN2 through some sort of route or tunnel over the public internet.
I can ping Router1 from Router2 but can not ping any computers connected to the same lan Router1 is conencted to from Router1. The same is true for Router2.
i can’t see a difference, besides that i have enabled proxy-arp at one side, but this is for PPTP only. Did you check if the EoIP-Tunnel is working? That is seeing MAC-Adresses from the other tunnel-side, and check if any traffic is going through the tunnel. Maybe you should post “/interface export” and “ip address print”
Maybe there is another way to do what I’m trying to do?
I need to allow servers in InternalLAN1 connect to servers in InternalLAN2 through some sort of route or tunnel over the public internet.
If no layer 2 is needed, of course a layer 3 connection, e.g. PPTP- or IPSec-tunnel would be better. Do the public interfaces have static IP-addresses? If yes, i would suggest using an IPSec-tunnel.
Unfortunately my networking knowledge is limited, but what I’m looking to do is have any server on the internal network in one data center seemlessly connect with any server in the internal network on the other data center.
All the servers are in the 192.168.0.x/24 subnet, ideally the solution would also allow broadcast packets so the windows servers could identify eachother by name.
All the servers are in the 192.168.0.x/24 subnet, ideally the solution would also allow broadcast packets so the windows servers could identify eachother by name.
LAN-Broadcasts could cause a lot of WAN-Traffic, does that matters?
AFAIK Windows-server could interconnect without seeing broadcasts, using the Windows Domain System, Active Directory or something (sorry my Windows-knowledge is limited)
But EoIP is working with MT ROS for sure. BTW which Router OS version is used?
One additional note, the arp list on the Rochester router seems to populate with the MACs from server in Vienna, however the ARP list in Vienna never seems to populate.
The routers were installed as virtual servers using Microsoft Virtual Server 2005 R2. It appears, that this is why I can not ping other computers on the lan. I can ping other virtual servers set up on the same boxes through the tunnel.
It looks like if I setup dedicated servers to do this, the eoip tunnel and brdige would work normally.
Here’s a few things you might try, based on the configuration you published on the URL you posted.
You have configured two IP addresses on the external interface of the Rochester router, and you have configured
the higher-numbered / second one of them (74.39.252.133) as the EoIP tunnel peer on the Vienna router.
Try using 74.39.252.129 as the EoIP tunnel endpoint (change the Vienna router accordingly).
Why do you have arp=proxy-arp on the bridge1 interface on the Rochester router?
Try changing it to arp=enabled
While you are at it: Since you’ve added the IP address to the bridge1 interface (that’s good) and not
to the interfaces that are members of the bridge (Internal, eoip-), you can switch off arp altogether on the
Internal and eoip- interfaces on both routers.
ARP functionality only makes sense on interfaces that actually have IP addresses assigned to them.