[MacPorts] #22872: aiccu - daemondo automatically restarts it, the reason why it exists is because something is broken.....

[MacPorts]

#22872: aiccu - daemondo automatically restarts it, the reason why it exists is
because something is broken.....
-----------------------+-------------------
  Reporter:  jeroen@…  |      Owner:  cr@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  1.8.1
Resolution:            |   Keywords:
      Port:  aiccu     |
-----------------------+-------------------

Comment (by fgp@…):

 Replying to [comment:6 jeroen@…]:
 > That is *NOT* correct. AICCU must *NEVER be restarted*

 This doesn't seem to be true. I've just tested this. Here's what I did

 1. `port install aiccu`

 2. Created `/opt/local/etc/aiccu.conf` and configured it for my SIXXS
 AYIAY tunnel

 2. I left the aiccu launchd service disabled, but did of course enable the
 tuntap service

 3. `aiccu start`

 4. Tunnel came up, works as expected

 5. I disabled WiFi and instead connected my phone over USB. OS X started
 using my phone's internet connection as expected (Using this connect to
 write this replay this very second, so it certainly works!)

 6. Tried pinging the other SIXXS tunnel endpoint, but no luck. aiccu logs
 the following once per minute
 {{{
   [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Can't
 assign requested address (49)
   [AYIYA-tundev->tun] : Error (-1) while sending 100 bytes to network:
 Can't assign requested address (49)
 }}}

 7. `aiccu stop`, `aiccu start`.

 8. Pinging the tunnel endpoint works again.

 So no, aiccu '''does not''' react to network changes correctly, at least
 not on OS X 10.9.5

 > Network changes is something that AICCU, or actually the protocols that
 it implements will handle and it does not need any restarts for network
 changes.

 Nope, unfortunately not! From the errors logged to `system.log`, my guess
 is that aiccu - for whatever reason - sets a source address for its
 socket(s), and fails to change it if that address is removed from the
 system. I haven't looked at the source to verify this, but it doesn't
 really matter anyway - fact is, never restarting aiccu means the tunnel
 will break if the primary interface changes!

 So we either need to patch AICCU to correct rebind its sockets (if that is
 indeed the problem here), or '''do''' restart it whenever the network
 configuration changes.

-- 
Ticket URL: <https://trac.macports.org/ticket/22872#comment:8>
MacPorts <https://www.macports.org/>
Ports system for OS X