I have a couple VPNs I use for work, and after installing F14 x86_64 it is failing:
Code:
Nov 5 12:40:57 raykj NetworkManager[4106]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 4203
Nov 5 12:40:57 raykj NetworkManager[4106]: <info> VPN service 'vpnc' appeared; activating connections
[Code]....
I am trouble trying to get vpnc to work on my laptop.
Using the same computer via Ubuntu, it works fine.
I used to use an older kernel with the cisco vpn client, but had to go through the motions of turning off cpus in order for it to work. I gave that trick a try and it does not work.
I pretty much followed the instructions from: Gentoo Linux Documentation -- Gentoo vpnc HOWTO
The machine completely locks up right after I enter my password...
I don't see anything relevant in the /var/log/messages file.
Is there another log file to look into specific to the vpnc?
In fc10 & fc11 everything worked well with vpnc.
With fc12 vpnc starts allows me to connect to my work site then everything works fine til I try and start a remote desktop connections to a windows client use tsclient. All I get is a blackscreen and my laptop is hung.
At work without the vpnc it works fine if I start the vpnc from nm it performs the exact same way and I get the blackscreen.
I have disable selinux.I also disabled the firewall
there was another gentlemen on here with the same issue.
The only way out is a hard reboot and there are no messages in the logs that say there were any problems.
I've been trying to connect to my office Cisco VPN several time using the network-manager-vpnc GUI in Ubuntu Karmic with no success. I read a couple of articles and i tried using the direct command line way:
Code:
sudo vpnc office
with the following /etc/vpnc/office.conf file:This is fictional data
Code:
IPSec gateway vpn.office.com
IPSec ID office
IPSec secret 0ff1c3
which worked perfecly.
So i went back to the Network Manager GUI way and i used the same credentials. Same fictional data I got a libnotify message telling me it couldn't connect.Anyone know how i could troubleshoot this issue? Would be great to have it integrated in gnome instead of running a background command which is not tracked by nwm.
When I run the YAST Online Update OR Software Management OR Zypper, the Updates (or install of new software) fails when the download of the Delta RPM reaches 98%. I have added ALL of the community repositories and have Imported the appropriate certificates. When watching the DeltaRPM or normal RPM download, it starts the download at approx. 4Mbs/sec until it reaches 98% of file downloaded. Then, the speed drops to 0 B/sec and the file download fails. This then prompts a Retry which again fails when it reaches approx 98% download. It does not matter if I am doing an Online Update, Doing a Software Management (to install new software) or using Zypper in a Terminal session, the result is the same.
I have even gone so far as to connect the machine DIRECTLY to the internet, bypassing all firewalls so as to ensure it is not a firewall
[Code]...
Since I installed FC11 vpnc stop working. I get "vpnc: no response from target." I tried running it with "strace" and the reason is a timeout: poll([{fd=3, events=POLLIN}], 1, 4000) = 0 (Timeout)
I tried google and adding "NAT Traversal Mode cisco-udp" to the config file works for some people but not for me Does anyone had experience with vpnc 0.5.3 in FC11?
I have been trying to connect to my University's VPN Server and for some reason vpnc fails. I have configured the vpn settings the same way I did for the past two years. They worked properly on Fedora 12 and 13, but for some reason fails on Fedora 14.
Code:
Jan 6 16:45:20 exodusprime NetworkManager[1269]: <info> Starting VPN service 'vpnc'...
Jan 6 16:45:20 exodusprime NetworkManager[1269]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 11731
Jan 6 16:45:20 exodusprime NetworkManager[1269]: <info> VPN service 'vpnc' appeared; activating connections
Jan 6 16:45:21 exodusprime NetworkManager[1269]: <info> VPN plugin state changed: 3
Jan 6 16:45:21 exodusprime NetworkManager[1269]: <info> VPN connection 'Swinburne University VPN' (Connect) reply received.
code....
Problem with fedora 13, I am no longer able set up a virtual private network using vpn. The following error message appers:
"/usr/sbin/vpnc: no response from target"
No problem when connecting with ubuntu or windows.
how nobody else could have run into this in the meantime. [URL] Two friends of mine are having the same issue on Ubuntu-11.4-machines. In short: Connecting to the Cisco-VPN via shell-command "vpnc" works flawlessly, whereas NetworkManager just doesn't connect at all. We had this working in older versions of Fedora/Ubuntu about some months ago...
View 9 Replies View RelatedI am having problems accessing my work desktop through my home computer running Fedora 13. I am able to remote into work through MAC and Windows XP. I loaded vpnc and was able to connect to the concentrator. I also able to ping it too. I cannot connect to my desktop using rdesktop. I get error message �Unable to connect, socket is unavailable. I cannot ping to the desktop.
View 2 Replies View RelatedI realize that Canonical is not responsible for the Catalyst driver, but I can't seem to operate outside of the Ubuntu Classic (no effects) mode for 64 bit Natty, and I was curius if anyone else had encountered or resolved this.
When I upgraded from 10.10 (I was using the fglrx package), xorg would immediately crash. I was able to reach the gdm screen only using recovery mode. I uninstalled the fglrx package, and now I can boot into Ubuntu Classic (no effects) mode only (no other desktop will work) using the open-source driver at no greater than 1280x1024.
When I try to re-install the catalyst driver using aptitude or Administration->Additional Drivers, the installation fails:
(jockey.log: WARNING: modinfo for module fglrx failed: ERROR: modinfo: could not find module fglrx)
Similarly, package generation from the AMD page fails:
Installation complete.
*** glibc detected *** ./setup.data/bin/x86_64/setup: double free or corruption (fasttop): 0x000000000259f630 ***
======= Backtrace: =========
[Code].....
I am having difficulties in establishing a vpn connection using vpnc (or NetworkManaager-vpnc).
As long as the openswan IPsec daemon is running, vpnc-helper quits with the error message
Quote:
Failed to bind to 0.0.0.0:500: Address already in use
[user@computer ...]# vpnc-helper --local--port 0
If I use NetworkManager-vpnc, then establishing the connection simply fails.
Using the --local-port 0 option does not change anything.
If I stop the ipsec service (service ipsec stop) then establishing the connectiong works, both with NetworkManager-vpnc and the console tool, but apparently the network traffic is not routed via the VPN - in my case this means that I cannot access hosts within the vpn and stuff.
Funny thing is - on my notebook from where I connect via WLAN, everything works fine. With Fedora 13 everything works fine, too.
Does anybody have an idea how to enforce that the vpn connection is actually used?
I am using KNetworkmanager-vpnc to VPN back to the office from home, the vpn connection works fine - for 15 minutes then I am disconnected. I am fairly certain that this is related to the Phase 1 key lifetime limit. The Knetworkmanager-vpnc GUI does not provide a location to enter this information. I think I found the config file that holds the connection information at /home/<user>/.kde/share/apps/networkmanagement/connections/ I just don't know the proper syntax to put in the file to specify a key life limit. Anyone out there know how to do this? I am using Fedora 14 x64 with knetworkmanager-vpnc 1.0.9-0.28.
View 1 Replies View RelatedI'm having problems with vpnc on F12 that work fine on F10 and F11. On F12, I can connect and can do some activities, but so far I noticed the following (show-stopping) issues:Attempting to connect to an Oracle database using either sqlplus or TORa hangs and eventually times out. I tried both the 11G and 10G instant clients.Copying a file to the host via a smb:// mount in nautilus freezes. An empty file is created though.
A rdesktop client opens a "black" window and goes no further. I attempted to downgrade vpnc on my F12 workstation from vpnc-0.5.3-4.fc12.x86_64 to vpnc-0.5.3-3.fc11.x86_64 to no avail. I also downgraded libgcrypt too and this didn't help either. Moreover, I upgraded these to the F13 rawhide version - still no luck.
I also confirmed on a F11 virtual machine that these work and that it doesn't work on 2 x64 and 1 x386 F12 machines. (The configuration and the host are the same in all cases.)
I have configured a Fedora 10 server on a mixed Win / ix network but am unable to get DNS to resolve on my Fedora boxes.My DHCP is provided from a D-Link 108G Router - but this will not provide DNS.Therefore I have tried to configure dnsmask to provide just DNS and not DHCP. I can ping around my 192.168.1.x network by IP but not name
View 4 Replies View RelatedI just upgraded Ubuntu 10.04 LTS. Now when I use vpnc to connect from the command line using vpnc-connect, I'm not only prompted for my password as usual, but now also being prompted for a "Passcode". Here's what the login attempt looks like:
Enter password for jegan@some.vpnhost.net:
Passcode for VPN jegan@216.23.18.33:
I've been using the same /etc/vpnc/default.conf file for years.Note that I do not have an /etc/vpnc.conf, or any of the other configuration files that vpnc checks for.Here's a modified copy of my /etc/vpnc/default.conf file:
## generated by pcf2vpnc
IPSec ID CRL-Qfe
IPSec secret XM-j-245Rv[code].............
I use VPNC to connect to a Cisco VPN. I am able to connect, but some issues exist when I use SSH. For example, I login through SSH to a computer in the VPN and I execute ls => it works. If I execute ls -la => connection stalls. I think it stalls every time it is supposed to return more content (top, ls /etc).
If I do scp from my end to server => works. If I do scp from server to my end => connection stalls.
I'm trying to setup a VPN using VPNC. All is well and I can create the VPN.
The problem is that CNTLM does not want to connect in the VPN Further more I am not sure what to look for? The logs are empty and CNTLM only reports 502 Parent proxy unreacheable.
How can I trace what the problem is?
My setup:
Ubuntu 10.10 64
CNTLM 0.91~rc6-0ubuntu1.1
VPNC 0.5.3r449-2
I tried fix I pointed here http://fedoramobile.org/Members/MrHappy/troubleshootingNetworkManager fails to see wireless networks with Intel 3945 chipsets(solution deals with the kernel module not with NetworkManager)but nothing to do. My actual problem is I can't see my wireless network but I see just those of my neighbours.I know mine is working because I can connect to using a Mac and windows.
View 5 Replies View RelatedI installed network-manager-vpnc, configured cisco vpn through NetworkManager. It works slow, but the bigger problem is that after minute or so the connection just freezes.Then I tried kvpnc. It works like it should from speed point of view. But it also hangs up after minute or two.Tried to change MTU of my wired connection to 1500 - no good.Tried to uncomment line in /etc/ppp/options "mru 542" - no good.
Created /var/run/vpnc because it was giving some error "can't open pidfile /var/run/vpnc/pid for writing".From logs everything seems fine except for "nm-dispatcher.action:Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1." in last line. If I use kvpnc it gives no errors.SO, how do I debug this thing or does anyone knows something I don't in this case?
When I connect to my company's VPN (it's a Cisco), it connects just fine and displays the broadcast message, but once connected I can't ping anything or ssh anywhere. Not on the private network, not on the Internet [URL], nothing. I can still browse the web without difficulties when connected to the VPN, but no ssh or ping. With ping, it properly resolves the host name, but I get 100% packet loss.
Once I disconnect from the VPN, a ping of [URL] works exactly as expected.
I don't have any firewalls set up on this host that I'm aware of (unless something is installed and configured by default).
I'm using Ubuntu 10.10, amd64 build.
Our company uses a customized vpnc (based on and almost the same as vpnc 0.5.3). I first tested it on a Windows host under Virtualbox everything works straight away. But when I want to use it on a Linux host directly it always ends in "No response from target". I have tested this on Fedora 12 and the latest Ubuntu.
I thought of firewall settings but iptables -L on Ubuntu returns an empty list even.
I'm trying to connect to a Cisco VPN at work from Ubuntu 10.10. On earlier versions, I was able to import the config and get it working. In 10.10, though, the best I've gotten is being able to connect to the VPN, see the welcome message, and have packets sent over the tunnel. I don't receive any packets, though.
The command-line vpnc client connects just fine. I found this bug report: [URL]
The symptoms it describes are exactly what I'm seeing. The apparent solution is to "make sure in your config that LZO Compression is enabled (checked) under Advanced"; however I see neither an option for compression nor an "Advanced" tab, button, or anything on my VPN config in Network Manager.
I installed vpnc package under RHEL 5.1 64 bit and its working fine. but it is showing frequent disconnectivity issue. I did added the script for respawning:
Code:
I have just added but no idea if it will work or not.Downloaded from external source.
1. How to check vpnc logs upon disconnectivity?
2. How to make the connectivity stable?
Since 2.6.27.19-170.2.35.fc10.x86_64, dhclient wlan0 doesn't seem to work any more.
However, bizarrely, dhclient eth0 does (to the same D-link wireless router).
The AP shows connected - tail /var/log/messages
No working leases in persistent database - sleeping.
WINXP connects just fine. This (B43) has worked nicely ever since FC10 came out, and I was able to use the WiFi at all kinds of places on a recent trip. Other than a couple of yum updates, I don't think anything else has changed since. Other devices on the wlan are getting their DHCP requests satisfied correctly.
Is anyone else having this problem since about a week ago? Perhaps there's something really obvious I'm missing. I can manually assign an IP address to wlan0, manually edit the routing tables and edit /etc/resolv.conf, and then Wifi seems to work OK, so it doesn't seem to be b43 itself unless it is dropping DHCPOFFERS. If this isn't a regression, does anyone have any tips about how to debug this?
I created a F14 x86_64 guest OS in VirtualBox4 (hosted by F14 x86_64) and configured it to get its IP from my router but it won't do so on boot. The other guest OS's (Fedora 14 i386, 2x Oracle EL5) are able to get their IPs on boot.
I checked the setting in the network manager and they show that the interface is to be activated on boot but it doesn't. When I log in and run ifup eth0 as root it works.
I just got vpnc setup to work with my VPN at work and now I am trying to figure out how to limit the traffic that is routed through the VPN while I'm connected to it. I only want traffic going to the local domain to be routed through the VPN.This is what my vpnc config file looks like:
Code:
IPSec gateway publicdomain.example.com
IPSec ID XXXX
[code]....
I have a Broadcom Corporation BCM4312 802.11b/g (rev 01) wireless card. I installed these packages:
broadcom-wl-5.10.91.9.3-1.fc12.noarch
akmod-wl-5.10.91.9.3-3.fc12.6.x86_64
kmod-wl-2.6.31.6-145.fc12.x86_64-5.10.91.9.3-3.fc12.8.x86_64
[code]....
uname -a says:
Linux boz.alafkhar 2.6.31.6-145.fc12.x86_64 #1 SMP Sat Nov 21 15:57:45 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
and:
# lsmod | grep wl
wl 1278432 0
lib80211 6436 2 lib80211_crypt_tkip,wl
[code]....
My networkmanager understands that the card is installed. But it can not find any network. Also iwlist scan gives me no result. I did not have this problem on earlier fedora releases. Recently I upgraded to F12 from F11. I should mention that I have another USB DLink wireless card and when I plug it, everything works fine with that card. I also tested wl_apsta driver using fw-cutter. I did not work neither.
I just built some machines with the Intel 82574L gigabit ethernet chip, loaded Fedora 14, and discovered a problem with the e1000e driver dying after a few minutes. A little time spent perusing the web told me that the same driver had problems in Fedora 12 and Fedora 13 as well. Congrats to Fedora for the hat trick.As of kernel 2.6.35.10-74.fc14.x86_64, e1000e driver 1.0.2-k4 still had bugs.[URL]
View 6 Replies View RelatedI'm running an up-to-date Fedora 12 machine with the Gnome desktop (meaning with Network Manager). My network connection is a wired ethernet to a switch which then connects to a Netgear router. For some reason, this machine can't renew its leases with DHCP, so NetworkManager deactivates eth0, taking my machine off the network. I have to click Network Manager and enable eth0, which seems to work every time.
How can I fix it? Here are the relevant bits from /var/log/messages showing a failed DHCP request and then the successful renewal.
Code:
Aug 1 04:00:08 ironton dhclient[12452]: DHCPREQUEST on eth0 to 192.168.1.1 port 67
Aug 1 04:00:08 ironton dhclient[12452]: DHCPNAK from 192.168.1.1
Aug 1 04:00:08 ironton NetworkManager[1261]: <info> (eth0): DHCPv4 state changed reboot -> expire
Aug 1 04:00:08 ironton NetworkManager[1261]: <info> (eth0): device state change: 8 -> 9 (reason 6)
Aug 1 04:00:08 ironton NetworkManager[1261]: <info> Marking connection 'System eth0' invalid because IP configuration expired.
[Code]...