Modify

Opened 8 years ago

Closed 6 years ago

Last modified 4 years ago

#7629 closed defect (fixed)

Aiccu should not be restarted when wan interface startup

Reported by: Laurent Bigonville <l.bigonville@…> Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:

Description

Hi,

Currently aiccu daemon is restarted when the wan interface is brought up. After some connectivity issues, aiccu has been restarted more than 5times in an hour, resulting in my sixxs account being blocked.

Please remove the hotplug rule causing aiccu to be restarted.

Attachments (0)

Change History (11)

comment:1 Changed 7 years ago by Laurent Bigonville <l.bigonville@…>

Any progress on this?

comment:2 Changed 7 years ago by anonymous

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

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

Fixed in r28219. Thanks!

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

Replying to acinonyx:

Fixed in r28219. Thanks!

That should be checked in also to Backfire's packages_10.03.1 branch.

comment:5 Changed 6 years ago by jow

Already is in r28220

comment:6 Changed 6 years ago by falstaff

  • Resolution fixed deleted
  • Status changed from closed to reopened

This is a bad fix. When the provider is reconnecting my PPPoE connection (which he does once a day) the Aiccu tunnel connection is broken afterwards. When I reconnect my interface (manually) too!

logread shows this when I reconnect my WAN connection:

Oct  6 14:57:59 netgear local7.err syslog: Already running instance HUP'ed, exiting

This is because we issue just a start. But because aiccu is still running, it doesn't reconnect's the tunnel through the new WAN connection...

Either one should fix the connectivity issues to avoid getting blocked or we should implement a logic which counts reconnect's and stops reconnecting after a given threshold...

comment:7 Changed 6 years ago by acinonyx

AICCU is supposed to automatically restore the tunnel when the WAN gateway changes. There is no need to restart it every time the PPPoE connection is restarted.

comment:8 Changed 6 years ago by anonymous

Hm, this does not work for me, I get this message after restarting the PPPoE connection:

<code>
Oct 7 13:18:35 netgear local7.err syslog: [AYIYA-tundev->tun] : Error (-1) while sending 148 bytes to network: Invalid argument (22)
</code>

comment:9 Changed 6 years ago by falstaff

Ok, I looked through the big AICCU documentation... (that is "the code")

The command aiccu_beat is doing the hartbeat (in common/aiccu.c). Either the command heartbeat_beat (common/heartbeat.c) is called for 6in4 tunnels, or the command ayiya_beat (common/ayiya.c) for AYIYA tunnels (which my tunnel is using). I looked through the functions, the latter seems not to have a reconnecting logic.

Either a patch is needed for solving this for AYIYA tunnel (which would be the nicer solution) or we do the restart workaround...

comment:10 Changed 6 years ago by acinonyx

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

Should be fixed in r28727 by enabling 'restart' option

comment:11 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.