<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: ALMOST: Cipe on Windows 2000 w/BSOD
From: "Jacob Joseph" <jmjoseph,AT,andrew,DOT,cmu,DOT,edu>
Date: Fri, 24 Aug 2001 17:36:18 +0200
In-reply-to: <200108232323.f7NNN5Z25811@otter.mbay.net>

Here's another follow-up.  I have encountered a few more problems.

I'm still having difficulties with routing.  I have set the local PTP IP to
10.0.0.20.  The remote network is 10.0.0.0 with a 10.0.0.254 gw.  I am able
to ping both directions ONLY between these machines.  If I either ping from
or to an internal machine on the remote network, I don't get anywhere.  This
kind of makes sense though--packets on the same network would not go to the
cipe gateway machine...  Is bridging possible on kernel 2.2(RH6.2)?  I don't
want to upgrade the kernel from 3000 miles away...

Or, rather than bothering with having my win2k machine as 10.0.0.20, I tried
192.168.1.1 in hopes that the routing would be easier to figure out...  Here
are the routing tables.  I just deleted the lines not pertinent to cipe(the
Internet IPs):

C:\>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 a0 cc 59 20 78 ...... NETGEAR FA310TX Fast Ethernet PCI
Adapter
0x1000004 ...08 00 58 00 00 01 ...... DKW Heavy Industries VPN Adapter.
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
       10.0.0.254  255.255.255.255      192.168.1.1     192.168.1.1       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.1.0    255.255.255.0      192.168.1.1     192.168.1.1       1
      192.168.1.1  255.255.255.255        127.0.0.1       127.0.0.1       1
    192.168.1.255  255.255.255.255      192.168.1.1     192.168.1.1       1

Default Gateway:       x.x.x.x
===========================================================================
Persistent Routes:
  None

------------------------and-------------------------------
[root@mail /root]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.1     0.0.0.0         255.255.255.255 UH    0      0        0
cipcb0
x.x.x.x     0.0.0.0         255.255.255.255 UH    0      0        0 eth1
10.0.0.254      0.0.0.0         255.255.255.255 UH    0      0        0 eth0
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
x.x.x.x      0.0.0.0         255.255.255.0   U     0      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         x.x.x.x      0.0.0.0         UG    0      0        0 eth1

My IPchains rules allow all traffic over the cipe link.  Obviously, I don't
have a route on the windows machine to the 10.0.0.0 network.  However, I get
an error when I attempt to do this:

C:\>route add 10.0.0.0 mask 255.255.255.0 10.0.0.254
The route addition failed: Either the interface index is wrong or the
gateway do
es not lie on the same network as the interface. Check the IP Address Table
for
the machine.

How can I work around this error?  Using the above command with a gateway of
192.168.1.1 does not seem to work.

Sorry for the long message; and thanks,
Jacob Joseph

----- Original Message -----
From: "Jacob Joseph" <jmjoseph,AT,andrew,DOT,cmu,DOT,edu>
To: <cipe-l,AT,inka,DOT,de>
Sent: Thursday, August 23, 2001 7:49 PM
Subject: ALMOST: Cipe on Windows 2000 w/BSOD

