Red Hat Bugzilla – Bug 220957
vpn network is not noticed by NetworkManagerDispatcher
Last modified: 2008-01-16 05:37:13 EST
Description of problem:
When openvpn interfaces are brought up, the NetworkManagerDispatcher scripts
aren't being run.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create an openvpn connection
2. Create a dummy NetworkManagerDispatcher script with side effects (i.e.
touches a file)
3. Start the openvpn interface
4. Verify (by lack of side effects) that dispatcher script did not run
NetworkManagerDispatcher scripts do not run for the 'tap0' device.
All NetworkManagerDispatcher scripts should be run for the openvpn device. I
would expect that the hook scripts would be run for any network device change,
physical or virtual.
This system has NetworkManager and NetworkManagerDispatcher running, with a few
dispatcher scripts installed. The hook scripts are being run for the non-vpn
device (eth0 or eth1) but not for the openvpn device tap0.
Have you tried this with Cisco VPN (vpnc) connections. This seems to be a
problem in the VPN subsystem to me, checking this with vpn could make us sure
about this. I'm going to have a look, too.
Sorry, this isn't something I can verify. I don't have access to a cisco vpn.
I am attempting to run a script based on NetworkManagerDispatcher seeing the
change to a VPN connection. When connecting with a wireless network on eth1
scripts run fine. However, when the openvpn connection on tun0 is up,
Dispatcher does not run.
It seems like this might be a feature request, to have a vpn connect/disconnect
hook similar to the existing hooks with Dispatcher.
Does this problem still exist on F-7/8? Have you had the chance to check with
vpnc. It seems to be a NM problem per se but before reassigning the component I
would like someone to check this.
Closing after long inactivity.