The above script was slightly different to the one I have but I copied it and
made the mods as above. The errors in syslog have gone but I'm no further
forward. The OpenVPN connects, as before, but no data throughput.
Presumably the fix will come in the regular updates??
--
You received this bu
This bug was fixed in the package network-manager -
0.8.3+git.20101219t181118.e919218-0ubuntu1
---
network-manager (0.8.3+git.20101219t181118.e919218-0ubuntu1) natty; urgency=low
* upstream snapshot 2010-12-19 18:11:18 (GMT)
+ e91921814569bf9033fa0779837a77b22eb98e4a
- libnm
** Branch linked: lp:ubuntu/network-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661951
Title:
Incorrect /etc/NetworkManager/dispatcher.d/01ifupdown
--
ubuntu-bugs mailing list
ubuntu-bug
I suck, I obviously lost track of the original bug report -- the scripts
are still missing vpn-up and vpn-down handlers, so I've reopened and I
will upload another revision with this fixed after lunch ;)
** Changed in: network-manager (Ubuntu)
Status: Fix Released => In Progress
--
You re
This bug was fixed in the package network-manager -
0.8.3+git.20101209t061929.638fb18-0ubuntu1
---
network-manager (0.8.3+git.20101209t061929.638fb18-0ubuntu1) natty; urgency=low
* upstream snapshot 2010-12-09 06:19:29 (GMT)
+ 638fb1878019ac75617b653d13f4970af6e9c970
- core:
** Branch linked: lp:~network-manager/network-manager/ubuntu.head
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661951
Title:
Incorrect /etc/NetworkManager/dispatcher.d/01ifupdown
--
ubuntu-bugs m
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661951
Title:
Incorrect /etc/NetworkManager/dispatcher.d/01ifupdown
--
It seems that the scripts in /etc/NetworkManager/dispatcher.d would
still have been run, because the reason for the failures was the
addition of a "hostname" action to trigger dispatcher scripts on
hostname changes. Any other "standard" case would have just worked as
usual to run dispatcher scripts
I just tried the fix of adding
exit 0;
after line 33 of /etc/NetworkManager/dispatcher.d/01ifupdown
I am still getting the error
ubuntu nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status
1.
Not sure what to do stop the problem. Again, I wonder i
Would suggest increasing the priority a little, because it seems that if
the 01ifupdown script fails, other scripts in the
/etc/NetworkManager/dispatcher.d/
directory don't get run. Or perhaps the fault is will NetworkManager -
should it error out if one script stops working? New bug?
--
Incor
Looks reasonable, marking as Triaged/Low, and assigning myself.
** Changed in: network-manager (Ubuntu)
Assignee: Сергій Матрунчик (SkyMan) (skymanphp) => Mathieu Trudel
(mathieu-tl)
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubunt
also before every ending of "case" block it should be exit 0:
exec run-parts /etc/network/if-up.d
exit 0;
;;
without it the script causes an error.
--
Incorrect /etc/NetworkManager/dispatcher.d/01ifupdown
https://bugs.launchpad.net/bugs/661951
You received this bug notification because you are
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Сергій Матрунчик (SkyMan) (skymanphp)
--
Incorrect /etc/NetworkManager/dispatcher.d/01ifupdown
https://bugs.launchpad.net/bugs/661951
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
13 matches
Mail list logo
