configuration question

All righty here is the situation I am trying to set up.

We have a network of QNX 4 boxes here in our office.

We also have a small network of computers in another city which I can
configure anyway I like for TCPIP.

I am able to make a SLIP connection from a box here in our office to one of
the boxes in the other city with no problem. However I wish to be able to
access the other machines in the other city from this same slip connection.
I have fiddled with routing and arp settings with no success and now must
ask if anyone else has ever set this up?

Ideally I would like the following:

192.168.4.230 ( in our office here ) makes a slip connection to
192.168.4.239 in another city ( they can ping each other no problems ).

I want 192.168.4.230 to be able to ping 192.168.4.236 which is another
computer on the same network as 192.168.4.239…

Sheldon Parkes

Sheldon Parkes <sheldon@onlinedata.com> wrote:

All righty here is the situation I am trying to set up.

We have a network of QNX 4 boxes here in our office.

We also have a small network of computers in another city which I can
configure anyway I like for TCPIP.

I am able to make a SLIP connection from a box here in our office to one of
the boxes in the other city with no problem. However I wish to be able to
access the other machines in the other city from this same slip connection.
I have fiddled with routing and arp settings with no success and now must
ask if anyone else has ever set this up?

Ideally I would like the following:

192.168.4.230 ( in our office here ) makes a slip connection to
192.168.4.239 in another city ( they can ping each other no problems ).

I want 192.168.4.230 to be able to ping 192.168.4.236 which is another
computer on the same network as 192.168.4.239…

Have your local office in 192.168.4.x netmask 255.255.255.0;
Have your remote office in 192.168.5.x netmask 255.255.255.0;
Have slip established between 192.168.4.1 and 192.168.5.1;
Then have ALL the 192.168.5.x node add route like:
route add -net 192.168.4 192.168.5.1
Have all the 192.168.4.x node add route like:
route add -net 192.168.5. 192.168.4.1

-xtang

Here’s a question: Should the slip connections have their own IP address? or
can they use the IP addresses of the computers involved. ie in the
slip.login should I use new IP addresses or use the same ones that the
computer uses from the /etc/hosts file?

I tried out your set up Xiaodan and could not get it to work for some
reason. One thing I did notice was that when I added the route on the remote
computers it came up on the ethernet interface instead of the slip interface
( which is why I asked the question above )

Sheldon

“Xiaodan Tang” <xtang@qnx.com> wrote in message
news:ahmncb$hpi$2@nntp.qnx.com

Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
All righty here is the situation I am trying to set up.

We have a network of QNX 4 boxes here in our office.

We also have a small network of computers in another city which I can
configure anyway I like for TCPIP.

I am able to make a SLIP connection from a box here in our office to one
of
the boxes in the other city with no problem. However I wish to be able
to
access the other machines in the other city from this same slip
connection.
I have fiddled with routing and arp settings with no success and now
must
ask if anyone else has ever set this up?

Ideally I would like the following:

192.168.4.230 ( in our office here ) makes a slip connection to
192.168.4.239 in another city ( they can ping each other no problems ).

I want 192.168.4.230 to be able to ping 192.168.4.236 which is another
computer on the same network as 192.168.4.239…

Have your local office in 192.168.4.x netmask 255.255.255.0;
Have your remote office in 192.168.5.x netmask 255.255.255.0;
Have slip established between 192.168.4.1 and 192.168.5.1;
Then have ALL the 192.168.5.x node add route like:
route add -net 192.168.4 192.168.5.1
Have all the 192.168.4.x node add route like:
route add -net 192.168.5. 192.168.4.1

-xtang
\

Sheldon Parkes <sheldon@onlinedata.com> wrote:

Here’s a question: Should the slip connections have their own IP address? or
can they use the IP addresses of the computers involved. ie in the
slip.login should I use new IP addresses or use the same ones that the
computer uses from the /etc/hosts file?

I tried out your set up Xiaodan and could not get it to work for some
reason. One thing I did notice was that when I added the route on the remote
computers it came up on the ethernet interface instead of the slip interface
( which is why I asked the question above )

