https://bugzilla.novell.com/show_bug.cgi?id=781692 https://bugzilla.novell.com/show_bug.cgi?id=781692#c1 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-gnome@forge.provo. |bnc-team-screening@forge.pr |novell.com |ovo.novell.com --- Comment #1 from Dominique Leuenberger 2012-11-08 08:55:19 UTC --- Sorry, I don't like the bug bounce game, but vpnc is not maintained by the gnome team, so the assignee is clearly wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=781692 https://bugzilla.novell.com/show_bug.cgi?id=781692#c2 Steve Revilak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |steve@srevilak.net --- Comment #2 from Steve Revilak 2012-11-21 01:57:01 UTC --- I've experienced the same issue on 12.2. After bringing up a vpnc tunnel, /etc/resolv.conf is NOT updated with the resolver configuration sent by the vpnc server. I'm starting vpnc with the following command line: $ sudo vpnc FOO Where `FOO' corresponds to the configuration file /etc/vpnc/FOO.conf. vpnc sets up the connection: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enter password for srevilak@vpnc.example.org: vpnc version 0.5.3 IKE SA selected psk+xauth-3des-sha1 NAT status: no NAT-T VID seen got address 192.168.2.10 IPSEC SA selected 3des-md5 VPNC started in background (pid: 3745)... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By this point, OpenSUSE 12.1's vpnc would have re-written /etc/resolv.conf, such that the first few lines are ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #@VPNC_GENERATED@ -- this file is generated by vpnc # and will be overwritten by vpnc # as long as the above mark is intact ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ and the last few line contain `nameserver' and `search' directives sent by the vpnc server. By contrast, OpenSUSE 12.2's vpnc does not change resolv.conf. In my experience, both vpnc versions (OpenSUSE 12.1 and 12.2) apply routes from the vpnc server (i.e., after setting up a tunnel you can run "route -n" and see a different set of routing information.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=781692 https://bugzilla.novell.com/show_bug.cgi?id=781692#c Steve Revilak changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|vpnc does not update |vpnc does not modify |network routing properly |/etc/resolv.conf after | |setting up a tunnel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=781692 https://bugzilla.novell.com/show_bug.cgi?id=781692#c4 --- Comment #4 from Steve Revilak 2012-11-23 19:21:47 UTC --- I'd like to provide some additional information. As of this morning, I have OpenSUSE 12.2 installed on two machines, and both are using the same vpnc configuration files. One exhibits the behavior described in this bug. The other does not. The machine that DOES NOT exhibit this behavior (which I'll call the "good machine") has NetworkManager disabled, via NETWORKMANAGER="no" in /etc/sysconfig/network/config. The machine that DOES exhibit this behavior (which I'll call the "bad machine") has NETWORKMANAGER="yes". This may not be the root cause, but it seems like an obvious configuration difference between the two machines. vpnc-script has a series of conditional statements, where it chooses a strategy for how to modify resolv.conf (lines 91--103). OpenSUSE 12.2 added one additional case ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ elif [ -x /sbin/netconfig ]; then # tool on Suse after 11.1 MODIFYRESOLVCONF=modify_resolvconf_suse_netconfig RESTORERESOLVCONF=restore_resolvconf_suse_netconfig ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If I comment out these three lines, then /etc/resolv.conf is set up properly. To me, this implies some sort of issue with modify_resolvconf_suse_netconfig. modify_resolvconf_suse_netconfig does this: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /sbin/netconfig modify -s vpnc -i "$TUNDEV" <<-EOF INTERFACE='$TUNDEV' DNSSERVERS='$INTERNAL_IP4_DNS' DNSDOMAIN='$CISCO_DEF_DOMAIN' EOF ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I've verified that the values of $TUNDEV, $INTERNAL_IP4_DNS and $CISCO_DEF_DOMAIN are correct for the vpnc server I'm connecting to. So, let's investigate netconfig. To investigate netconfig, I put the invocation into a separate shell script (my-netconfig), replaced the variables with the appropriate values for this vpnc server, and added a --verbose flag. Here's the --verbose output. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ $ sudo sh my-netconfig debug: lockfile created (/var/run/netconfig.pid) for PID 3278 debug: lockfile created debug: write new STATE file /var/run/netconfig//tun0/netconfig0 debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime debug: dns-resolver module called debug: Static Fallback debug: Use NetworkManager policy merged settings debug: exec get_dns_settings: /var/run/netconfig/NetworkManager.netconfig debug: get_dns_settings: service 'NetworkManager' => rank '1' debug: get_dns_settings: DNS_SEARCHLIST_1='local' debug: get_dns_settings: DNS_SERVERS_1='192.168.1.1' debug: exit get_dns_settings: /var/run/netconfig/NetworkManager.netconfig debug: write_resolv_conf: ' local ' ' 192.168.1.1 ' debug: No changes for /etc/resolv.conf debug: dns-bind Module called debug: dns-dnsmasq Module called debug: nis Module called debug: Static Fallback debug: Use NetworkManager policy merged settings debug: exec get_nis_settings: /var/run/netconfig/NetworkManager.netconfig debug: exit get_nis_settings: /var/run/netconfig/NetworkManager.netconfig debug: set_nisdomainname: eth0 118 debug: set_nisdomainname: => yes debug: set_nisdomainname: old[]=, new[118]= debug: format_yp_conf called with : debug: Using static fallback debug: format_static[0] called debug: No changes for /etc/yp.conf debug: nis domainname '' is up to date debug: ntp-runtime Module called debug: Static Fallback debug: Use NetworkManager policy merged settings debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig debug: get_ntp_settings: NTP_SERVER_LIST='' debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig $ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In this case, "bad machine" is using a Network Manager configuration called `home' with a (wired) static IP, a search domain of `local', and a dns server address of 192.168.1.1. I tried switching to a dhcp-based configuration; that did not make a difference -- netconfig does not want to overwrite resolv.conf. All though this is not a real solution, I can submit vpnc-script.patch as a WORKAROUND. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=781692 https://bugzilla.novell.com/show_bug.cgi?id=781692#c Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|coolo@suse.de |tittiatcoke@gmail.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=781692 https://bugzilla.novell.com/show_bug.cgi?id=781692#c7 --- Comment #7 from Steve Revilak 2014-02-12 00:51:35 UTC --- Hello Raymond, Thanks for checking back on the status of this issue. I no longer have access to Cisco VPN that would be accessed via vpnc (my employer switched to AnyConnect prior to November 2013). Consequently, I have no way of testing whether this issue still exists. That said, if you've got a PIX laying around and don't mind giving me a VPN login, I'd be happy to try it out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.