I just wanted to come on line and say thanks to Dave and Xiaodan. I have
finally configured a fairly complex internal network complete with routing,
interior domain names, and NAT from the inside to the outside.
Pretty flipping cool I must admit!
So thanks again to you guys. From now on when someone has a question about
this stuff I have some sophisticated examples that I can volunteer.
There are two things that I never did get working but I gave up on both of
them and found a better way to do things.
The first was that I was trying to subnet 10 two different way. (10.0.0/24
and 10.1/16 and 10.2/16) Some of the code allowed it but other routines
didn’t like it (nameserver).
The other thing I never got to work was the ‘route add -interface’. It gave
the illusion of working but didn’t. The deal was that there was a host that
insisted on being 10.0.0.24/24 but the only convenient network to plug it
into was 10.1/16. The route add -interface is supposed to tell routing to
transmit a packet to this IP address (10.0.0.24) on a specific interface
(10.1) even though it is otherwise wrong. The route program DOES put the
correct route in the routing table but Tcpip does not honor it when trying
to transmit the packet.
Thanks again a million times. Really. Now I’m ready to tackle the word.
Or maybe mail (Oh NO!)
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:aa72c5$qkl$1@nntp.qnx.com…
“Bill Caroselli (Q-TPS)” <> QTPS@earthlink.net> > wrote:
Should the ‘route add -interface’ work with TCP/IP v5.0?
(see below)
I couldn’t find “route add -interface” in my copy of the
TCP/IP v5 docs.
But, that’s not definitive.
-David
“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > wrote in message
news:aa4obq$ba4$> 1@inn.qnx.com> …
Using QNX 4.25E and TCP/IP v 5.0
I have three interfaces, en1, en2 and en3. My routing tables are set
up
so
that network 10.0/16 is routed to en1, and this works.
OK. Now it gets goofy.
I have a host 10.0.0.24 that is physically plugged into the segment on
en3.
I believe that I should be able to add the line:
route add -interface 10.0.0.24 10.2.0.2
where 10.2.0.2 is the interface for this host on en3.
When I try:
route get 10.0.0.24
then all the correct information is displayed. The packet will be
addressed
to 10.0.0.24 on en1.
BUT, it doesn’t happen. Can I add a route to an interface in TCP/IP
v5.0?
(BTW, The docs say that I can. Look at the page for route under ‘add’
under
‘-interface’.)
\
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.