Re: Network Manager patched on Ubuntu Karmic 9.10
My big issue in Karmic is that I can't join "hidden" networks - even if I know the SSID and the passphrase. This seems to be a regression from the earlier versions of Ubuntu. I have seen reports of it on Launchpad, but so far the importance of the issue is "undetermined". I think it is fairly critical myself, but I don't get to vote. :-) Trey Nolen I have another one for Karmic, and I can do that as well. I've noticed that there does not seem to be any way to get it to pay any attention to an Ad-Hoc network. When I'm in range, the network appears in the knetworkmanager applet, but if I click on it, nothing happens (much the same as a hidden network did in a case we'd discussed in the past). I'm not sure what the debug info would say, but it should be interesting to find out. It looks like absolutely nothing happens at all. - -- _ _ _ _ ___ _ _ _ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: VPN Suggestion
> > One suggestion for VPN settings is to have non-company IP traffic not route > > on the VPN by default. > > > > To accomplish this now you have to go to the IPv4 routes page which is > > buried 3 layers deep and select. > > "Use this connection only for resources on its network" > > > > I would suggest moving this to the VPN connection page and rename it > > something like. > > "Use this connection for resources on other networks" default to unchecked > > I might have this backwards but I disagree, this setting overwrites > whatever the server sends you so the default should be to respect what > the server sends. If someone wants that setting for all their users > let them set it on the server. Otherwise it will cause support issues > for people when some clients do not act as they are expected to act. > ___ I agree with the first post. In almost every instance, I have to drill down and check the "Use this connection only for resources on its network" selection. Windows acts like NM does by default, and you have to remove "Use default gateway on remote network". If NM wants to stay in line with what Windows is doing, that's fine, but I would respectfully ask that the option at least be put on the main config screen to reduce the number of clicks. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM and Nokia N95
It may be your provider. I use Verizon, and to make mine work, I had to edit the connection and enter a username/password. Verizon's is <10 digit TN>@vzw3g.com with a password of vzw. Some providers don't require a password, but yours might. Trey Nolen On Sun, 2009-09-13 at 22:47 +0100, Robert Piasek wrote: > Hi, > > I'm trying to connect my Nokia N95 using phonet driver and NM. Device is > picked up by kernel and properly initialized, but it doesn't connect due to > some problems with ppp. Please have a look on log below and let me know what > can be done to make it work. > > > Sep 13 22:40:26 [kernel] [39436.837937] usb 2-1.2: new full speed USB device > using ehci_hcd and address 10 > Sep 13 22:40:26 [kernel] [39436.930958] usb 2-1.2: New USB device found, > idVendor=0421, idProduct=0070 > Sep 13 22:40:26 [kernel] [39436.930966] usb 2-1.2: New USB device strings: > Mfr=1, Product=2, SerialNumber=0 > Sep 13 22:40:26 [kernel] [39436.930973] usb 2-1.2: Product: Nokia N95 8GB > > Sep 13 22:40:26 [kernel] [39436.930977] usb 2-1.2: Manufacturer: Nokia > > Sep 13 22:40:26 [kernel] [39436.931170] usb 2-1.2: configuration #1 chosen > from > 1 choice > Sep 13 22:40:26 [kernel] [39436.941261] cdc_acm 2-1.2:1.10: ttyACM1: USB ACM > device > Sep 13 22:40:28 [NetworkManager] (ttyACM1): found serial port > (udev:GSM hal:GSM)_ > Sep 13 22:40:28 [NetworkManager] (ttyACM1): new Modem device (driver: > 'cdc_acm')_ > Sep 13 22:40:28 [NetworkManager] (ttyACM1): exported as > /org/freedesktop/Hal/devices/usb_device_421_70_noserial_if0_0_serial_unknown_1_ > Sep 13 22:40:32 [NetworkManager] (ttyACM1): device state change: 1 -> > 2 (reason 2)_ > Sep 13 22:40:32 [NetworkManager] (ttyACM1): deactivating device > (reason: 2)._ > Sep 13 22:40:32 [NetworkManager] nm_ip4_config_add_nameserver: assertion > `nameserver != s' failed > Sep 13 22:40:32 [NetworkManager] Policy set 'Auto eth2' (eth2) as > default for routing and DNS._ > Sep 13 22:40:32 [NetworkManager] > nm_system_device_flush_ip4_routes_with_iface: > assertion `iface_idx >= 0' failed > Sep 13 22:40:32 [NetworkManager] > nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' > failed > Sep 13 22:40:32 [NetworkManager] (ttyACM1): device state change: 2 -> > 3 (reason 0)_ > Sep 13 22:40:44 [NetworkManager] Activation (ttyACM1) starting > connection 'Three'_ > Sep 13 22:40:44 [NetworkManager] (ttyACM1): device state change: 3 -> > 4 (reason 0)_ > Sep 13 22:40:44 [NetworkManager] Activation (ttyACM1) Stage 1 of 5 > (Device Prepare) scheduled..._ > Sep 13 22:40:44 [NetworkManager] Activation (ttyACM1) Stage 1 of 5 > (Device Prepare) started..._ > Sep 13 22:40:44 [NetworkManager] Invalid bits (0). Valid values are 5, 6, 7, > 8. > Sep 13 22:40:44 [NetworkManager] Invalid parity ( > Sep 13 22:40:44 [NetworkManager] Invalid stop bits (0). Valid values are 1 > and > 2) > Sep 13 22:40:44 [NetworkManager] Activation (ttyACM1) Stage 1 of 5 > (Device Prepare) complete._ > Sep 13 22:40:45 [NetworkManager] (ttyACM1): powering up..._ > Sep 13 22:40:45 [NetworkManager] Registered on Home network_ > Sep 13 22:40:45 [NetworkManager] Associated with network: +COPS: > 0,2,"23420",2_ > Sep 13 22:40:45 [NetworkManager] Connected, Woo!_ > Sep 13 22:40:45 [NetworkManager] Activation (ttyACM1) Stage 2 of 5 > (Device Configure) scheduled..._ > Sep 13 22:40:45 [NetworkManager] Activation (ttyACM1) Stage 2 of 5 > (Device Configure) starting..._ > Sep 13 22:40:45 [NetworkManager] (ttyACM1): device state change: 4 -> > 5 (reason 0)_ > Sep 13 22:40:45 [NetworkManager] Starting pppd connection_ > Sep 13 22:40:45 [NetworkManager] Activation (ttyACM1) Stage 2 of 5 > (Device Configure) complete._ > Sep 13 22:40:45 [pppd] Plugin /usr/lib64/pppd/2.4.4/nm-pppd-plugin.so loaded. > Sep 13 22:40:45 [pppd] pppd 2.4.4 started by root, uid 0 > Sep 13 22:40:45 [pppd] Baud rate for /dev/ttyACM1 is 0; need explicit baud > rate > Sep 13 22:40:46 [pppd] Exit. > Sep 13 22:40:46 [NetworkManager] ppp_exit_code(): ppp pid 9500 exited > with error: Fatal pppd error_ > Sep 13 22:40:46 [NetworkManager] (ttyACM1): device state change: 5 -> > 9 (reason 14)_ > Sep 13 22:40:46 [NetworkManager] Marking connection 'Three' invalid._ > Sep 13 22:40:46 [NetworkManager] Activation (ttyACM1) failed._ > Sep 13 22:40:46 [NetworkManager] (ttyACM1): device state change: 9 -> > 3 (reason 0)_ > Sep
Re: Multiple VPNs and resolvconf
Well, it will definitely cause problems with local name resolution (local to each VPN), but for the work we do, we are working with IPs most of the time anyway so that is not an issue. I could live with some resolv.conf issues if it would just connect. Trey Nolen On Mon, 2009-08-10 at 11:51 +0200, Dominik George wrote: > I'm not quite sure whether this is a problem. If nameserver A cannot > resolve a hostname, the system will try nameserver B automagically, then > nameserver C until it gets a result. > > This produces overhead while resolving names, but doesn't break the > resolver if there is more than one zone and more than one server. > > -nik > > Paul Wouters schrieb: > > On Sun, 9 Aug 2009, Trey Nolen wrote: > > > >> I would like to second this request. I frequently need more than one > >> concurrent VPN, and right now I have to do it using virtual machines. > > > > It's a bit of a hard problem to fix. The way most VPN DNS server swork, > > is they assume the VPN supplied DNS server can answer for both the > > internal > > DNS zones and the external world. So the laptop does not need any > > awareness of > > where to send which DNS query to. And the /etc/resolv.conf method is > > not really suitable for this. > > > > Now with two VPNs, and two different internal zones, what do you do? If > > you would add all VPN supplied nameservers, you will get inconsistent > > results. > > > > And it breaks when you as kfor internal.company1.com at company2.com's > > VPN DNS server (you would get the public ansewr, likely an NXDOMAIN). > > > > The real answer would be a provisioning system where you not only > > receive a DNS > > server entry, but also a name space for which that server is valid.aBut > > I don't think there is any DHCP option for that currently available. > > > > currently, the best solution would be to preconfigure the two DNS servers > > using a local resolving nameserver and specific forwarders, so you say > > for > > *.company1.com use this DNS, for *.company2.com use that DNS. > > > > Making unix systems smarter with respect to DNS(SEC) is very much needed > > but a work in progress. > > > > For unbound, this can be dynamically configured using unbound-control. In > > fact, if you would apply the nameserver to the given domain name from > > DHCP, > > you might get close in most cases. > > > > Paul > > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Multiple VPNs and resolvconf
I would like to second this request. I frequently need more than one concurrent VPN, and right now I have to do it using virtual machines. Trey Nolen On Sun, 2009-08-09 at 22:10 +0200, Dominik George wrote: > Hi list, > > are there plans for NetworkManager to support multiple VPNs > simultaneously? The applet currently only allows one VPN connection at a > time, I don't know if NM internally supports more. > > Furthermore, NetworkManager really should honour manual entries in > /etc/resolv.conf so VPN management is posible with other software (NM > will override entries made by OpenVPN, etc. every now and then). > > With kind regards, > Nik > > ___ > 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
Re: success story
> > > My GF got a verison card for her Mac. I can stick it in my linux box, > pick nm's "Auto Mobile Broadband (CDMA) connection" and it just > works. > > dmesg > > [22246.904627] usb 7-1: new full speed USB device using uhci_hcd and address 2 > [22247.115925] usb 7-1: configuration #1 chosen from 1 choice > [22248.061132] usbcore: registered new interface driver usbserial > [22248.061159] USB Serial support registered for generic > [22248.061259] usbcore: registered new interface driver usbserial_generic > [22248.061263] usbserial: USB Serial Driver core > > > [22248.073507] USB Serial support registered for GSM modem (1-port) > [22248.073641] option 7-1:1.0: GSM modem (1-port) converter detected > [22248.073797] usb 7-1: GSM modem (1-port) converter now attached to ttyUSB0 > [22248.073826] option 7-1:1.1: GSM modem (1-port) converter detected > [22248.073917] usb 7-1: GSM modem (1-port) converter now attached to ttyUSB1 > [22248.073943] usbcore: registered new interface driver option > [22248.073947] option: v0.7.2:USB Driver for GSM modems > [22345.117757] PPP BSD Compression module registered > [22345.125091] PPP Deflate Compression module registered This indicates that we can pull the phone number off the device and substitute it in the username for Verizon. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: success story
> Awesome, thanks for the rave :) Good to hear the success stories while > slaving away in the sausage factory :) > > TBH though, it's interesting that your configuration required the > username and password. Do you mind sharing that if it doesn't contain > any personal information? Sprint doesn't care what they are (they could > be guest/guest), I was under the assumption that Verizon didn't either. Verizon's username/password is: username: <10 digit phone number>@vzw3g.com pass: vzw Not sure how that could be automated much more unless there is some way to realize that the CDMA connection is actually a Verizon one. I guess we could prompt for carrier? Then, ask for the phone number if they pick Verizon. Also, it should be noted that I was using my phone. The dedicated USB/PCCard devices also have a phone number associated with them and use the same user/pass combo. Most people don't know the phone number associated with their USB device. I know that Verizon's software prompts for the number, but already has it filled in, so it is able to read it from somewhere in the device. Hope this helps. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
success story
Sorry for the partial message getting sent out. Here is the real message: I just wanted to take a minute of your time to relate a success story for network manager. I'm staying at a hotel where they charge for wifi (losers), but I have a Samsung i760 on Verizon with the tethering plan. When I last used it with my netbook, I had network manager .6. I used a PPP dialer to log onto the network. Now, I have Ubuntu's Netbook Remix which is based on Jaunty and it comes with NM .7. I was thinking that I still needed a dialer, and was trying to figure out how to get online to download one. I went ahead and plugged up my phone, and saw "Auto Mobile Broadband CDMA Connection"! I tried to use it, and it logged on but I couldn't surf. So, I edited the entry, and found the spot for my user/pass, etc. I put that in (fortunately, I knew it), and everything just worked! My wife has a Windoze laptop and she was jealous. I had to download Verizon Access Manager using my netbook so we could get her going. I love having the functionality built in. Anyway, enough time taken up. Great work guys! Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
success story
I just wanted to take a minute of your time to relate a success story for network manager. I'm staying at a hotel where they charge for wifi (losers), but I have a Samsung i7 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot connect to wpa/wpa2 network with hidden SSID
> 2009/2/27 Joshua C. > I cannot connect with the latest Networkmanager to any network > with > wpa/wpa2 that doesn't broadcast its name. Once the name is > revealed > there are no problems. This is on Fedora 11 and there's a bug > about it > here: https://bugzilla.redhat.com/show_bug.cgi?id=486877 > > Installed are: > NetworkManager-0.7.0.98-1.git20090225.fc11 > NetworkManager-gnome-0.7.0.98-1.git20090225.fc11 > NetworkManager-glib-0.7.0.98-1.git20090225.fc11 > wpa_supplicant-0.6.7-4.fc11 > wpa_supplicant-gui-0.6.7-4.fc11 > > > i had this problem some months ago. Then it was with f9/f10 > and it was > fixed later. but now it's back again. I also had (have) a similar problem on Ubuntu 9.04. However, it also happens when the SSID is not hidden. It seems to only happen when the AP will auto switch between WPA and WPA2. If I force the AP to pick one, it works OK. I'm not sure if this is rooted in the same issue. I'm afraid I haven't done much research into it to see if there are any previous bug reports. I just changed the setting on the AP and went on with life... Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: issue with pptp plugin
On Wed, 2009-06-17 at 08:11 -0500, Trey Nolen wrote: > > On Tue, 2009-06-16 at 15:40 +0200, Axel wrote: > > Le 15/06/2009 14:15, Trey Nolen a écrit : > > > Jun 15 07:09:57 stuggots NetworkManager: Maximum Segment Size > > > (MSS): 0 > > > > > > > It could be the problem. It seems that no MTU is defined. > > Once your VPN connection is established, try to type the command : "sudo > > ifconfig ppp0 mtu 1412" in a terminal and try again to create some > > traffic, like your remote desktop session. > > > > It may be related to this bug : > > http://bugzilla.gnome.org/show_bug.cgi?id=559116 , but from this bug : > > "Latest 0.7.1rc1 PPTP plugin uses 1400 as the default MTU." but your > > version looks like to be 0.7.1rc4. > > I found that bug, too. You may have missed one of my later emails where > I state that I have an MTU of 1400 when I am connected. Below is output > from ifconfig when I'm connected: > > ppp0 Link encap:Point-to-Point Protocol > inet addr:192.168.4.107 P-t-P:192.168.4.107 > Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 > RX packets:11 errors:0 dropped:0 overruns:0 frame:0 > TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:3 > RX bytes:291 (291.0 B) TX bytes:228 (228.0 B) > > > > > I did try your suggestion of changing the MTU to 1412, but it had no > effect. I run Hardy (Ubuntu 8.04) on another of my computers and I have > noticed that the inet address and the P-t-P address are different when > I'm connected to a VPN with it. Could that be a source of the issue? > Well, I know there wasn't much interest in this issue, but I finally resolved it so I figured I'd post the resolution anyway. At home, I was able to reproduce the problem with both my desktop and my laptop (both running Jaunty). I went to a restaurant that had wifi with my laptop and noticed that my VPNs would stay connected. So, I realized it had to be something on my home network. Since MTUs had been mentioned before (regarding the PPP interface), I adjusted those on my router, and it fixed the problem. Normally, when I have an MTU issue on a router connected to the internet, it results in problems with certain websites and/or slow speed on sites. I had neither of these issues, but the VPNs would drop and now do not. Maybe this will help someone else with this unusual issue. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: issue with pptp plugin
On Tue, 2009-06-16 at 15:40 +0200, Axel wrote: > Le 15/06/2009 14:15, Trey Nolen a écrit : > > Jun 15 07:09:57 stuggots NetworkManager: Maximum Segment Size > > (MSS): 0 > > > > It could be the problem. It seems that no MTU is defined. > Once your VPN connection is established, try to type the command : "sudo > ifconfig ppp0 mtu 1412" in a terminal and try again to create some > traffic, like your remote desktop session. > > It may be related to this bug : > http://bugzilla.gnome.org/show_bug.cgi?id=559116 , but from this bug : > "Latest 0.7.1rc1 PPTP plugin uses 1400 as the default MTU." but your > version looks like to be 0.7.1rc4. I found that bug, too. You may have missed one of my later emails where I state that I have an MTU of 1400 when I am connected. Below is output from ifconfig when I'm connected: ppp0 Link encap:Point-to-Point Protocol inet addr:192.168.4.107 P-t-P:192.168.4.107 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:291 (291.0 B) TX bytes:228 (228.0 B) I did try your suggestion of changing the MTU to 1412, but it had no effect. I run Hardy (Ubuntu 8.04) on another of my computers and I have noticed that the inet address and the P-t-P address are different when I'm connected to a VPN with it. Could that be a source of the issue? Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: issue with pptp plugin
On Mon, 2009-06-15 at 10:36 +0200, Axel wrote: > Le 13/06/2009 21:15, Trey Nolen a écrit : > > I'm running Ubuntu Jaunty using the network manager package that comes > > with the distro. It is version 0.7.1~rc.4.1-0ubuntu2. The > > network-manager-pptp package is version 0.7.1~rc.4.20090316 > > +bzr23-0ubuntu3. > > > > Would you post the log messages that seems to be related to your VPN > connection attempts ? (on fedora 11, you can find it in the > /var/log/messages file, it may be the same on ubuntu) Here you go: Jun 15 07:09:54 stuggots NetworkManager: VPN plugin state changed: 3 Jun 15 07:09:54 stuggots NetworkManager: VPN connection 'Test VPN' (Connect) reply received. Jun 15 07:09:54 stuggots pppd[4731]: Plugin /usr/lib/pppd/2.4.5//nm-pptp-pppd-plugin.so loaded. Jun 15 07:09:54 stuggots pppd[4731]: pppd 2.4.5 started by root, uid 0 Jun 15 07:09:54 stuggots pppd[4731]: Using interface ppp0 Jun 15 07:09:54 stuggots pppd[4731]: Connect: ppp0 <--> /dev/pts/2 Jun 15 07:09:54 stuggots pptp[4735]: nm-pptp-service-4482 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Jun 15 07:09:54 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Jun 15 07:09:54 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Jun 15 07:09:54 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Jun 15 07:09:55 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Jun 15 07:09:55 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Jun 15 07:09:55 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 5058). Jun 15 07:09:55 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_disp:pptp_ctrl.c:950]: PPTP_SET_LINK_INFO received from peer_callid 1 Jun 15 07:09:55 stuggots pptp[4743]: nm-pptp-service-4482 log[ctrlp_disp:pptp_ctrl.c:953]: send_accm is , recv_accm is Jun 15 07:09:55 stuggots pptp[4743]: nm-pptp-service-4482 warn[ctrlp_disp:pptp_ctrl.c:956]: Non-zero Async Control Character Maps are not supported! Jun 15 07:09:55 stuggots pppd[4731]: CHAP authentication succeeded Jun 15 07:09:55 stuggots pppd[4731]: MPPE 128-bit stateless compression enabled Jun 15 07:09:57 stuggots pppd[4731]: Cannot determine ethernet address for proxy ARP Jun 15 07:09:57 stuggots pppd[4731]: local IP address 192.168.4.109 Jun 15 07:09:57 stuggots pppd[4731]: remote IP address 192.168.4.115 Jun 15 07:09:57 stuggots pppd[4731]: primary DNS address 192.168.4.14 Jun 15 07:09:57 stuggots pppd[4731]: secondary DNS address 192.168.4.249 Jun 15 07:09:57 stuggots NetworkManager: VPN connection 'RealtyBid' (IP Config Get) reply received. Jun 15 07:09:57 stuggots NetworkManager: VPN Gateway: 0.0.0.0 Jun 15 07:09:57 stuggots NetworkManager: Tunnel Device: ppp0 Jun 15 07:09:57 stuggots NetworkManager: Internal IP4 Address: 192.168.4.109 Jun 15 07:09:57 stuggots NetworkManager: Internal IP4 Prefix: 32 Jun 15 07:09:57 stuggots NetworkManager: Internal IP4 Point-to-Point Address: 192.168.4.115 Jun 15 07:09:57 stuggots NetworkManager: Maximum Segment Size (MSS): 0 Jun 15 07:09:57 stuggots NetworkManager: Internal IP4 DNS: 192.168.4.14 Jun 15 07:09:57 stuggots NetworkManager: Internal IP4 DNS: 192.168.4.249 Jun 15 07:09:57 stuggots NetworkManager: DNS Domain: '(none)' Jun 15 07:09:57 stuggots NetworkManager: Login Banner: Jun 15 07:09:57 stuggots NetworkManager: - Jun 15 07:09:57 stuggots NetworkManager: (null) Jun 15 07:09:57 stuggots NetworkManager: - Jun 15 07:09:58 stuggots NetworkManager: (ppp0): writing resolv.conf to /sbin/resolvconf Jun 15 07:09:58 stuggots NetworkManager: VPN connection 'RealtyBid' (IP Config Get) complete. Jun 15 07:09:58 stuggots NetworkManager: (eth0): writing resolv.conf to /sbin/resolvconf Jun 15 07:09:58 stuggots NetworkManager: Policy set 'Auto eth0' (eth0) as default for routing and DNS. Jun 15 07:09:58 stuggots NetworkManager: VPN plugin state changed: 4 Jun 15 07:09:58 stuggots nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. --This is where it stops while the connection is connected. Then, after some traffic passes, you get: Jun 15 07:10:20 stuggots pptp[4735]: nm-pptp-service-4482 warn[decaps_gre:pptp_gre.c:331]: short read (-1): Message too long Jun 15 07:10:20 stuggots pptp[4743]: nm-pptp-service-4482 log[callmgr_main:pptp_callmgr.c:234]: Closing co
issue with pptp plugin
I'm running Ubuntu Jaunty using the network manager package that comes with the distro. It is version 0.7.1~rc.4.1-0ubuntu2. The network-manager-pptp package is version 0.7.1~rc.4.20090316 +bzr23-0ubuntu3. My PPTP VPNs get connected fine and traffic passes just like I want it to. The problem is that the VPN drops shortly after I'm connected. It seems to have something to do with the AMOUNT of traffic that goes through the VPN. For example, I can ping a machine on the remote network for a good while without dropping the connection, but if I bring up a remote desktop session, the VPN will almost immediately drop. If I log into, for example, the web interface on a router of the remote network, I can usually browser to two pages before the VPN drops. When the VPN drops, I get a "VPN Failed" notification in the Gnome notification window. It is almost like the VPN never FULLY establishes. The "VPN Failed" window is the same one I get if the VPN never connects at all. I'm using pretty much the stock options when creating the VPN, with a few exceptions: I specify a route for the remote network. I check "Use this connection only for resources on its network". I disable EAP authentication. I enable MPPE encryption and allow stateful encryption (have tried that both ways). If anyone has any ideas on how to get this functioning better, I welcome them. Thanks. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: VPN Default Route
On 1/2/09 7:44 AM, "Maxim Levitsky" wrote: > On Fri, 2009-01-02 at 13:37 +0100, Ermanno Bonifazi wrote: > I'm back on the > subject below. I have just upgraded to Ubuntu 8.10 > and find confusing that > creating a PPTP VPN all traffic is routed via > the VPN (this mean the default > gateway is set by an automatic policy > to the VPN pppx). > > Since I'm using > a mobile broadband modem and my PPTP VPN do not accept > all traffic but just > the VPN traffic, all the remaing Internet traffic > should go via the ppp0 (in > my case the mobile broadband) and not via > ppp1 (the VPN tunnell). > > If > you leave VPN with default setting, when a VPN is started the > default > gateway is automatically changed to VPN tunnel andf not the > the previous > default gw (the modem). > > > I was able to achieve this behavior going to > IPv4 setting, adding a > manual route for my VPN and checking the flag "Ignore > automatically > obtained routes". > > I believe this may be confusing > expecially for "standard user". I > believe something more similar to Windows > PPTP vpn ( a check "do not > use gateway on remote network) could be more > efficent, and will let > the user decide if they want to use the VPN as > default gw or the > previous set default ge (in my case the modem or the > WLAN). May be in > fact also difficult that user will know the route set by > the VPN > server to add this information in IPV4 routes tab of NM. > > So far > this is my understanding of the behavior, but looking on the > web, I've nof > found a different and simpler way to achieve the > behavior I mention. > > > Any suggestion or comment? > I think I missed part of this thread, but I agree that the default route behavior is not ideal. One thing that I think is important is that NM should restore the routes that were present when the VPN is disconnected. Currently, it only restores the default route, and if you had any others, they are lost and have to be manually re-setup. I¹ve noticed that a VPN to an IPv4 network even blows away my IPv6 routes. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: VPN doesn't work in Ibex
I, too, have seen this issue. I will try out those packages and let you know. Trey Nolen - Original Message - From: "Alexander Sack" <[EMAIL PROTECTED]> To: "Tor Fosnaes" <[EMAIL PROTECTED]> Cc: Sent: Sunday, November 16, 2008 9:01 AM Subject: Re: VPN doesn't work in Ibex On Sun, Nov 16, 2008 at 07:26:35AM -0330, Tor Fosnaes wrote: I have tried every possible workaround and solution from forum after forum after mailing list after blog and still NO GO. Regardless of settings and choices VPN will NOT connect to Windows PPTP server; all worked flawlessly under HERON. I have not tried reverting nm back to HERON; this seems counter-productive and probably result in even more problems. If anyone has a workaround, or if Canonical/Gnome has it fixed, please, please send me the URL as my VPN work waits. try the packages from http://launchpad.net/~network-manager/+archive Thanks, - Alexander ___ 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
RE: default route problem
> > > But, if you do, you can't use any VPNs. At least when I try it, all > my VPNs go away. If you have a method that works, please describe how. > > What exactly do you mean by "go away"? They disappear from the connection editor? Or they activate but the routing is wrong and traffic just > doesn't get through? Well, right now I've gone back to NM .6 because of issues I've discussed earlier, so I can't tell you exactly. But, as I recall, it was similar to the way that .6 acts, which is to say that if you change the settings, the whole VPN Connections menu disappears from the nm-applet. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: default route problem
On Mon, Oct 6, 2008 at 5:39 PM, Trey Nolen <[EMAIL PROTECTED]> wrote: On this same topic, Network Manager also removes any NON default routes that you have. I personally sometimes set different routes up for the internal network. These are NOT given out by DHCP, but when you connect/disconnect a VPN, those routes are blown away. I would LOVE for this to be addressed. You CAN go to the connection editor and ADD static routes to your connection. Tambet But, if you do, you can't use any VPNs. At least when I try it, all my VPNs go away. If you have a method that works, please describe how. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: multiple VPN (PPTP) connections at once
I would like to echo a need for this. I too thought that NM .7 would be capable of this and it was one of the reasons for me to try it out. Trey Nolen I never really had big trouble using the NetworkManager-0.6 but when I heard about that the NetworkManager-0.7 would have the capability to manage multiple active devices I instantly thought about my VPN (PPTP) connections; the usage within my linux environment was kinda annoying compared to the usage I knew from my XP desktop. At XP I can run multiple VPNs simultaneously so that I can manage different clients via RDP at once. I thought I could use them the same way with NM-0.7 now but unfortunately I still can only use a single VPN connection at once (at least by using the GUI). Is anybody working on that feature or can explain if something can be done? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: default route problem
On this same topic, Network Manager also removes any NON default routes that
you have. I personally sometimes set different routes up for the internal
network. These are NOT given out by DHCP, but when you connect/disconnect a
VPN, those routes are blown away. I would LOVE for this to be addressed.
Trey Nolen
On Mon, Oct 6, 2008 at 2:43 PM, Vitja Makarov <[EMAIL PROTECTED]>
wrote:
> DHCP provides default route, but when you bring pptp up, you may want
> to use ppp device as default route, e.g internet.
> Then if you'll replace default one with ppp, then you will loose route
> to pptp server.
>
> 2008/10/6 Stuart Ward <[EMAIL PROTECTED]>:
>> Am I missing something obvious, but shouldn't the DHCP server provide
>> the default route to the client.
>>
>> eg my dhcpd.conf
>>
>> subnet 192.168.0.0 netmask 255.255.255.0 {
>>option routers 192.168.0.4;
>>range 192.168.0.10 192.168.0.50;
>>option netbios-name-servers 192.168.0.2;#wins server
>> }
>>
>> Where 192.168.0.4 is the default router
>>
>> -- Stuart Ward M +44 7782325143
>>
>>
>>
>> On Mon, Oct 6, 2008 at 12:51 PM, Vitja Makarov <[EMAIL PROTECTED]>
wrote:
>>> Hi, all!
>>>
>>> Home ISP often use the following network configuration scheme:
>>>
>>> - Lan IP address is assigned using DHCP
>>> - PPTP is used for internet connection
>>>
>>> If pptp server is in your network, that should be ok to replace
>>> default route with ppp one, but when pptp server is routed via DHCP
>>> provided default route, you can't simply do it, you have first
>>> provide manually route for pptp server, then remove default.
>>>
>>> Can we solve a problem this way:
>>> - user should choose which networks he want to route using DHCP
>>> default route
>>> - then add pptp server to this list
>>> - build rules and change routing table
>>> - then remove default route, or increase metrics
>>> - launch pppd
>>> - if failed restore previous settings
>>>
>>>
>>> That should make pptp configuration less painful on linux desktop.
>>> That should be useful for all other kinds of PPP as well.
>>>
>>> I can provide some sample code in few days, using libnl.
>>>
>>> Thanks,
>>> vitja.
>>> ___
>>> NetworkManager-list mailing list
>>> NetworkManager-list@gnome.org
>>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>>>
>>
>
> vitja.
>
___
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
Re: dnsmasq
> How about a NM option to disable updating of resolv.conf. This > should be settable in 3 different places: > >-globally >-interface (wired/wireless) >-per manually configured connections > YES! Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: downgrade to 0.6.6 temporally?
downgrading in intrepid isnt really supported. We should figure out why it doesnt work for you. Have you looked in the "advanced ..." settings available for your pptp connection in nm-connection-editor? I had problems with about 50% of my PPTP connections when using .7, but NM didn't really give me any feedback on what the issue was. I checked the logs, but to no avail. Are there any debugging options that can be passed to the pptp plugin somehow? If so, I'll be glad to do some testing with my connections. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: downgrade to 0.6.6 temporally?
unfortunatly Im still unable to connect to our Windows 2003 VPN Server on my Intrepid machine. It worked on hardy and the bug is already filed at lp: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/259168 I wonder if I can downgrade only the network-manager to 0.6.6 untill this bug is fixed. I just tried to build it from source but got an error because my package wireless-tools isn't the right one that was expected for that network-manager version. How could I work around it...I don't won't to destabilise my system but I want to get my VPN to work :-) Well, I'm not running Intrepid yet, but I did upgrade to NM .7 on Hardy and had problems with it. I successfully downgraded to .6.6 and fixed my issues (most of them anyway). It is kind of a pain to downgrade, but it can be done. I did have one problem after downgrading though - I was unable to create *new* VPNs. I already had some created before upgrading to .7 and those work OK, but I could not get new ones configured after the switch. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: problem with pptp plugin
>>On Thu, 2008-09-18 at 12:44 -0500, Trey Nolen wrote: >> I do a lot of work with PPTP VPNs. I have over 100 on my workstation. I >> had upgraded to NM .7 for some of the features it had, but it had a lot >> of problems that were showstoppers for me. So, I reverted back to m > >What sorts of issues did you have with the 0.7 plugin? The first thing was that I had over 100 existing connections that didn't come over with the upgrade to .7. I can recreate them, though, so that wasn't too bad in of itself. The biggest problem I had was that it seemed that only about 50% of my connections would work. It seemed that if they didn't work the first time (for whatever reason - password wrong, username wrong, config error, etc), they would NEVER work. Even after the issue was corrected. On some of the ones that wouldn't connect I couldn't determine a reason. However, those same connections work with the .6.6 version. This was a showstopper because I had no way of connecting to those nets. Another issue that was an annoyance was that the connections were not alphabetized on the config page. They are on the menu where you choose the one you are connecting to, but on the config page, they stayed in the order they were entered. This becomes an issue when you have as many connections as I do. Frequently, when I entered a new connection, it would not show up on the list of available connections on the pull down menu. I would have to go and re-edit the connection and re-save it (sometimes multiple times) to get it to show up. I would like to add that it would be nice to get some more detail when a connection doesn't work. This isn't something .7 specific, because .6.x has the same issue. When a connection doesn't work, sometimes I have to revert to a Windows machine to see an error code so that I can troubleshoot the issue. Thanks. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
problem with pptp plugin
I do a lot of work with PPTP VPNs. I have over 100 on my workstation. I had upgraded to NM .7 for some of the features it had, but it had a lot of problems that were showstoppers for me. So, I reverted back to my older NM .6.6 and the network-manager-pptp .6.5_svnhead2574-0ubuntu1 that comes packaged with Hardy. Now, my existing VPN connections work fine, but I cannot create a new one. When I try to add one, I can choose the type of connection (step 1), but when I go to "step 2" where the settings are put in, the Forward button is grayed out. Since I can't go "forward", I can't save the new connection. Anyone know what I might be able to do to correct this? Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
static routes
The new network manager is improved over .6 in that it will keep my static routes after I connect/disconnect from a VPN. However, it still will not keep those routes after a reboot. Is there any way to make these routes persistent using NM? Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: upgrading from NM .6 to .7
On Mon, 2008-09-08 at 15:16 -0400, Dan Williams wrote: > On Mon, 2008-09-08 at 11:39 -0500, Trey Nolen wrote: > > I am running Ubuntu 8.04. I upgraded to Networkmanager .7 recently. I > > had about 125 or so PPTP VPN's setup, and when NM .7 installed, they > > were gone. The info is still under my .gconf folder (specifically, > > ~/.conf/system/networking/vpn_connections//%gconf.xml ) > > > > Is there any way to pull that in to the new NM? > > The applet doesn't make an effort to copy over old PPTP connections, but > that code could certainly be written just like it exists for OpenVPN and > vpnc so far. In the mean time, you could use XSLT or something to > transform the old format to the new format and reload into GConf, but > that doesn't sound like a whole lot of fun :) Thanks. I did find parts (if not all) of my old connections in ~/.gconf/system/networking/connections. I'm not sure if that's where they were before, or if something made an attempt to put them there. I have a subdirectory for each connection and new ones created in the new NM .7 are added sequentially to the existing ones. Can you elaborate or point me to documentation on the differences between the old and new formats? Should I make an effort to clean out the old connections if I am not going to convert them? If so, specifically what should I clean out? Thanks. Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
upgrading from NM .6 to .7
I am running Ubuntu 8.04. I upgraded to Networkmanager .7 recently. I had about 125 or so PPTP VPN's setup, and when NM .7 installed, they were gone. The info is still under my .gconf folder (specifically, ~/.conf/system/networking/vpn_connections//%gconf.xml ) Is there any way to pull that in to the new NM? Trey Nolen ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
