Re: detecting resolv.conf changes
Howard Chu wrote: Date: Wed, 22 Apr 2009 17:55:29 -0400 From: Eric S. Johanssone...@harvee.org how do I detect that resolv.conf changes? I'm trying to fix a multiple name server problem by using dnsmasq as an intermediary and I need to keep resolv.conf pointing at localhost. See this post: http://mail.gnome.org/archives/networkmanager-list/2008-September/msg00042.html did these patches get incorporated into the mainline? If so, what version? given my previous successes with installing network manager from scratch (usually ending in a reinstall), I am reluctant to touch anything that requires patching. I'm going to experiment with and inotify based solution. That may be a little less destructive to my mental and laptop well-being. Thanks for the pointer though. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
detecting resolv.conf changes
how do I detect that resolv.conf changes? I'm trying to fix a multiple name server problem by using dnsmasq as an intermediary and I need to keep resolv.conf pointing at localhost. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problem with openvpn and dns
this isn't really a problem with network manager but that is where first manifested. The problem is that when open VPN is started, the far side DNS entry is added to resolv.conf and there in lies the problem. When the far side DNS server returns a NXDOMAIN which keeps the resolver from looking at the next name server. What the user experiences is that the only names to resolve are those coming from the far-side-of-the-VPN name server. I've encountered this problem on Mac and Linux systems and while it would be nice to find a solution with a resolver change, I'm looking at an alternative using dnsmasq because of having been burned by VMWare's less than ideal DHCP and DNS handling. Here's the path to madness. Install dnsmasq Set /etc/resolv.conf to the local dnsmasq (nameserver 127.0.0.1) *Tell network manager to store its information to /etc/resolv.conf.vpn Tell dnsmasq to read the server list from /etc/resolv.conf.vpn is it possible to tell network manager to store its information elsewhere? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
dns work arounds
running with ubuntu 8.04 and a crufty netmanager from last summer. my main problem is that the dns data from open vpn connections is ignored. a secondary problem is that routes are not handled correctly when switching between wifi and wired. since the latest netmanager won't compile on 8.04 (kernel too old), any ideas for workarounds? thanks --- eric ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: dns work arounds
(forgot to send to list) Marc Luethi wrote: On Wed, 2009-03-11 at 16:40 -0400, Eric S. Johansson wrote: since the latest netmanager won't compile on 8.04 (kernel too old), any ideas for workarounds? https://launchpad.net/~network-manager/+archive/ppa select hardy heron and find the right sources.list statements: deb http://ppa.launchpad.net/network-manager/ppa/ubuntu hardy main deb-src http://ppa.launchpad.net/network-manager/ppa/ubuntu hardy main That should word, I think regards W: GPG error: http://ppa.launchpad.net hardy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D702BF6B8C6C1EFD installed key -BEGIN PGP PUBLIC KEY BLOCK- Version: SKS 1.0.10 mI0ESXX0pgEEAMDSk9Vd+OWZNIa4dL2SpqFAjVq/hm4Nac2oc33g+BwP3jFajUC/quPnYXXl N7GER+tTHJ9d0PlXQDoRxXFRdSjZYUHDkiT8UV1I+sTxkjDaA7uMXD4dEcL0SG0nh6OyHHrd 9PrWzIZ/jS6PsYtKrKwHYCvP/igPr5/bH1PQoyZzABEBAAG0IUxhdW5jaHBhZCBQUEEgZm9y IE5ldHdvcmstbWFuYWdlcoi2BBMBAgAgBQJJdfSmAhsDBgsJCAcDAgQVAggDBBYCAwECHgEC F4AACgkQJI3R7ryOv+h8JQP+Ib07jYEiNG3PZf22xkV2rU/ybI9s4fT1CCoPJq5V3uJmouUs jtSXMD/9V44kFamw+Xq1EVEWeExfeABjaX7Vc9SR50Kl/DJVvBAbGs8rM2JxldQsl4sGWnTn AMJx/fv4iQsdyaklS3TcK6xo1yL21C4j0wYsmNxS16F28L3hRQ4= =8t/V -END PGP PUBLIC KEY BLOCK- used the text and video instructions. I've had this problem for months and when I wasn't able to resolve it, I deleted the repository and forgot about it till now. any idea why this problem persists? --- eric Marc ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
upgrading to 0.7
I apologize if this is a frequently asked question but I'm trying to upgrade to network manager 0.7 (Or later) on ubuntu 8.04. the last time I updated with some time last June with some .debs one of the developers created out of the svn tree. I've been trying to connect to the network manager repository but, the PGP key doesn't match (or so it seems). After following the instructions for key extraction and addition to the apt-get key ring, I get the following: W: GPG error: http://ppa.launchpad.net hardy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D702BF6B8C6C1EFD W: You may want to run apt-get update to correct these problems e...@first-triad:~/open-vpn-config$ in sources.list deb http://ppa.launchpad.net/network-manager/ppa/ubuntu hardy main deb-src http://ppa.launchpad.net/network-manager/ppa/ubuntu hardy main key retrieved -BEGIN PGP PUBLIC KEY BLOCK- Version: SKS 1.0.10 mI0ESXX0pgEEAMDSk9Vd+OWZNIa4dL2SpqFAjVq/hm4Nac2oc33g+BwP3jFajUC/quPnYXXl N7GER+tTHJ9d0PlXQDoRxXFRdSjZYUHDkiT8UV1I+sTxkjDaA7uMXD4dEcL0SG0nh6OyHHrd 9PrWzIZ/jS6PsYtKrKwHYCvP/igPr5/bH1PQoyZzABEBAAG0IUxhdW5jaHBhZCBQUEEgZm9y IE5ldHdvcmstbWFuYWdlcoi2BBMBAgAgBQJJdfSmAhsDBgsJCAcDAgQVAggDBBYCAwECHgEC F4AACgkQJI3R7ryOv+h8JQP+Ib07jYEiNG3PZf22xkV2rU/ybI9s4fT1CCoPJq5V3uJmouUs jtSXMD/9V44kFamw+Xq1EVEWeExfeABjaX7Vc9SR50Kl/DJVvBAbGs8rM2JxldQsl4sGWnTn AMJx/fv4iQsdyaklS3TcK6xo1yL21C4j0wYsmNxS16F28L3hRQ4= =8t/V -END PGP PUBLIC KEY BLOCK- thanks for any help ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: upgrading to 0.7
Alexander Sack wrote: you need to get to preferences - software sources - authentication and add the downloaded yet there to prevent those warnings from popping up. did that and I see an entry starting with: BC8EBFE8 2009-01-20 Still get the same error. --- eric ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
IP sec VPN
is a possible for net manager to manage IP sec VPNs? Every time I try to use the VPN dialog, it tells me I have no VPN software installed. This is very surprising as I have both IP sec and open VPN software installed. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IP sec VPN
Darren Albers wrote: On Sun, Aug 17, 2008 at 11:34 AM, Eric S. Johansson [EMAIL PROTECTED] wrote: is a possible for net manager to manage IP sec VPNs? Every time I try to use the VPN dialog, it tells me I have no VPN software installed. This is very surprising as I have both IP sec and open VPN software installed. The only IPSEC VPN supported are those supported by VPNC, there has been talk on the list of creating a VPN plugin for Openswan or something similar but AFAIK there has not been an releases. urk. racoon is bitching about a fatal parse error. probably something I did wrong when creating the initial configuration. In any case, I will take this off to the kvpnc mailing list. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Darren Albers wrote: On Mon, May 19, 2008 at 8:17 AM, Alexander Sack [EMAIL PROTECTED] wrote: On Mon, May 19, 2008 at 07:23:30AM -0400, Darren Albers wrote: Check out the howto at the link I posted, you need to install libdbus-glib-1-dev and libdbus-glib-2-dev The proper depends of nm 0.7 for hardy should already be in the PPA of the ubuntu network-manager team: https://edge.launchpad.net/~network-manager/+archive Remember to get the wpasupplicant from there as well. - Alexander I also should have clarified that you didn't need all the development packages if you don't plan on building VPN plugins. I didn't realize that you had already packaged wpa_supplicant so I will update my notes to use that package instead. I know that you are busy, but do you have plans to start building snapshots of NM 0.7? Having tried putting all the pieces together from what people said here, all I can say is ouch. While it is most definitely no blame, please don't inflict these .deb on any other poor sod that happens to come along. Why? it's trivially easy, in fact almost guaranteed to end up in the condition where you have no network connectivity whatsoever. if you aren't comfortable with editing /etc/network/interfaces, it will be most unpleasant. DHCP requests are sent, received, and ignored. This is true for both WiFi and ethernet. Adding a static ethernet configuration requires rebooting the machine before it is seen. The user interface for adding a static IP configuration would only be seen as good by geek tab (temporarily able-bodied). Field selection, visual feedback, and ease with which you can lose what you just typed in all work against the user. I've attached a cut down version of syslog. I apologize for its chaos but I was flailing about trying desperately to get an ethernet connection back so I could tell you about how unpleasant experience had been. :-) Let me know what you have another set of .deb for me to test and what, if any, I should remove. Once a test crash dummy, always a test crash dummy. (I wonder if I can get my library to give me an ethernet cable instead of WiFi?) May 19 18:00:44 first-triad NetworkManager: info (eth0): device state change: 1 - 2 May 19 18:00:44 first-triad NetworkManager: info (eth0): bringing up device. May 19 18:00:44 first-triad kernel: [ 41.356740] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX May 19 18:00:44 first-triad NetworkManager: info (eth0): preparing device. May 19 18:00:44 first-triad NetworkManager: info (eth0): deactivating device. May 19 18:00:44 first-triad kernel: [ 41.356747] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO May 19 18:00:44 first-triad kernel: [ 41.356840] ADDRCONF(NETDEV_UP): eth0: link is not ready May 19 18:00:44 first-triad kernel: [ 41.356843] bridge-eth0: enabling the bridge May 19 18:00:44 first-triad kernel: [ 41.356847] bridge-eth0: up May 19 18:00:44 first-triad kernel: [ 41.359114] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready May 19 18:00:44 first-triad NetworkManager: info (wlan0): device state change: 1 - 2 May 19 18:00:44 first-triad NetworkManager: info (wlan0): bringing up device. May 19 18:00:44 first-triad kernel: [ 41.362583] ACPI: PCI Interrupt :05:00.0[A] - GSI 19 (level, low) - IRQ 19 May 19 18:00:44 first-triad kernel: [ 41.362706] PM: Writing back config space on device :05:00.0 at offset 1 (was 12, writing 16) May 19 18:00:45 first-triad vmnet-dhcpd: Configured subnet: 192.168.253.0 May 19 18:00:45 first-triad vmnet-dhcpd: Setting vmnet-dhcp IP address: 192.168.253.254 May 19 18:00:45 first-triad vmnet-dhcpd: Recving on VNet/vmnet8/192.168.253.0 May 19 18:00:45 first-triad vmnet-dhcpd: Sending on VNet/vmnet8/192.168.253.0 May 19 18:00:45 first-triad kernel: [ 41.491344] /dev/vmnet: open called by PID 5962 (vmnet-dhcpd) May 19 18:00:45 first-triad kernel: [ 41.491367] /dev/vmnet: port on hub 8 successfully opened May 19 18:00:45 first-triad kernel: [ 41.497347] /dev/vmnet: open called by PID 5982 (vmnet-natd) May 19 18:00:45 first-triad kernel: [ 41.497367] /dev/vmnet: port on hub 8 successfully opened May 19 18:00:45 first-triad kernel: [ 41.512666] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels May 19 18:00:45 first-triad kernel: [ 41.516681] Registered led device: iwl-phy0:RX May 19 18:00:45 first-triad kernel: [ 41.516713] Registered led device: iwl-phy0:TX May 19 18:00:45 first-triad NetworkManager: info (wlan0): preparing device. May 19 18:00:45 first-triad kernel: [ 41.524146] ADDRCONF(NETDEV_UP): wlan0: link is not ready May 19 18:00:45 first-triad NetworkManager: info (wlan0): deactivating device. May 19 18:00:45 first-triad NetworkManager: info (eth0): carrier now ON (device state 2) May 19 18:00:45 first-triad NetworkManager: info (eth0): device state change: 2 - 3 May 19 18:00:45 first-triad
Re: netmanager problems with ubuntu 8.04
Dan Williams wrote: Looks like there might be Debian-style D-Bus permission issues with the nm-dhcp.action callout's dbus config files disallowing it from sending NetworkManager the returned DHCP configuration. What's the contents of your /etc/dbus-1/system.d/nm-dhcp-client.conf file? !DOCTYPE busconfig PUBLIC -//freedesktop//DTD D-BUS Bus Configuration 1.0//EN http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd; busconfig policy user=root allow own=org.freedesktop.nm_dhcp_client/ allow send_interface=org.freedesktop.nm_dhcp_client/ /policy policy context=default deny own=org.freedesktop.nm_dhcp_client/ deny send_interface=org.freedesktop.nm_dhcp_client/ /policy /busconfig ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Darren Albers wrote: In the short-term set the two deny's at the bottom to permit. It will get DHCP working and maybe Dan or someone can help us figure out what the proper permissions are. that was actually part of the original instructions but for some reason my calibrated eyeball diff failed. Now I can access my open access point and I will try it tomorrow on a wep protected one. Unfortunately, adding open VPN connections don't seem to work at all. I can make do with a CLI invocation in the host OS in the meantime. I may need to play some games to give the guest OSs access to the same open VPN connection but that's my problem. How much commentary do people want on user interface issues? I am disabled and as a result am highly sensitive to bad user interfaces. the current user interface failed me miserably because 1) I had to type, and 2) my exceedingly clumsy typing caused the user interface to fail in ways that forced me to go back to the beginning multiple times. This process cost me a good deal of physical pain. you can't do much about 1 because NaturallySpeaking is barely usable under wine. With any luck, that will change of the next year but right now, it's not so good if you need full function speech recognition under Linux[1]. But 2, that we can do something about. We can minimize typing and the user interface flow can make failures a little less painful. ---eric [1] no, don't mention Sphinx, don't mention Julius, don't mention HTK or any other speech recognition product whose primary goal is to give graduate students something to do and write a paper about. They don't work, have large enough vocabularies, or sufficient language modeling not to mention user interfaces or integration to an authoring systems/applications. Yes, I do get very cranky on this topic. :-) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: netmanager problems with ubuntu 8.04
Kenneth Crudup wrote: On Sun, 18 May 2008, Eric S. Johansson wrote: ... but ends up with me trying networkmanager 0.7. must say that with backported modules, wifi works great again. I am most grateful. What did you do?! I've been unable to get it to work from the SVN. didn't use svn. not that much of a masochist. back port modules info here http://linuxtechie.wordpress.com/2008/04/24/making-intel-wireless-3945abg-work-better-on-ubuntu-hardy/ network manager 0.7 info from here http://ubuntuforums.org/showthread.php?t=676992 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
netmanager problems with ubuntu 8.04
the tale starts with a wifi incompatability (3945ABG) and takes many twists and turns but ends up with me trying networkmanager 0.7. must say that with backported modules, wifi works great again. I am most grateful. but... openvpn is not working. I just find the message in syslog: May 18 00:15:06 first-triad kernel: [15356.397874] nm-vpn-properti[5374]: segfault at eip b6d6e507 esp bfae1390 error 6 after vpn configurations - configure vpn - +add - create vpn connection - forward (twice) and error 6. google didn't yield any useful results. ideas on what I should try? --- eric ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
