Ticket #78 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Chillispot can't resolve uamserver address while starting

Reported by: pjf Assigned to: pjf
Priority: normal Milestone: 0.2rc1
Component: General networking Version: 0.2rc1
Severity: major Keywords:
Cc:

Description

Because rcS.d/S27chilli is started before rcS.d/S40staticrt, DNS query for resolving uamserver URL will fail. However, we need to leave such order because S27chilli creates a networking interface (what generally should be S2[0-9]*).

A possible workaround would be to modify Chillispot to try to resolve uamserver infinitely or to split it's startup into two parts: S27chilli just creates tun interfaces and eg. rc3.d/S??chilli starts the chilli daemon.

Change History

08/16/06 21:12:39 changed by pjf

  • milestone changed from 0.2 to 0.2rc1.

08/16/06 22:18:48 changed by pjf

  • status changed from new to closed.
  • resolution set to fixed.

Two possible workarounds implemented:

  • rcS.d/S27chilli uses openvpn (hack) to create interfaces,
  • rc3.d/S28chilli starts the actual service
  • chilli will try to resolve uamserver for about 5 mins before failing