> OK.  I am now able to ping both directions, but not to the network behind
> the remote gateway(yet).  I am still in the market for a BSOD fix, but I
> think the gateway just needs the IPchains rules to allow me to get past
> it...
>
> I just don't want to wrack anyone's brain unnecessarily, so I thought it
> prudent to post a follow-up.
>
>
> Jacob Joseph
>
>
>
> ----- Original Message -----
> From: <jacobmj,AT,mbay,DOT,net>
> To: <cipe-l,AT,inka,DOT,de>
> Cc: <ewheeler,AT,kaico,DOT,com>; <chip,AT,innovates,DOT,com>
> Sent: Thursday, August 23, 2001 4:23 PM
> Subject: Re: Cipe on Windows 2000 w/BSOD
>
>
> > Thanks Chip and Eric.
> >
> > Well, I'm glad to hear its not just me. :-)  On the other hand, it
sounds
> like
> > I'm stuck.  I don't really have the option of getting another linux
> machine to
> > go with my Win2k machine.  I hope I don't have to switch products...  I
> really
> > do like CIPE.  And besides, I really don't feel like remotely
recompiling
> a
> > kernel to support Freeswan.
> >
> > Maybe we should go to the source. :) Damion, can you offer any help or
> does it
> > seem that Windows 2000 is not quite yet ready to go?  (Well, let me
> clarify
> > that; of course Win2k or any other MS product is not 'ready to go'--Is
> there a
> > workaround for CIPE *ON* Win2k?
> >
> > At this point, I think I can do without Suspend and Hibernate if only
CIPE
> > would actually work.  Does anyone have a working configuration that I
> could
> > take a peek at?  The "Work" network is 10.0.0.0/24 with a GW of
> 10.0.0.254.  I
> > am only on the Internet, so I don't have an internal IP.  I'm still a
bit
> > confused of how to configure CIPE-Win32.  I do think I have it installed
> > correctly.  I used the Add hardware wizard to add the Adapter and then
did
> > the "cipesrv install."  I also started the service after a reboot, then
> used
> > the cipe control panel with a reboot afterwards.  I've tried with and
> without
> > setting an IP in the network connection properties.  Any suggestions?
> >
> >
> > Thanks,
> > Jacob Joseph
> >
> >
> >
> > ----- Original Message -----
> > From: <ewheeler,AT,kaico,DOT,com>
> > To: <jacobmj,AT,mbay,DOT,net>
> > Cc: <cipe-l,AT,inka,DOT,de>
> > Sent: Wednesday, August 22, 2001 10:41 PM
> > Subject: Re: Cipe on Windows 2000
> >
> >
> > > I've tried to get w2k workingand I've had no luck this far.  I do know
> > > that if I right-click on the device and select disable, my system
turns
> > > itself off hard!  It spins down hd, fans, etc...  Dunno how it flipped
> > > that APCI powerbutton, but it sure did!
> > >
> > > --Eric
> > >
> > > On Thu, 23 Aug 2001 jacobmj,AT,mbay,DOT,net wrote:
> > >
> > > > Hello all.  I'm having a bit of a hard time converting one end of my
> CIPE
> > > > VPN from a linux box to a Win2k machine.  The Linux machine used to
> serve as
> > > > a gateway for my small masqueraded subnet at home, but now the Win2k
> machine
> > > > is all alone on the Internet.  What I need to do is to be able to
> connect
> > > > from that one machine to the subnet behind the Linux machine at
work.
> In
> > > > configuring Cipe-Win32, I've encountered quite a few problems with
> IPs, so,
> > > > to keep it short, could someone simply send me a CIPE options
> file(minus the
> > > > IPs and hash :) as well as the corresponding options to use within
the
> CIPE
> > > > control panel.  My main issue is with setting the Local VPN IP on
the
> > > > Windows 2000 machine.  Is it correct to set it within the TCP
options
> in the
> > > > network control panel?
> > > >
> > > > I could go into much greater detail, but the problem is probably a
> simple
> > > > setting that I have wrong.
> > > >
> > > > One other thing, is anyone else getting a BSOD(PFN list corrupt)
when
> > > > disabling the CIPE network adapter in the network control panel?
This
> is
> > > > preventing my machine from entering suspend or hibernate mode.  My
> only fix
> > > > thus far is to reboot into safe mode and disable the CIPE VPN
adapter
> within
> > > > device manager.
> > > >
> > > >
> > > >
> > > > Thanks for the help,
> > > > Jacob Joseph
> >
> >
> >
> > --
> > Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> > Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> > Other commands available with "help" in body to the same address.
> > CIPE info and list archive:
> <URL:http://sites.inka.de/~bigred/devel/cipe.html>
> >
>
>
> --
> Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> Other commands available with "help" in body to the same address.
> CIPE info and list archive:
<URL:http://sites.inka.de/~bigred/devel/cipe.html>
>





<< | Thread Index | >> ]    [ << | Date Index | >> ]