paolo.zarpellon at gmail
Nov 29, 2007, 6:05 AM
Post #4 of 6
(3318 views)
Permalink
|
On Nov 28, 2007 8:11 PM, Joerg Mayer <jmvpnc[at]loplof.de> wrote:
> On Tue, Nov 27, 2007 at 10:21:23PM +0100, Andreas Heider wrote:
> > I just got vpnc compiled fine under cygwin but only version 0.4.0 and
> > current svn. With both I am able to connect to the Cisco VPN Server of our
> > university (Uni Bayreuth), or at least it seems so. The client tells me
> > everything is ok, but I cannot access restricted areas of the uni net. I
> > think there went something wrong by changing the route tables. Please read
> > the following output of vpnc and route print, hopefully you can tell me
> > what's wrong.
>
> Unfortunately, I can't. Instead I'm quite confused:
>
>
> > VPN Gateway: 132.180.252.49
> > Internal Address: 132.180.224.224
> ...
> > Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl
> > 0.0.0.0 0.0.0.0 132.180.252.49 132.180.224.224 1
> > 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.38 1
> > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> > 131.188.0.0 255.255.0.0 132.180.224.224 132.180.224.224 1
> > 132.180.0.0 255.255.0.0 132.180.224.224 132.180.224.224 1
> > 132.180.224.0 255.255.255.0 132.180.224.224 132.180.224.224 1
> > 132.180.224.224 255.255.255.255 127.0.0.1 127.0.0.1 1
> > 132.180.255.255 255.255.255.255 132.180.224.224 132.180.224.224 1
> > 192.109.202.0 255.255.255.192 132.180.224.224 132.180.224.224 1
> > 192.168.1.0 255.255.255.0 192.168.1.38 192.168.1.38 1
> > 192.168.1.38 255.255.255.255 127.0.0.1 127.0.0.1 1
> > 192.168.1.255 255.255.255.255 192.168.1.38 192.168.1.38 1
> > 224.0.0.0 224.0.0.0 132.180.224.224 132.180.224.224 1
> > 224.0.0.0 224.0.0.0 192.168.1.38 192.168.1.38 1
> > 255.255.255.255 255.255.255.255 132.180.224.224 132.180.224.224 1
> > Standardgateway: 192.168.1.1
>
> If I read the code in vpnc-script-win.js correctly, there should have
> been a line like "132.180.252.49 255.255.255.255 192.168.1.1
> 192.168.1.38 1".
there was a fix which went in the trunk not long ago to fix a couple
of issue with vpnc-script-win.js, one of those was an issue with the
VPN gateway route.
> Also, why are there two default routes? Maybe the old
> default route should be deleted?
> Btw, when INTERNAL_IP4_NETMASK is not set, the linux script uses
> 255.255.255.255 as netmask. Is there a specific reason why this isn't
> done on windows? (ok, linux will currently ignore the value of
> INTERNAL_IP4_NETMASK and always use 255.255.255.255 but that's already
> fixed in my sources).
windows (xp, at least) does not let you use 255.255.255.255 as netmask:
$ netsh interface ip set address TAP2 static 10.0.0.1 255.255.255.255
255.255.255.255 is not an acceptable value for mask.
In vpnc-script-win.js, the netmask is currently hardcoded to
255.255.255.0. There was a patch to set it to either
INTERNAL_IP4_NETMASK or some other default value if
INTERNAL_IP4_NETMASK was not set but it never got applied.
Regards,
Paolo
> Ciao
> Joerg
>
> PS: Can you please tell me a sample address that should be reachable but
> isn't?
> --
> Joerg Mayer <jmayer[at]loplof.de>
> We are stuck with technology when what we really want is just stuff that
> works. Some say that should read Microsoft instead of technology.
> _______________________________________________
> vpnc-devel mailing list
> vpnc-devel[at]unix-ag.uni-kl.de
> https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
> http://www.unix-ag.uni-kl.de/~massar/vpnc/
>
_______________________________________________
vpnc-devel mailing list
vpnc-devel[at]unix-ag.uni-kl.de
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/
|
