My syslog for failed vpn connection
Nov 20 08:42:26 Tor NetworkManager: info Starting VPN service 'org.freedesktop.NetworkManager.pptp'... Nov 20 08:42:26 Tor NetworkManager: info VPN service 'org.freedesktop.NetworkManager.pptp' started (org.freedesktop.NetworkManager.pptp), PID 21849 Nov 20 08:42:26 Tor NetworkManager: info VPN service 'org.freedesktop.NetworkManager.pptp' just appeared, activating connections Nov 20 08:42:26 Tor NetworkManager: info VPN plugin state changed: 3 Nov 20 08:42:26 Tor NetworkManager: info VPN connection 'AMEIL' (Connect) reply received. Nov 20 08:42:26 Tor pppd[21850]: Plugin /usr/lib/pppd/2.4.4/nm-pptp-pppd-plugin.so loaded. Nov 20 08:42:26 Tor pppd[21850]: pppd 2.4.4 started by root, uid 0 Nov 20 08:42:26 Tor pppd[21850]: Using interface ppp0 Nov 20 08:42:26 Tor pppd[21850]: Connect: ppp0 -- /dev/pts/1 Nov 20 08:42:26 Tor pptp[21852]: nm-pptp-service-21849 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Nov 20 08:42:26 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Nov 20 08:42:26 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Nov 20 08:42:26 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 31498). Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:950]: PPTP_SET_LINK_INFO received from peer_callid 61400 Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:953]: send_accm is , recv_accm is Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 warn[ctrlp_disp:pptp_ctrl.c:956]: Non-zero Async Control Character Maps are not supported! Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:950]: PPTP_SET_LINK_INFO received from peer_callid 61400 Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:953]: send_accm is , recv_accm is Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 warn[ctrlp_disp:pptp_ctrl.c:956]: Non-zero Async Control Character Maps are not supported! Nov 20 08:42:27 Tor pppd[21850]: LCP terminated by peer (rM-?]^^@[EMAIL PROTECTED]@^BM-3) Nov 20 08:42:27 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_disp:pptp_ctrl.c:912]: Received Call Clear Request. Nov 20 08:42:30 Tor NetworkManager: info VPN plugin failed: 1 Nov 20 08:42:30 Tor pppd[21850]: Connection terminated. Nov 20 08:42:30 Tor pptp[21852]: nm-pptp-service-21849 warn[decaps_hdlc:pptp_gre.c:204]: short read (-1): Input/output error Nov 20 08:42:30 Tor pptp[21852]: nm-pptp-service-21849 warn[decaps_hdlc:pptp_gre.c:216]: pppd may have shutdown, see pppd log Nov 20 08:42:30 Tor pptp[21859]: nm-pptp-service-21849 log[callmgr_main:pptp_callmgr.c:234]: Closing connection (unhandled) Nov 20 08:42:30 Tor pptp[21859]: nm-pptp-service-21849 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request' Nov 20 08:42:30 Tor pptp[21859]: nm-pptp-service-21849 log[call_callback:pptp_callmgr.c:79]: Closing connection (call state) Nov 20 08:42:30 Tor NetworkManager: info VPN plugin failed: 1 Nov 20 08:42:30 Tor pppd[21850]: Modem hangup Nov 20 08:42:30 Tor pppd[21850]: Exit. Nov 20 08:42:30 Tor NetworkManager: info VPN plugin failed: 1 Nov 20 08:42:30 Tor NetworkManager: info VPN plugin state changed: 6 Nov 20 08:42:30 Tor NetworkManager: info VPN plugin state change reason: 0 Nov 20 08:42:30 Tor NetworkManager: WARN connection_state_changed(): Could not process the request because no VPN connection was active. Nov 20 08:42:30 Tor NetworkManager: info Policy set 'Auto ameilmodem' (ath0) as default for routing and DNS. As per Olaf's suggestion to use syslog readouts, here it is. Can anyone tell why it doesn't make the connection from this readout? Please advise, vpn user getting desperate! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Review of syslog results
The only atypical entry seems to be where the connection is made and the send_accm is and recv_accm is . The next line gives a Non-Zero ACCM are not supported. So is it the that it doesn't like? Or is it the - which appears to all zeros to me. This is followed by both send and recv accm values being which is followed again by the Non-Zero error. The next line says LCP terminated by peer (ie. the windows server cuts the connection (?) and then the nm vpn reacts to the closed connection by shutting down and delivering the failed error message. Baffling for us GUI-habituated, ex-Gatesians. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Review of syslog results
On Thu, Nov 20, 2008 at 2:56 PM, Tor Fosnaes [EMAIL PROTECTED] wrote: The only atypical entry seems to be where the connection is made and the send_accm is and recv_accm is . The next line gives a Non-Zero ACCM are not supported. So is it the that it doesn't like? Or is it the - which appears to all zeros to me. This is followed by both send and recv accm values being which is followed again by the Non-Zero error. The next line says LCP terminated by peer (ie. the windows server cuts the connection (?) and then the nm vpn reacts to the closed connection by shutting down and delivering the failed error message. Would be nice if you didn't start a new thread with each response. -- Patryk Zawadzki ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Networkmanager inserting 'stray' DNS server in /etc/resolv.conf
Hi... My environment: Kernel: 2.6.24-21-386 on Ubuntu 8.04 (Hardy) HW: Compaq nc6220 NM: 0.6.6-0ubuntu5 At home, I have wireless configured to get DNS from opendns.org (207.67.222.222). I never use wired connections at home. When I vpn into work, the vpn software I use alters /etc/resolv.conf to put the work dns servers in front of the home dns servers. At the office, I exclusively used wired connections and despite that I find that nm will insert a DNS reference to the 'home' DNS server first. Since I am behind a firewall, this ensures that every DNS request I make first fails, and has to drop back to the internal DNS servers. I can't figure out where NM is getting this value. I routinely hack it out, but a restart of NM puts is back. Is there a way to correct this or is this an artifact of this version of NM? Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Hostname set to localhost.localdomain at reboot
Hello there! I hear this is a common problem and I hear that you think it's been fixed. However, it most certainly has not. My computer is a Dell Vostro 1500 running Ubuntu Intrepid with the latest updates as of today (11/20). My networkmanager package version is 0.7~~svn20081018t105859-0ubuntu1, as reported by aptitude. So I start my computer up normally. The /etc/init.d/hostname script runs and sets my hostname to northbound, like it should be. Then, NetworkManager runs and changes it to localhost.localdomain. Boo. Here's an example session that I set up to show you just what I mean: [EMAIL PROTECTED]:~$ hostname northbound [EMAIL PROTECTED]:~$ sudo /etc/init.d/NetworkManager restart * Stopping NetworkManager... [ OK ] * Starting NetworkManager... [ OK ] [EMAIL PROTECTED]:~$ hostname northbound # About 5-10 seconds later: [EMAIL PROTECTED]:~$ hostname localhost.localdomain # About 15 minutes later in a separate shell when NM's connected to my network: [EMAIL PROTECTED]:~$ hostname northbound.uccs.edu [EMAIL PROTECTED]:~$ aptitude show network-manager | grep -i version Version: 0.7~~svn20081018t105859-0ubuntu1 Does anyone know how to help? I'd be happy to provide more details if you'd like. Thank you for your time. Michael ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Networkmanager inserting 'stray' DNS server in /etc/resolv.conf
On Thu, 2008-11-20 at 10:50 -0500, Rick Beldin wrote: Hi... My environment: Kernel: 2.6.24-21-386 on Ubuntu 8.04 (Hardy) HW: Compaq nc6220 NM: 0.6.6-0ubuntu5 At home, I have wireless configured to get DNS from opendns.org (207.67.222.222). I never use wired connections at home. When I vpn into work, the vpn software I use alters /etc/resolv.conf to put the work dns servers in front of the home dns servers. At the office, I exclusively used wired connections and despite that I find that nm will insert a DNS reference to the 'home' DNS server first. Since I am behind a firewall, this ensures that every DNS request I make first fails, and has to drop back to the internal DNS servers. I can't figure out where NM is getting this value. I routinely hack it out, but a restart of NM puts is back. Do you have any DNS servers configured in /etc/network/interfaces? dan Is there a way to correct this or is this an artifact of this version of NM? Rick ___ 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: Hostname set to localhost.localdomain at reboot
On Thu, 2008-11-20 at 11:05 -0700, Michael W wrote: Hello there! I hear this is a common problem and I hear that you think it's been fixed. However, it most certainly has not. My computer is a Dell Vostro 1500 running Ubuntu Intrepid with the latest updates as of today (11/20). My networkmanager package version is 0.7~~svn20081018t105859-0ubuntu1, as reported by aptitude. So I start my computer up normally. The /etc/init.d/hostname script runs and sets my hostname to northbound, like it should be. Then, NetworkManager runs and changes it to localhost.localdomain. Boo. Here's an example session that I set up to show you just what I mean: NetworkManager will only change it to localhost.localdomain if it cannot get the persistent hostname that you've specified in /etc/hostname. When nm-system-settings starts up, it should be loading the ifupdown plugin, which will read /etc/hostname and provide that hostname to NetworkManager. NetworkManager will then use that hostname _exclusively_. So the fact that it's getting set to localhost.localdomain means one of a few things: 1) nm-system-settings + ifupdown isn't able to read the persistent hostname from /etc/hostname 2) NM isn't able to get the persistent hostname from nm-system-settings (which is done using dbus) and can be verified with the following command: dbus-send --print-reply --system --dest=org.freedesktop.NetworkManagerSystemSettings /org/freedesktop/NetworkManagerSettings org.freedesktop.DBus.Properties.GetAll string:org.freedesktop.NetworkManagerSettings.System 3) NM isn't able to set the hostname for some reason 4) NM isn't able to update /etc/hosts with your new hostname Are there any errors printed out in /var/log/daemon.log after NM sets the IP address? They would reference 'hostname' if there are any. Dan [EMAIL PROTECTED]:~$ hostname northbound [EMAIL PROTECTED]:~$ sudo /etc/init.d/NetworkManager restart * Stopping NetworkManager... [ OK ] * Starting NetworkManager... [ OK ] [EMAIL PROTECTED]:~$ hostname northbound # About 5-10 seconds later: [EMAIL PROTECTED]:~$ hostname localhost.localdomain # About 15 minutes later in a separate shell when NM's connected to my network: [EMAIL PROTECTED]:~$ hostname northbound.uccs.edu [EMAIL PROTECTED]:~$ aptitude show network-manager | grep -i version Version: 0.7~~svn20081018t105859-0ubuntu1 Does anyone know how to help? I'd be happy to provide more details if you'd like. Thank you for your time. Michael ___ 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: IEEE802.1x + STATIC WEP
nop, no idea about that :(
On Thu, 2008-11-20 at 13:20 -0500, Dan Williams wrote:
On Wed, 2008-11-19 at 14:41 -0600, Mario Medina wrote:
Hi! I have in my office a uncommon configuration of the network, weuse
IEEE802.1x keymanagement with TLS and static WEP keys, is N-M capable
of configuring this type of network?
Not at this time; this is the first instance I've heard of this, and
kinda pointless actually as the WEP key doesn't rotate...
Any idea what AP hardware and RADIUS server is backing your network
setup?
Dan
At this time I do the connection manually with this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=admin
update_config=1
network={
ssid=wnetwork
key_mgmt=IEEE8021X
auth_alg=OPEN
eap=TLS
identity=myusername
password=mypassword
ca_cert=/etc/network/cacert.pem
client_cert=/etc/network/cert.pem
private_key=/etc/network/key.pem
private_key_passwd=thekeypassword
wep_key0=hex static wep key
disabled=0
}
and it connects. sometimes i need to issue a manual iwconfig to set
the key, but at this time i can't find the way to do this with N-M.
Thanks
Cristo te Ama. Por que de tal manera te amó Dios, que dio a su único
Hijo, para que vivas con Dios eternamente, si es que crees en su Hijo.
www.iglesiacristianaebenezer.com
Salud Integral: www.drmedina.com.mx
Todo de Linux: www.viviendolinux.com
___
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: Networkmanager inserting 'stray' DNS server in /etc/resolv.conf
On Thu, 2008-11-20 at 18:23 +, Dan Williams wrote: Do you have any DNS servers configured in /etc/network/interfaces? No, no DNS servers there... And to... On Thu, 2008-11-20 at 18:12 +, Mathieu Trudel-Lapierre wrote: I'd personally check if resolvconf is installed on your system, then if it is, whether the opendns.org server is listed in one of the files under /etc/resolvconf/resolv.conf.d. Resolvconf does have some special behavior that isn't always what you'd want or expect, I found; especially when using network-manager-vpnc on Ubuntu 8.04. No, I don't have resolvconf installed: dpkg -l resolvconf Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- un resolvconf none (no description available) The only thing that occurs to me is that the 'pattern' of my work is to start my day at home, shutdown, startup again in the office. The opendns.org nameserver always comes first. Dimly grasping at straws, I deleted all the 'manual configuration' entries in nm and will monitor to see if any these are influencing what is going on here. Rick ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
how to configure tap0/br0 correctly
Hi there, I am on Ubuntu 8.10, upgraded from previous release mainly to get the shiny new Network Manager 0.7 that was supposed to honor the /etc/network/interfaces settings. I need to get tap0 bridged with eth0 so I have the following entries in the 'interfaces' file: == auto eth0 iface eth0 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down auto tap0 iface tap0 inet manual up ifconfig $IFACE 0.0.0.0 up down ifconfig $IFACE down tunctl_user username auto br0 iface br0 inet dhcp bridge_ports eth0 tap0 == The goal is obviously to let the br0 replace the eth0 for all my outgoing networking, including VPN connections etc. Now I'd swear it worked perfectly for a couple of days but it stopped working suddenly today and I am unable to get it working again. The nm-applet does not appear until I restart the NM daemon and then the nm-applet indicates that I have everything managed by the /etc/network/interfaces so it will not allow me to launch VPN connection on it. I have read so many open bug reports in Ubuntu about their NM that I decided I need to ask here for the right solution: how to set the br0 so that NM will accept it and the nm-applet will allow me running VPN over it... When I tried removing the eth0 from /etc/network/interfaces to let NM manage it the routing got messed up because both eth0 and br0 got their address from DHCP. Right now I have the default Ubuntu setting in nm-system-settings.conf, that is [ifupdown] managed=false. I have tried enabling it but things didn't look better so I restored the original setting. Thanks for any advice. I am sure all Debian/Ubuntu/similar users of VirtualBox and other emulators that use the tap interfaces would be more than happy to know the right setting compatible with NM. Petr ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
v6 only networks broken?
hi, I am not sure if someelse else at IETF already raised this, but NM does not work on IPv6 only networks. After association on the wifi, it disassociates with could not obtain an address. We suspect because it did not get an ipv4 ip address via dhcp, though we did get an ipv6 address. Paul ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
