| 2010-05-10 06:48:07 |
Gombo Tsydynzhapov |
bug |
|
|
added bug |
| 2010-05-10 06:50:52 |
Gombo Tsydynzhapov |
branch linked |
|
lp:ubuntu/lucid/ifupdown |
|
| 2010-05-10 06:52:50 |
Gombo Tsydynzhapov |
description |
Binary package hint: upstart
After upgrading Ubuntu Server from 8.04 LTS to 10.04 LTS persistent mode dialing for pppd is broken.
I have a VPN setup over PPTP using pppd.
From syslog, after the connection is lost for whatever reason (here plug was disconnected):
pptp[986]: anon log[pptp_handle_timer:pptp_ctrl.c:1050]: closing control connection due to missing echo reply
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request'
pptp[986]: anon log[pptp_conn_close:pptp_ctrl.c:430]: Closing PPTP connection
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 3 'Stop-Control-Connection-Request'
pptp[986]: anon log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
pppd[954]: Modem hangup
pppd[954]: Connect time 3.0 minutes.
pppd[954]: Sent 18851 bytes, received 12102 bytes.
pppd[954]: Connection terminated.
pppd[954]: Terminating on signal 15
pppd[954]: Exit.
pppd exits and never tries to dial again.
The bug is apparently similar to #78043 and #396804, but now it is caused by pppd0 device being brought down by network-interface upstart job instead of udev.
Indeed, editing /etc/udev/rules.d/85-ifupdown.rules to exclude "remove" action completely has no effect, but editing last line of network-interface.conf to read
post-stop exec ifdown --allow hotplug $INTERFACE
work this bug around.
Probably, this is no solution, since in practice, as far as I understand, ifdown is never get called for any interface, but I don't know better. |
Binary package hint: upstart
After upgrading Ubuntu Server from 8.04 LTS to 10.04 LTS persistent mode dialing for pppd is broken.
I have a VPN setup over PPTP using pppd.
From syslog, after the connection is lost for whatever reason (here plug was disconnected):
pptp[986]: anon log[pptp_handle_timer:pptp_ctrl.c:1050]: closing control connection due to missing echo reply
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request'
pptp[986]: anon log[pptp_conn_close:pptp_ctrl.c:430]: Closing PPTP connection
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 3 'Stop-Control-Connection-Request'
pptp[986]: anon log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
pppd[954]: Modem hangup
pppd[954]: Connect time 3.0 minutes.
pppd[954]: Sent 18851 bytes, received 12102 bytes.
pppd[954]: Connection terminated.
pppd[954]: Terminating on signal 15
pppd[954]: Exit.
pppd exits and never tries to dial again.
The bug is apparently similar to https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/78043 and https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/78043, but now it is caused by pppd0 device being brought down by network-interface upstart job instead of udev.
Indeed, editing /etc/udev/rules.d/85-ifupdown.rules to exclude "remove" action completely has no effect, but editing last line of network-interface.conf to read
post-stop exec ifdown --allow hotplug $INTERFACE
work this bug around.
Probably, this is no solution, since in practice, as far as I understand, ifdown is never get called for any interface, but I don't know better.
|
|
| 2010-05-10 06:53:54 |
Gombo Tsydynzhapov |
description |
Binary package hint: upstart
After upgrading Ubuntu Server from 8.04 LTS to 10.04 LTS persistent mode dialing for pppd is broken.
I have a VPN setup over PPTP using pppd.
From syslog, after the connection is lost for whatever reason (here plug was disconnected):
pptp[986]: anon log[pptp_handle_timer:pptp_ctrl.c:1050]: closing control connection due to missing echo reply
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request'
pptp[986]: anon log[pptp_conn_close:pptp_ctrl.c:430]: Closing PPTP connection
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 3 'Stop-Control-Connection-Request'
pptp[986]: anon log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
pppd[954]: Modem hangup
pppd[954]: Connect time 3.0 minutes.
pppd[954]: Sent 18851 bytes, received 12102 bytes.
pppd[954]: Connection terminated.
pppd[954]: Terminating on signal 15
pppd[954]: Exit.
pppd exits and never tries to dial again.
The bug is apparently similar to https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/78043 and https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/78043, but now it is caused by pppd0 device being brought down by network-interface upstart job instead of udev.
Indeed, editing /etc/udev/rules.d/85-ifupdown.rules to exclude "remove" action completely has no effect, but editing last line of network-interface.conf to read
post-stop exec ifdown --allow hotplug $INTERFACE
work this bug around.
Probably, this is no solution, since in practice, as far as I understand, ifdown is never get called for any interface, but I don't know better.
|
Binary package hint: upstart
After upgrading Ubuntu Server from 8.04 LTS to 10.04 LTS persistent mode dialing for pppd is broken.
I have a VPN setup over PPTP using pppd.
From syslog, after the connection is lost for whatever reason (here plug was disconnected):
pptp[986]: anon log[pptp_handle_timer:pptp_ctrl.c:1050]: closing control connection due to missing echo reply
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request'
pptp[986]: anon log[pptp_conn_close:pptp_ctrl.c:430]: Closing PPTP connection
pptp[986]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 3 'Stop-Control-Connection-Request'
pptp[986]: anon log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
pppd[954]: Modem hangup
pppd[954]: Connect time 3.0 minutes.
pppd[954]: Sent 18851 bytes, received 12102 bytes.
pppd[954]: Connection terminated.
pppd[954]: Terminating on signal 15
pppd[954]: Exit.
pppd exits and never tries to dial again.
The bug is apparently similar to https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/78043 and https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/396804, but now it is caused by pppd0 device being brought down by network-interface upstart job instead of udev.
Indeed, editing /etc/udev/rules.d/85-ifupdown.rules to exclude "remove" action completely has no effect, but editing last line of network-interface.conf to read
post-stop exec ifdown --allow hotplug $INTERFACE
work this bug around.
Probably, this is no solution, since in practice, as far as I understand, ifdown is never get called for any interface, but I don't know better.
|
|
| 2010-05-11 07:00:19 |
Scott James Remnant (Canonical) |
affects |
upstart (Ubuntu) |
ppp (Ubuntu) |
|
| 2010-08-13 02:18:52 |
Craig Ringer |
bug task added |
|
ifupdown |
|
| 2010-08-24 05:37:32 |
Alexey Osipov |
bug |
|
|
added subscriber Alexey Osipov |
| 2010-08-24 06:04:12 |
Alexey Osipov |
bug task added |
|
ppp |
|
| 2010-08-24 06:05:58 |
Alexey Osipov |
ppp: status |
New |
Invalid |
|
| 2010-10-12 12:10:03 |
imagine |
bug |
|
|
added subscriber imagine |
| 2010-11-19 06:42:30 |
Alexey Osipov |
bug task added |
|
upstart |
|
| 2011-03-11 23:39:57 |
Scott James Remnant |
affects |
upstart |
null |
|
| 2011-03-13 10:09:54 |
imagine |
marked as duplicate |
|
78043 |
|
| 2011-07-25 20:25:09 |
Launchpad Janitor |
ppp (Ubuntu): status |
New |
Confirmed |
|