It is my understanding that you can assign same address to both
interface (slip and ether). The route add shows en0 is also correct.

Note you have to set BOTH routing table to make “ping” working.
Set only one side won’t help.

You should be able to tell if packet is moving through netstat -ni,
watch the Ipkts/Opkts number on each interface…

The first step is try to ping on the slip machine, see if slip
works correct. Then on other node (with route add settings).

You also need to enable forwarding on the 2 slip node (Socket -d
forward).

Also, you are suppose to use ppp instead of slip, unless you absolutely
sure about the serial settings.

-xtang

Sheldon

“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:ahmncb$hpi$> 2@nntp.qnx.com> …
Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
All righty here is the situation I am trying to set up.

We have a network of QNX 4 boxes here in our office.

We also have a small network of computers in another city which I can
configure anyway I like for TCPIP.

I am able to make a SLIP connection from a box here in our office to one
of
the boxes in the other city with no problem. However I wish to be able
to
access the other machines in the other city from this same slip
connection.
I have fiddled with routing and arp settings with no success and now
must
ask if anyone else has ever set this up?

Ideally I would like the following:

192.168.4.230 ( in our office here ) makes a slip connection to
192.168.4.239 in another city ( they can ping each other no problems ).

I want 192.168.4.230 to be able to ping 192.168.4.236 which is another
computer on the same network as 192.168.4.239…

Have your local office in 192.168.4.x netmask 255.255.255.0;
Have your remote office in 192.168.5.x netmask 255.255.255.0;
Have slip established between 192.168.4.1 and 192.168.5.1;
Then have ALL the 192.168.5.x node add route like:
route add -net 192.168.4 192.168.5.1
Have all the 192.168.4.x node add route like:
route add -net 192.168.5. 192.168.4.1

-xtang
\

Hi Xiaodan

I know your the TCP/IP guru but are you sure about this one? I really don’t
think this is so.

“Xiaodan Tang” <xtang@qnx.com> wrote in message
news:ahmtg7$n0s$2@nntp.qnx.com

It is my understanding that you can assign same address to both
interface (slip and ether). The route add shows en0 is also correct.

“Bill Caroselli (Q-TPS)” <QTPS@earthlink.net> wrote:

Hi Xiaodan

I know your the TCP/IP guru but are you sure about this one? I really don’t
think this is so.

OK, I confess.

I am positive I did that myself on ppp interface. And I just hope
slip interface will do same. Unless that perticular stack (4.25?)
do not support that…

-xtang


“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:ahmtg7$n0s$> 2@nntp.qnx.com> …
It is my understanding that you can assign same address to both
interface (slip and ether). The route add shows en0 is also correct.

The slip connection is working fine. Each node on either end can ping the
other one. The problem is trying to ping another machine on the remote end.
I put in the route add -net statements and as far as I can tell ( which is
not very far ) the output from netstat -r makes sense but I can’t ping from
the slip client to another node on the slip hosts side…

If it will help I can post the netstat -r output

Sheldon

“Xiaodan Tang” <xtang@qnx.com> wrote in message
news:ahmtg7$n0s$2@nntp.qnx.com

Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
Here’s a question: Should the slip connections have their own IP
address? or
can they use the IP addresses of the computers involved. ie in the
slip.login should I use new IP addresses or use the same ones that the
computer uses from the /etc/hosts file?

I tried out your set up Xiaodan and could not get it to work for some
reason. One thing I did notice was that when I added the route on the
remote
computers it came up on the ethernet interface instead of the slip
interface
( which is why I asked the question above )

It is my understanding that you can assign same address to both
interface (slip and ether). The route add shows en0 is also correct.

Note you have to set BOTH routing table to make “ping” working.
Set only one side won’t help.

You should be able to tell if packet is moving through netstat -ni,
watch the Ipkts/Opkts number on each interface…

The first step is try to ping on the slip machine, see if slip
works correct. Then on other node (with route add settings).

You also need to enable forwarding on the 2 slip node (Socket -d
forward).

Also, you are suppose to use ppp instead of slip, unless you absolutely
sure about the serial settings.

-xtang

Sheldon

“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:ahmncb$hpi$> 2@nntp.qnx.com> …
Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
All righty here is the situation I am trying to set up.

We have a network of QNX 4 boxes here in our office.

We also have a small network of computers in another city which I can
configure anyway I like for TCPIP.

I am able to make a SLIP connection from a box here in our office to
one
of
the boxes in the other city with no problem. However I wish to be
able
to
access the other machines in the other city from this same slip
connection.
I have fiddled with routing and arp settings with no success and now
must
ask if anyone else has ever set this up?

Ideally I would like the following:

192.168.4.230 ( in our office here ) makes a slip connection to
192.168.4.239 in another city ( they can ping each other no
problems ).

I want 192.168.4.230 to be able to ping 192.168.4.236 which is
another
computer on the same network as 192.168.4.239…

Have your local office in 192.168.4.x netmask 255.255.255.0;
Have your remote office in 192.168.5.x netmask 255.255.255.0;
Have slip established between 192.168.4.1 and 192.168.5.1;
Then have ALL the 192.168.5.x node add route like:
route add -net 192.168.4 192.168.5.1
Have all the 192.168.4.x node add route like:
route add -net 192.168.5. 192.168.4.1

-xtang


\

Sheldon Parkes <sheldon@onlinedata.com> wrote:

The slip connection is working fine. Each node on either end can ping the
other one. The problem is trying to ping another machine on the remote end.
I put in the route add -net statements and as far as I can tell ( which is
not very far ) the output from netstat -r makes sense but I can’t ping from
the slip client to another node on the slip hosts side…

And you are sure both the slip node have tcpip started with “forward” ?
Did you forget route add -net on the slip machine ?

-xtang

If it will help I can post the netstat -r output

Sheldon

“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:ahmtg7$n0s$> 2@nntp.qnx.com> …
Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
Here’s a question: Should the slip connections have their own IP
address? or
can they use the IP addresses of the computers involved. ie in the
slip.login should I use new IP addresses or use the same ones that the
computer uses from the /etc/hosts file?

I tried out your set up Xiaodan and could not get it to work for some
reason. One thing I did notice was that when I added the route on the
remote
computers it came up on the ethernet interface instead of the slip
interface
( which is why I asked the question above )

It is my understanding that you can assign same address to both
interface (slip and ether). The route add shows en0 is also correct.

Note you have to set BOTH routing table to make “ping” working.
Set only one side won’t help.

You should be able to tell if packet is moving through netstat -ni,
watch the Ipkts/Opkts number on each interface…

The first step is try to ping on the slip machine, see if slip
works correct. Then on other node (with route add settings).

You also need to enable forwarding on the 2 slip node (Socket -d
forward).

Also, you are suppose to use ppp instead of slip, unless you absolutely
sure about the serial settings.

-xtang

Sheldon

“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:ahmncb$hpi$> 2@nntp.qnx.com> …
Sheldon Parkes <> sheldon@onlinedata.com> > wrote:
All righty here is the situation I am trying to set up.

We have a network of QNX 4 boxes here in our office.

We also have a small network of computers in another city which I can
configure anyway I like for TCPIP.

I am able to make a SLIP connection from a box here in our office to
one
of
the boxes in the other city with no problem. However I wish to be
able
to
access the other machines in the other city from this same slip
connection.
I have fiddled with routing and arp settings with no success and now
must
ask if anyone else has ever set this up?

Ideally I would like the following:

192.168.4.230 ( in our office here ) makes a slip connection to
192.168.4.239 in another city ( they can ping each other no
problems ).

I want 192.168.4.230 to be able to ping 192.168.4.236 which is
another
computer on the same network as 192.168.4.239…

Have your local office in 192.168.4.x netmask 255.255.255.0;
Have your remote office in 192.168.5.x netmask 255.255.255.0;
Have slip established between 192.168.4.1 and 192.168.5.1;
Then have ALL the 192.168.5.x node add route like:
route add -net 192.168.4 192.168.5.1
Have all the 192.168.4.x node add route like:
route add -net 192.168.5. 192.168.4.1

-xtang


\