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

Subject: Re: Routing Win32 - Linux
From: Gert.Vandelaer,AT,medisearch-int,DOT,com
Date: Thu, 23 Aug 2001 14:21:02 +0200

Just to inform you,

I did another setup, with the exact same routing info, but between 2 linux
boxes,
and it worked within seconds ... no problems at all.

I did notice however, that there was some extra information in the linux
consoles about "Peer coming up / down" "correct key" ...
Things I've never noticed when trying to connect the NT to the Linux box
...
Is this normal behaviour ...

Please tell me what else info you need ...
I'd really like to get this working ;-)

I'm now going to setup CIPE between 2 WinNT boxes, where 1 of them is
behind a linux firewall ...
maybe more success with this setup ...

Bye,
Gert

                                                                              
                                                            
                    Gert.Vandelaer@medisear                                   
                                                            
                    ch-int.com                     To:     Damion K.Wilson 
<dwilson,AT,ibl,DOT,bm>                                               
                    Sent by:                       cc:     
cipe-l,AT,inka,DOT,de     
                                                            
                    owner-cipe-l,AT,inka,DOT,de           Subject:     Re: 
Routing 
Win32 - Linux                                                 
                                                                              
                                                            
                                                                              
                                                            
                    22/08/2001 11:38 AM                                       
                                                            
                                                                              
                                                            
                                                                              
                                                            

Hy Damion,

Maybe I should add that both PC's are not on the same hub, the 10.10.10.0
and 192.168.1.0 networks are on a different hub than the 192.168.0.0
network  (this to make sure no weird broadcasts conflicts with SMB later on
...)

the 10.10.10.0 network is the fake-internet
the 192.168.0.1 nework is the Remote LAN
the 192.168.0.0 network is the Local LAN

So I changed the CIPE settings as you suggested,

On Linux Box :
me   10.10.10.1
peer 10.10.10.10
local ip  192.168.0.50 (so a different ip than the eth0, as suggested)
ptp  192.168.1.100

ip-up : adds a route for the 192.168.1.0 network via 192.168.1.100

On NT Box :
me 10.10.10.10
peer 10.10.10.1
local ip  192.168.1.100
ptp  192.168.0.50

and still no succes,
when I ping 192.168.1.100 from the linux, I can see echo-requests being
sent out via cipcb0 interface (tcpdump),
but on the NT box I can only see blank lines coming in the CIPE interface
(windump), every echo-request results on the NT-BOX with "|ether
", no echo-reply is being sent.
The packets seem to arrive empty ... I'm also sure that the key is correct.

And when I try to ping 192.168.0.50 from the NT box, i get "no route to
host", and i can't do "route add 192.168.0.0 mask 255.255.255.0
192.168.0.50" because of the "The route addtion failed : 87" error ...

Maybe I'm overlooking some routing issue ?

I also didn't quite understand what you ment with "the netmask on the linux
box is wrong" ...
anyway, with this new setup I think all masks and routes should be fine ?

Is there any other network / dump / debug info you require so you can get a
better picture of my test-setup ?

Thnx,

Cya,
Gert

                    Damion
                    K.Wilson             To:
Gert.Vandelaer,AT,medisearch-int,DOT,com
                    <dwilson@ibl.        cc:     cipe-l,AT,inka,DOT,de
                    bm>                  Subject:     Re: Routing Win32 -
Linux

                    22/08/2001
                    03:01 AM

I think that the netmask on the Linux side may be wrong for a point to
point
interface.

Also, you shouldn't have to setup routing info unless either one of the
CIPE
boxes is attached to a network that the other is not directly attached to
and
needs to reach. CIPE provides a new directly attached network and either
peer
should be able to reach the other without a gateway involved.

It appears as though you are trying to route packets intended for CIPE
through the ethernet adapter IP addresses. If that is what you are
attempting, then you are chasing a red herring because CIPE doesn't work
like
that. Think of CIPE providing an additional network card for your computer.

With that in mind, setting the CIPE adapter ip address to match the
Ethernet
adapter's IP network address is a bad idea.

DKW

On Tuesday 21 August 2001 07:31, you wrote:
> Hya all,
>
> I'm still trying to get a CIPE connection going between a WinNT and
Linux.
> Cipe on the Linux box seems to be working correct.
> insmod cipcb ; cipe-cb ...
> runs in debug mode ...
> key's are exact the same (tripple checked this ...)
>
> Linux Box looks like this:
> "netstat -nr"
> Kernel IP routing table
> Destination    Gateway   Genmask   Flags      MSS Window  irtt    Iface
> 192.168.1.0    192.168.1.50   255.255.255.0   UG   40   0          0
> cipcb0
> 192.168.1.0    0.0.0.0        255.255.255.0   U    40   0          0
> cipcb0
> 192.168.0.0    0.0.0.0        255.255.255.0   U    40   0          0
> eth0
> 10.10.10.0     0.0.0.0        255.255.255.0   U    40   0          0
> eth1
> 127.0.0.0 0.0.0.0        255.0.0.0 U     40   0          0        lo
>
> "ifconfig"
> cipcb0    Link encap:IPIP Tunnel  HWaddr
>           inet addr:192.168.0.10  P-t-P:192.168.1.50  Mask:255.255.255.0
>           UP POINTOPOINT RUNNING NOARP  MTU:1442  Metric:1
>           RX packets:72 errors:1 dropped:0 overruns:0 frame:1
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>
> eth0      Link encap:Ethernet  HWaddr 00:10:4B:06:7F:D2
>           inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:27445 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:26839 errors:0 dropped:0 overruns:0 carrier:3
>           collisions:3 txqueuelen:100
>           Interrupt:11 Base address:0x6c00
>
> eth1      Link encap:Ethernet  HWaddr 00:10:4B:79:7D:16
>           inet addr:10.10.10.10  Bcast:10.255.255.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:46305 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:13724 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:9 Base address:0x7c00
>
> Windows NT box:
> "ipconfig"
> Windows NT IP Configuration
> Ethernet adapter El90xnd3:
>      IP Address. . . . . . . . . : 192.168.1.50
>      Subnet Mask . . . . . . . . : 255.255.255.0
>      Default Gateway . . . . . . :
>
> Ethernet adapter El90xnd1:
>      IP Address. . . . . . . . . : 10.10.10.1
>      Subnet Mask . . . . . . . . : 255.255.255.0
>      Default Gateway . . . . . . :
>
> Ethernet adapter CIPE2:
>      IP Address. . . . . . . . . : 10.10.10.2
>      Subnet Mask . . . . . . . . : 255.255.255.0
>      Default Gateway . . . . . . :
>
>
> "route print"
>
===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 a0 24 d6 b1 88 ...... 3Com 3C90x Ethernet Adapter
> 0x3 ...00 a0 24 d3 f0 ed ...... 3Com 3C90x Ethernet Adapter
> 0x4 ...08 00 58 00 00 01 ...... DKW Heavy Industries VPN Adapter.
>
===========================================================================
>
===========================================================================
> Active Routes:
> Network Destination        Netmask          Gateway       Interface
Metric
>        10.10.10.0    255.255.255.0       10.10.10.1      10.10.10.1
1
>        10.10.10.0    255.255.255.0       10.10.10.2      10.10.10.2
1
>        10.10.10.1  255.255.255.255        127.0.0.1       127.0.0.1
1
>        10.10.10.2  255.255.255.255        127.0.0.1       127.0.0.1
1
>    10.255.255.255  255.255.255.255       10.10.10.1      10.10.10.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.50    192.168.1.50
1
>      192.168.1.50  255.255.255.255        127.0.0.1       127.0.0.1
1
>     192.168.1.255  255.255.255.255     192.168.1.50    192.168.1.50
1
>         224.0.0.0        224.0.0.0       10.10.10.1      10.10.10.1
1
>         224.0.0.0        224.0.0.0       10.10.10.2      10.10.10.2
1
>         224.0.0.0        224.0.0.0     192.168.1.50    192.168.1.50
1
>   255.255.255.255  255.255.255.255     192.168.1.50    192.168.1.50
1
>
===========================================================================
>
> and I can't add a route for the 192.168.0.0 network ...
>
> "route add 192.168.0.0 mask 255.255.255.0 10.10.10.2" gives me always the
> 87 error "The route addtion failed : 87"
>
> which route should I add than ?
>
> When I ping from Linux-box to Win-NT box I can see via (manually patched
> tcpdump, because of libpcap6) tcpdump -i cipcb0
> that there is a icmp-echo request being sent out, but on the NT-Box
nothing
> is being received (checked via Windump)
> So the packets destined for the 192.168.1.0 network are sent out over the
> CIPE-Linux device, but are not received by the Win-NT.
>
> In the other direction, well ... I can't even add a route for the
> 192.168.0.0 network (except when I use gateway 10.10.10.1, but this is
the
> external Interface, and than it works off course via simple
IP-forwarding,
> and not via tunnel)
>
> Please tell me what more information you need (or less information),
> I'm stumped on this one ...
>
>
> Oh Yes, when the CIPE-link comes up, I can see NT-Box go "Send CT_PING",
> and than on the Linux "Received CT_PING ; Sending CT_PONG", but I don't
see
> "CT_PING received" on the NT-Box after that, maybe this is crucial
> information also ? :-)
>
>
> Thnx,
> Cya,
> Gert
>
>
>
> --
> 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 | >> ]