Modify

Opened 6 years ago

Closed 5 years ago

Last modified 4 years ago

#10241 closed defect (wontfix)

AICCU problem when PPPoE reconnects

Reported by: ferob Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: aiccu tunnel pppoe ayiya Cc:

Description

Since r28219 AICCU does not work as expected.
And this fix solves nothing, because when the provider reconnecting the PPPoE connection (usually every 24 hours) the tunnel connection is broken afterwards. And because AICCU is still running, it doesn't reconnects the tunnel.

AICCU is supposed to automatically restore the tunnel when the WAN gateway reconnects, but after that it only works with static tunnels.

So if you use AYIYA tunnel and you leave it without a restart, then this error message spams the log:

Oct 16 20:55:11 Netgear local7.err syslog: [AYIYA-tundev->tun] : Error (-1) while sending 112 bytes to network: Invalid argument (22)
Oct 16 20:55:11 Netgear local7.err syslog: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)

Before r28219 the issued restart was okay with AYIYA tunnels, but it was not really a good method, because it should avoid getting blocked (because of the restarts). And you could accidentally restart the tunnel a few times when configuring the router, tuning some other things or just some other random PPPoE reconnects, because of the provider.

After looking through the source it seems that there is no reconnecting logic, because AICCU using a connected UDP socket for AYIYA and heartbeat traffic.

Some workaround is needed on the hotplug script (or maybe a patch would be the best) for solving this for AYIYA tunnels.

Attachments (0)

Change History (6)

comment:1 follow-up: Changed 6 years ago by acinonyx

  • Resolution set to duplicate
  • Status changed from new to closed

Should be fixed in r28727 by enabling 'restart' option

comment:2 Changed 6 years ago by anonymous

You might add the 'restart' option to the model config:
https://dev.openwrt.org/browser/packages/ipv6/aiccu/files/aiccu.conf

comment:3 in reply to: ↑ 1 Changed 6 years ago by anonymous

  • Resolution duplicate deleted
  • Status changed from closed to reopened

It not seems to work.
And now if the ip changes and I do a '/etc/init.d/aiccu restart' it does nothing.

Nov  5 15:13:22 Netgear local7.err syslog: Already running instance HUP'ed, exiting
Nov  5 15:13:23 Netgear local7.err syslog: [AYIYA-tundev->tun] : Error (-1) while sending 112 bytes to network: Invalid argument (22)
Nov  5 15:13:23 Netgear local7.err syslog: [AYIYA-tundev->tun] : Error (-1) while sending 112 bytes to network: Invalid argument (22)
Nov  5 15:13:23 Netgear local7.err syslog: [AYIYA-tundev->tun] : Error (-1) while sending 112 bytes to network: Invalid argument (22)

comment:4 Changed 6 years ago by Matthew Wire <devel@…>

There needs to be a delay in the restart function and restart must be enabled in the config file.

I have sent the following patch to the developers which solves the problem for me:

Signed-off-by: Matthew Wire <devel@mrwire.co.uk>
Index: ipv6/aiccu/files/aiccu.init
===================================================================
--- ipv6/aiccu/files/aiccu.init	(revision 30618)
+++ ipv6/aiccu/files/aiccu.init	(working copy)
@@ -59,6 +59,7 @@
 	local cfg="$1"
 	config_get_bool restart "$cfg" restart 0
 	[ "$restart" -eq 1 ] && stop_instance "$cfg"
+	sleep 5
 	start_instance "$cfg"
 }
 
Index: ipv6/aiccu/files/aiccu.config
===================================================================
--- ipv6/aiccu/files/aiccu.config	(revision 30618)
+++ ipv6/aiccu/files/aiccu.config	(working copy)
@@ -9,3 +9,4 @@
 	option defaultroute	'1'
 	option nat		'1'
 	option heartbeat	'1'
+	option restart		'1'

comment:5 Changed 5 years ago by jogo

  • Resolution set to wontfix
  • Status changed from reopened to closed

Aiccu init scripts and configs have been removed in r32666 (see commit log for the reasons).

comment:6 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.