Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ssh sentinel to befsx41 vpn connect but no thru-put

Status
Not open for further replies.

vpncnfg

Technical User
Feb 11, 2003
6
CA
Hello All,

I can establish a VPN connection via SSH-Sentinel 1.3.2.2 under win98se (dialup) to a VPN endpoint on my Linksys BEFSX-41 (two win98se boxes behind the router).

Both ends confirm the connect -- however so far I have been unable to establish _any_ data throughput to or linkage to the LAN behind the router.

Now what? (I've RTfM .. twice :)

Thanks in advance...

vpncnfg PS. ,,
==
Here's some things I've tried so far:

router is broadcasting netbios; "\\IP\resource" variants fail; most recent interation of the Sentinel to BEFVP/SX connection guide from SSH (the 10 page PDF), new manual IP specs (the only change) - nada

 
It sounds like a routing issue. Do these PCs behind the Linksys know to go through the Linksys box to access your Virtual Lan. You should try a tracert command to see what IP routes are being used.
 
Thanks for the suggestion! (I got a one hop tracert from the lan behind the router to the remote node, and a lost in space choke sequence working from the remote node to the router end point).

Asking myself why / why / why re: the above it occured to me that the fast one hop from behind the lan reflects that there's no required traffic filters in the router, ergo a quick data trip, while ssh-sentinel has pre/post ip-sec rules required, and it seems that none of the default rules enable encryption and passage through the vpn.

Through a first session of experimentation I've yet to get an encrypted data packet to traverse the vpn (still 0 packets sent / 0 packets received) -- all very humbling.

I don't want or need an "easy way out", as I know that at the end of the day I'll have to grind out my own rules to get proper functionality. Having said that it would be really useful to see a/some sample ssh-sentinel rule sets used to secure vpn file/print shares; remote control (the timbuktu's of this world); etc.

I would greatly appreciate reference to sample rule sets for users of ssh-sentinel 1.3.2.2 to the BEFVP/SX router vpn endpoints.

(this may have been too verbose -- I'll work on it)

Thanks, vpncnfg :)


 
With vpn-sentinel connected to an end point on my BEFSX-41 I've tried to ping from the remote to a box behind the router (192.168.1.100) -- nada. Net View -- nada. \\192.168.1.100 -- nada.

18 hours per day for 10 days -- I'm stumped.

Now what :)
 
Can you ping the router LAN IP ( 192.168.1.1 ? )

If yes, the default gateway of the machines behind linky is not pointing to linky.

If no, forget about tweaking pre/post settings and stick to the original SSH manual.

No traces of 192.168.1.x network should be in your remote computer, NIC, WLAN, dial-up, GPRS, PPTP interfaces, pls check
 
Thanks for the replies.
Problem solved :)
Solution: Remove PCMCIA Ethernet card from laptop,
thereby removing IP resolution conflict.

vpncnfg
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top