What kind of test case did you use? If you stop an interface and restart it while racoon is running, racoon has already bound to the IP address of the interface and will work, provided that the interface keeps the same address.
The problem occurs when racoon starts up while an interface is down for some reason and is started after racoon. This can easily happen on a laptop for the wireless interface when the airplane mode is engaged during boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972786 Title: racoon does not bind to interfaces brought up afterwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/972786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
