IPv6 is gone after using network-manager with vpn

Hi! Please attach the file '/var/log/syslog' to the bug. Thanks

On Tue, 27 Nov 2007, Marco Rodrigues wrote:

> Hi! Please attach the file '/var/log/syslog' to the bug. Thanks
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => Low
> Status: New => Incomplete

I am sorry, but it was a while since I was on an IPv6 network with my
laptop and the logs have been deleted since. It is easy to replicate
if you are connected to an IPv6 network though.

--
patrik_wallstrom->foodfight-><email address hidden>->+46-733173956
http://pawal.blipp.com/

I've been experiencing this issue myself over the last few days...

Interestingly, it felt the need to withdraw the IP address from eth1 temporarily also, before putting it back shortly after.

It then felt the need to withdraw my public IPv6 address, register a link local address, and then remove that as well. ifconfig output at the bottom.

Note that this is IPv6 and VPN over wireless (eth1 is the wireless, eth0 is a 10/100 LAN port with nothing connected).

Hope it helps.

Jan 2 18:58:29 seven NetworkManager: <info> Will deactivate the VPN connection 'PIPE', service 'org.freedesktop.NetworkManager.ppp_starter'.
Jan 2 18:58:29 seven NetworkManager: <info> Clearing nscd hosts cache.
Jan 2 18:58:29 seven NetworkManager: <WARN> nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Jan 2 18:58:29 seven avahi-daemon[7192]: Withdrawing address record for 192.168.18.241 on eth1.
Jan 2 18:58:29 seven avahi-daemon[7192]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.18.241.
Jan 2 18:58:29 seven avahi-daemon[7192]: Interface eth1.IPv4 no longer relevant for mDNS.
Jan 2 18:58:29 seven avahi-daemon[7192]: Withdrawing address record for 2001:470:xxxx:17c:213:2ff:fecb:3300 on eth1.
Jan 2 18:58:29 seven avahi-daemon[7192]: Registering new address record for fe80::213:2ff:fecb:3300 on eth1.*.
Jan 2 18:58:29 seven avahi-daemon[7192]: Withdrawing address record for fe80::213:2ff:fecb:3300 on eth1.
Jan 2 18:58:29 seven avahi-daemon[7192]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.18.241.
Jan 2 18:58:29 seven avahi-daemon[7192]: New relevant interface eth1.IPv4 for mDNS.
Jan 2 18:58:29 seven avahi-daemon[7192]: Registering new address record for 192.168.18.241 on eth1.IPv4.
Jan 2 18:58:30 seven NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.ppp_starter' signaled state change 4 -> 5.
Jan 2 18:58:30 seven NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.ppp_starter' signaled state change 5 -> 6.
Jan 2 18:58:30 seven pppd[19495]: Terminating on signal 15
Jan 2 18:58:30 seven pppd[19495]: Child process /usr/sbin/pptp aaa.bbb.ccc.ddd --nolaunchpppd (pid 19496) terminated with signal 15
Jan 2 18:58:30 seven pppd[19495]: Connect time 0.5 minutes.
Jan 2 18:58:30 seven pppd[19495]: Sent 3597 bytes, received 4269 bytes.
Jan 2 18:58:30 seven pppd[19495]: MPPE disabled
Jan 2 18:58:30 seven pptp[19500]: anon log[callmgr_main:pptp_callmgr.c:255]: Closing connection (shutdown)
Jan 2 18:58:30 seven pptp[19500]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request'
Jan 2 18:58:30 seven pptp[19500]: anon log[call_callback:pptp_callmgr.c:78]: Closing connection (call state)
Jan 2 18:58:30 seven pppd[19495]: Modem hangup
Jan 2 18:58:30 seven pppd[19495]: Connection terminated.
Jan 2 18:58:30 seven pppd[19495]: Exit.

eth1 Link encap:Ethernet HWaddr 00:13:02:CB:33:00
          inet addr:192.168.18.241 Bcast:192.168.18.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
...

Hi Patrik
do you still experience this issue with the current version of the appication?, how do you obtain you IPv6 address, manually set or via a radvd server or similar?.

Thanks in advance

On Thu, 20 Mar 2008, Basilio Kublik wrote:

> Hi Patrik
> do you still experience this issue with the current version of the
> appication?, how do you obtain you IPv6 address, manually set or via
> a radvd server or similar?.

I am just about to upgrade to hardy. But yes, using autoconf, so if
it's radvd or some other router just works. Some are pushing to use
DHCPv6 but I haven't tried that yet.

During IETF71 during the hour without IPv4 connectivity,
network-manager just hung and waited for DHCP, so I had to manually
configure the interface (without network-manager) for IPv6. Do you
know if this has been fixed as well? I will try this during a workshop
next month.

--
patrik_wallstrom->foodfight-><email address hidden>->+46-733173956

On Thu, 20 Mar 2008, Basilio Kublik wrote:

> Hi Patrik
> do you still experience this issue with the current version of the
> appication?, how do you obtain you IPv6 address, manually set or via
> a radvd server or similar?.

It worked now using Hardy and network-manager 0.6.6-0ubuntu5.

--
patrik_wallstrom->foodfight-><email address hidden>->+46-733173956

this doesnt apply to latest NM in intrepid and doesnt qualify for a SRU.