I see what appears to be a similar bug posted in the Debian tracker with
an upstream fix.
01ifupdown errs out on vpn connection change events
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518530
--
[8.10] Error: Failed to set IPv4 route
https://bugs.launchpad.net/bugs/294394
You received this
I am seeing the same nm-dispatcher ifupdown error in Lucid when I try to
connect to my university's VPN. It is able to connect and receives all
of the routes but no traffic passes to the remove network.
May 12 10:12:07 sps31-728-ckr1 NetworkManager: Policy set 'Auto eth0'
(eth0) as default for
Ok, i think this problem is related to my router.
When changing to another network the problem goes away. I have tried two
other home networks and the vpn functions correctly. Therefore i
conclude it is not an ubuntu/vpnc/networkmanager issue.
--
[8.10] Error: Failed to set IPv4 route
https://bu
Sorry maybe this is more useful for the routes with ip address and not
hostname...
before:
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
0.0.0.0 192.168.1.1 0.0.0.0 UG
Still present in 9.10 after upgrading except now the VPN no longer seems
to function and allow me to connect. All is the same at the other end of
the VPN and I'm pretty sure it is configured the same as it always was
in network manager at my end.
route before vpn:
Destination Gateway G
Hi,
Are you still experiencing this issue? Please see if this can be
reproduced with the current release of Ubuntu (9.10).
Stefano, please post the routes as shown by 'netstat -rn' when connected
to the VPN and when not connected, as well as and excerpt of
/var/log/syslog (with any sensitive info
** Changed in: network-manager-vpnc (Ubuntu)
Status: Incomplete => New
--
[8.10] Error: Failed to set IPv4 route
https://bugs.launchpad.net/bugs/294394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
On Sun, Dec 28, 2008 at 7:37 PM, Alexander Sack wrote:
> Stefano wrote:
> > No, it does not.
> > The interface at the end of the overall process is still ath0 and not
> tun0.
> >
> >
> please attach your /etc/NetworkManager/nm-system-settings.conf and your
> /etc/network/interfaces files here.
>
Stefano wrote:
> No, it does not.
> The interface at the end of the overall process is still ath0 and not tun0.
>
>
please attach your /etc/NetworkManager/nm-system-settings.conf and your
/etc/network/interfaces files here.
status incomplete
Thanks!
** Changed in: network-manager-vpnc (Ubu
No, it does not.
The interface at the end of the overall process is still ath0 and not tun0.
On Sat, Dec 27, 2008 at 7:02 PM, Alexander Sack wrote:
> Stefano wrote:
> > ** Changed in: network-manager-vpnc (Ubuntu)
> >Status: New => Confirmed
> >
> >
> Is this fixed in latest intrepid pac
Stefano wrote:
> ** Changed in: network-manager-vpnc (Ubuntu)
>Status: New => Confirmed
>
>
Is this fixed in latest intrepid packages available in ~network-manager
team PPA (http://launchpad.net/~network-manager/+archive)?
--
[8.10] Error: Failed to set IPv4 route
https://bugs.launchpa
** Changed in: network-manager-vpnc (Ubuntu)
Status: New => Confirmed
--
[8.10] Error: Failed to set IPv4 route
https://bugs.launchpad.net/bugs/294394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
I confirm.
There is that last error about the dispatcher and I can somehow get the pid
file to be written by creating the vpnc directory and changing its permissions.
--
[8.10] Error: Failed to set IPv4 route
https://bugs.launchpad.net/bugs/294394
You received this bug notification because you a
13 matches
Mail list logo
