[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-07-31 Thread Launchpad Bug Tracker
[Expired for ipsec-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ipsec-tools (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu.

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-06-01 Thread Kaarle Ritvanen
I had a discussion on this issue with one of the upstream developers. According to him, racoon should observe the addition of a new IP address via a NETLINK socket, but this functionality is broken in versions prior to 0.8 causing it to fail with some configurations. He also mentioned that there

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-12 Thread James Page
** Changed in: ipsec-tools (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu. https://bugs.launchpad.net/bugs/972786 Title: racoon does not bind to interfaces brought up

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-12 Thread Marc Cluet
** Changed in: ipsec-tools (Ubuntu) Assignee: (unassigned) = Marc Cluet (lynxman) ** Changed in: ipsec-tools (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu.

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-12 Thread James Page
Hi Kaarle Thanks for taking the time to report this bug. I've been trying to reproduce your issue on 11.04 but at the moment I see racoon binding to new interfaces as they are started and stopped. This is with the default configuration. Is there anything in your config that would prevent this

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-12 Thread James Page
** Changed in: ipsec-tools (Ubuntu) Assignee: Marc Cluet (lynxman) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu. https://bugs.launchpad.net/bugs/972786 Title: racoon does not bind to

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-12 Thread Kaarle Ritvanen
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

Re: [Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-12 Thread James Page
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/04/12 16:15, Kaarle Ritvanen wrote: 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

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-03 Thread Kaarle Ritvanen
** Patch added: Suggested solution https://bugs.launchpad.net/bugs/972786/+attachment/2998333/+files/ipsec-tools-sighup-on-if-up.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu.

[Bug 972786] Re: racoon does not bind to interfaces brought up afterwards

2012-04-03 Thread Ubuntu Foundation's Bug Bot
The attachment Suggested solution of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch'