Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - io-pkt / pppd: forwarding IP packets doesn't work: (5 Items)
   
io-pkt / pppd: forwarding IP packets doesn't work  
Our systems consist of two x86 machines (A and B). Both are
connected to a 100 M/Bit LAN.

An analog modem is connected to the serial port of the machine A. From our office (Windows XP) I dial into machine A 
using PPP protocol. From my
computer in the office I want to get access to the machine A and the machine B.

The complete configuration is working on QNX 6.3.2.

With QNX 6.4 M8 I can dial into the machine A and can access the machine A from my Windows machine using TELNET + FTP.

But I can't access the machine B from the Windows machine.


In the attachment is the startup script and the modem script.


What must we change, to get IP forwaring working with io-pkt ?
Attachment: Compressed file modem.zip 1.23 KB
Re: io-pkt / pppd: forwarding IP packets doesn't work  
On Thu, Oct 23, 2008 at 05:20:30AM -0400, Matthias Klein wrote:
> Our systems consist of two x86 machines (A and B). Both are
> connected to a 100 M/Bit LAN.
> 
> An analog modem is connected to the serial port of the machine A. From our office (Windows XP) I dial into machine A 
using PPP protocol. From my
> computer in the office I want to get access to the machine A and the machine B.
> 
> The complete configuration is working on QNX 6.3.2.
> 
> With QNX 6.4 M8 I can dial into the machine A and can access the machine A from my Windows machine using TELNET + FTP.

> 
> But I can't access the machine B from the Windows machine.
> 
> 
> In the attachment is the startup script and the modem script.
> 
> 
> What must we change, to get IP forwaring working with io-pkt ?

Does you windows box have a route to machine B using machine A
as the gateway?  Does machine B have a route back?

-seanb
RE: io-pkt / pppd: forwarding IP packets doesn't work  
First I guess the sysinit in your attached file is not what you are
using on machine A. There is no driver on command line or mounted onto
before the script calls waitfor enX. 

The other parts of the scripts looks fine. I assume the machine A and
machine B are on the same LAN cable when you are saying the are on the
same LAN, i.e., they are not seeing each other through a router or
switch. 

I think you may start to investigate by looking into tcpdump. 

For example let us say the scenario is, 
Your windows box (192.168.0.2) --ppp-- machine A (ppp=192.168.0.1 and
en0 192.168.1.1) ===LAN CABLE== machine B (192.168.1.2). That is,
machine A connects network 192.168.0.0/24 and 192.168.1.0/24.

On machine A, you may run tcpdump -i en0 to see if the packet with
src=192.168.0.2 (that is, from you windows box in your office) and
dst=192.168.1.2 is transimited through en0. If that is only what you
see, the problem is that somehow the machine B does not reply the
request. You may do further for investigation by doing tcpdump on
machine B also. And you may also try on machine B, route add 192.168.0.0
192.168.1.1. So, when the packet with src=192.168.0.2 and
dst=192.168.1.2 is received by machine B, it knows to send the reply to
192.168.1.1 as the first hop which is machine A. 

Thanks
Weijie


-----Original Message-----
From: Matthias Klein [mailto:community-noreply@qnx.com] 
Sent: October 23, 2008 5:21 AM
To: ionetmig-networking
Subject: io-pkt / pppd: forwarding IP packets doesn't work

Our systems consist of two x86 machines (A and B). Both are
connected to a 100 M/Bit LAN.

An analog modem is connected to the serial port of the machine A. From
our office (Windows XP) I dial into machine A using PPP protocol. From
my
computer in the office I want to get access to the machine A and the
machine B.

The complete configuration is working on QNX 6.3.2.

With QNX 6.4 M8 I can dial into the machine A and can access the machine
A from my Windows machine using TELNET + FTP.

But I can't access the machine B from the Windows machine.


In the attachment is the startup script and the modem script.


What must we change, to get IP forwaring working with io-pkt ?


_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post15435
Re: RE: io-pkt / pppd: forwarding IP packets doesn't work  
>Does you windows box have a route to machine B using machine A as the gateway?  

Yes, the windows box has machine B as gateway.

> Does machine B have a route back?

Not direct. I think that is the purpose of the "proxyarp" option of pppd.


>First I guess the sysinit in your attached file is not what you are
>using on machine A. There is no driver on command line or mounted onto
>before the script calls waitfor enX. 

The sysinit file is from machine A. The driver is automatically loaded by enum-devices:

io-pkt-v4-hc -p tcpip forward -p qnet &
waitfor /net
enum-devices
waitfor /dev/io-net/en0
ifconfig en0 192.9.200.101  up

(The sysinit of machine B looks similar)

>I assume the machine A and machine B are on the same LAN cable when you are 
>saying the are on the same LAN, i.e., they are not seeing each other through a 
>router or switch. 

Machine A (192.9.200.101) and machine B (192.9.200.102) are connected using a normal switch.

The modem dial-out connection of the windows box has a static IP adress in the 192.9.200.x segment (the same as machine 
A and B) and has machine A as gateway.

I think you may start to investigate by looking into tcpdump. 


Exact the same configuration (sysinit's and modem script) are working fine on QNX 6.3.2. I only replaced the text "io-
net" with "io-pkt".


In the next days I will try some route setting and try to investigate using tcpdump.
Re: RE: io-pkt / pppd: forwarding IP packets doesn't work  
I have found a solution:

The PPP IP-adresses must be on a diffetent segment than the local IP-adresses (e.g.: local 192.9.200.x and PPP 192.9.201
.x).
And the machine B must have the machine A as gateway.

On QNX 6.3.2 with io-net is was no problem if all IP-adresses are in the same segment (e.g. 192.9.200.x). And no gateway
 was needed.


In the attachment are my working sysinit and modem scripts ...
Attachment: Compressed file modem_new.zip 1.98 KB