- NETGEAR DG834 ADSL and CISCO VPN Client
- Posted by Alan Fay on November 27th, 2003
This is a very new NETGEAR ADSL router. It looks like a
really good router, it's got VPN pass thru, and everything.
I've just installed this ADSL router (connected with Demon)
and it works great for normal internet access.
However, when I try to do a CISCO Client VPN connect (which
works over a simple modem connection) I can connect and
negotiate, but then the internet connection dies (all
access).
The CISCO VPN client is v4.0. I tried this on windows
it didn't even negotiate. On Linux it did negotiate
and connect successfully. But then no internet access.
Cisco VPN client:-
-rw-r--r-- 1 root root 3696640 Nov 27 18:46 vpnclient-linux-4.0.Rel-k9.tar
Netgear allowed inbound ports:-
Any(ALL)(TCP/UDP:1,65535)
ALLOW always
Send to: 192.168.0.2 (Linux Server)
Yes everything. No other special rules, NO DMZ, etc.
I have to actually reboot my linux 2.4.21 v7.2 Redhat
machine to be able to connect back to the internet
(not very good, this is a windows type requirement).
Has anyone else had better luck with this ?
Please CC: me on any replies, I can receive them very
fast.
Alan
- Posted by Rik Bain on November 28th, 2003
On Thu, 27 Nov 2003 16:34:02 -0600, Alan Fay wrote:
Sounds as if the vpn policy does not have split tunneling enabled, in
which case, only the ipsec traffic will be allowed. This is configured
on the vpn termination device, not on the client.
Rik Bain
- Posted by Jimmy Dubke on December 1st, 2003
"Alan Fay" <alan@fay.demon.co.uk> wrote in message
news:bq5uam$ag0$1$8300dec7@news.demon.co.uk...
If you're using a firewall the router IP address needs to be added to the
firewall, as the modem will already be configured to get through the
firewall, but the router's IP will not - if in doubt turn the FW,
temporarily, off.
I just put a NETGEAR cable router on, and the Cisco client worked fine after
re-configuring the the FW, and configuring the router.
I did have one slight operator error. When done configuring my router I
just killed the browser that is used to configure the router instead of
using the logoff button on the router's configuration program. While that,
indeed, did kill the browser, it didn't terminate the router's configuration
program. The result was that then nothing worked. All I had to do was
cycle the router's power then everything was ok. As a precaution I went
back to the router and verified that everything was ok; after verifying
everything was ok, I then used the correct logoff button to place the router
into normal service, and everything worked.
JD