New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fails to add tunnel as it already exists - Smartgateway fails #83
Comments
Hi,
I would guess the smartgw code (or the tunnel code itself) needs a codepath
that reacts to the "file exists" code by removing and re-adding the tunnel.
Henning
…On Sun, Jun 28, 2020 at 4:38 PM Sven Roederer ***@***.***> wrote:
On my node I was not able to access the internet via SmartGateway.
ip route returned no default route even a Smartgateway was avail in the
net (direct neighbour 10.36.217.96). I found the logfile full of following
messages:
Sun Jun 28 16:29:25 2020 daemon.err olsrd[6735]: Cannot add tunnel
tnl_0a24d960 to 10.36.217.96: File exists (17)
Sun Jun 28 16:29:25 2020 daemon.err olsrd[6735]: Cannot create tunnel
tnl_0a24d960
Sun Jun 28 16:29:43 2020 daemon.err olsrd[6735]: Cannot add tunnel
tnl_0a24d960 to 10.36.217.96: File exists (17)
Sun Jun 28 16:29:43 2020 daemon.err olsrd[6735]: Cannot create tunnel
tnl_0a24d960
Sun Jun 28 16:29:50 2020 daemon.info odhcpd[848]: Using a RA lifetime of
0 seconds on br-dhcp
Sun Jun 28 16:29:51 2020 daemon.err olsrd[6735]: Cannot add tunnel
tnl_0a24d960 to 10.36.217.96: File exists (17)
Sun Jun 28 16:29:51 2020 daemon.err olsrd[6735]: Cannot create tunnel
tnl_0a24d960
Sun Jun 28 16:29:59 2020 daemon.err olsrd[6735]: Cannot add tunnel
tnl_0a24d960 to 10.36.217.96: File exists (17)
Sun Jun 28 16:29:59 2020 daemon.err olsrd[6735]: Cannot create tunnel
tnl_0a24d960
This was seen running OpenWrt (Freifunk "Firmware Berlin (Hedy 1.0.6)")
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#83>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABXRRN6TFPQRWZZA5L2HXKTRY5IXDANCNFSM4OKR3JNA>
.
|
Today I had some luck and found something in the logfile:
Up to some point the system works normal and changes the SmartGateway endpoint from time to time. For an unknown reason olsrd crashes then suddenly, and for this reason is not removing the established tunnel. |
First, the version of OLSRd used in Hedy-1-0-X is way old and I have not seen this happen with the latest stable release. Second, this is not a new problem, which was fixed in openwrt/luci@5d0b720 and openwrt/luci@667f73a way back in July 2018 So, for me the question is: Why aren't these changes in the Hedy-1.0.6 release? The original freifunk issue is freifunk-berlin/firmware#522 |
I have not checked the code, but I assume the initial problem is still there. When the tunnel can not be setup, as it's already there, the daemon will flood the logfile with messages about this. So probably the handling of such situations should be rethought.
Obviously it was never cherry-picked / backported to the 17.01 branch. |
I've gone to great lengths in the code to always clean up the tunnels. Only on rare occasions (e.g. very hard crashes in which the exit handler is not called) can this still occur. I strongly suggest you upgrade olsrd to the latest master. Edit: I also suggest to use the sgw script that is provided by olsrd (files/sgw_policy_routing_setup.sh) and not use your own script. That script is an integral part of sgw. |
As the very old olsr nodes, which prevented us to use more recent version (#20), have gone offline, an update can be rolled out. If the olsr-code also was improved here, the issue might be not such a show stopper and resource-sink anymore. Just had a short look into the olsrd-package (https://github.com/openwrt-routing/packages/tree/master/olsrd) and it seems that they also use the original sgw-script. |
On my node I was not able to access the internet via SmartGateway.
ip route
returned no default route even a Smartgateway was avail in the net (direct neighbour 10.36.217.96). I found the logfile full of following messages:This was seen running OpenWrt (Freifunk "Firmware Berlin (Hedy 1.0.6)")
The text was updated successfully, but these errors were encountered: