Hi
I have 2 CHR (one on KVM and the other on ESXi) with EoIP tunnel in between
on First CHR (KVM ) everything was OK until today, EoIP tunnel stop working
First CHR(KVM ) Version 6.43.2
Sec CHR (ESXi) 6.42.7
Try to upgrade to same as KVM CHR ROS version and set tunnel id 1. Also check logs and sock proxy for strange stuff.
nothing.
they are same version
still not working
Stupid question - do you have only the EoIP tunnel between the two CHRs or also a GRE tunnel?
Please check logs and ave you tried to ping routers if they can reach each-other?
they can ping each other with their public IP
And with 1500 mtu?
P.S.: Try to use this macs range for both sides 00:00:5E:80:00:00 - 00:00:5E:FF:FF:FF
I have the same of problem, how to solve it?
Thank you!
L.E.: I added GRE in firewall and it`s works!
The reason is that EoIP is one of possible applications using GRE as transport. The very idea of GRE is to allow tunneling different types of payload (G = generic). So what we are used to call a GRE tunnel is actually an “IP over GRE” one, whilst EoIP is an “Ethernet over GRE” one.
I have the same problem, in my case GRE traffic was filtered by the first rule, which resets the “invalid” connection state input chain.
As soon as I disabled this rule, the GRE traffic flow as usual, I could not understand what was the matter.
But as soon as I turned on the PPTP service port, GRE traffic was no longer dumped as invalid.
The problem is that the PPTP service port has been disabled for more than a year and everything worked fine, but after updating 6.45.6 it stopped working and rolling back to 6.45.3 did not return this functionality
The PPTP service must be enabled, otherwise GRE traffic may be filtered input chain by an Drop invalid connection state rule.
This problem appeared after the update on one of my devices, PPTP was turned off, after disabling drop rule GRE start work, and after enabling PPTP service GRE no more dropped as invalid
I have the same problem.
I have try to new EOIPV6 and it’s not running, too.
I found the solution for this problem which I cannot explain.
At first I create new eoipv6 interface and it’s not running like the problem in this post.
Coincidentally, I use the webfig via browser to create new eoipv6 with the same configure in winbox and it’s running !!!
If anyone know, please explain.
That sounds as if the command line or Winbox (you haven’t stated which of these two you use normally) and WebFig were using different defaults when adding an EoIP v6 configuration item.
If you create one tunnel using your usual user interface, and the other one using WebFig, what does /interface/eoipv6/export verbose show?