How can I test the Loopback mode in my Network Driver!!

QNX Newsgroups (Archives) qdn.public.ddk.network
#1

Could anyone plz tell me how can I test the loopback mode for my driver
code:
I do the following:

In linux, we do
ifconfig wn0 192.168.0.88 up ( with the netmask as 255.255.255.0)
ping 192.168.0.99, my ping goes through
Similarly, How can I do it in QNX??

This is wat happens with BIG TCPIP

  1. mount -Tio-net mydriver.so (whose interface is en0)
  2. mount -Tio-net -oif=en0:11.2 /lib/dll/npm-tcpip.so (BIG TCP/IP)
    tcpip: unrecognised option: if
    (What does this mean?)
  3. ifconfig en0 11.0.0.2 up
  4. route add 11.0.0.1 en0
    en0: bad Value
    (What does this mean? This entry doesn’t get updated in my routing table,
    which inturn doesn’t help me in testing for loopback mode)
    ping 11.0.0.1

Could anyone help me how can i test loopback mode as I could not find any
documentation off, even in DDK.

Thanks
Jalaja




What does it mean?



Thanks
Jalaja

#2

Jalaja <jganapat@storage.com> wrote:

  1. mount -Tio-net mydriver.so (whose interface is en0)
  2. mount -Tio-net -oif=en0:11.2 /lib/dll/npm-tcpip.so (BIG TCP/IP)
    tcpip: unrecognised option: if
    (What does this mean?)

The use of if=en0:… with the tiny stack is not supported with the
big stack - you have to use ifconfig/route.

  1. ifconfig en0 11.0.0.2 up
  2. route add 11.0.0.1 en0
    en0: bad Value

This is just the wrong arguments to route. Take a look for the proper
ones in the helpviewer.

chris

\

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

#3
  1. mount -Tio-net mydriver.so (whose interface is en0)
  2. mount -Tio-net -oif=en0:11.2 /lib/dll/npm-tcpip.so (BIG TCP/IP)
    tcpip: unrecognised option: if
    (What does this mean?)


    The use of if=en0:… with the tiny stack is not supported with the
    big stack - you have to use ifconfig/route.

If you look at the command above, I have given as BIG TCPIP, not the tiny
one.
So, for BIG TCPIP, also if=en0 is not supported???


But the Helper view says even Tiny tcpip supports if. Infact I copied it
from the Helper view.

  1. ifconfig en0 11.0.0.2 up
  2. route add 11.0.0.1 en0
    en0: bad Value
    This is just the wrong arguments to route. Take a look for the proper
    ones in the helpviewer.
    I am sorry to say that I could not find any help in this regard in the

Helper view.

chris

\

cdm@qnx.com > “The faster I go, the behinder I get.”
Chris McKillop – Lewis Carroll –
Software Engineer, QSSL

#4

Jalaja <jganapat@storage.com> wrote:
:> > 1. mount -Tio-net mydriver.so (whose interface is en0)
:> > 2. mount -Tio-net -oif=en0:11.2 /lib/dll/npm-tcpip.so (BIG TCP/IP)
:> > tcpip: unrecognised option: if
:> > (What does this mean?)
:> >
:>
:> The use of if=en0:… with the tiny stack is not supported with the
:> big stack - you have to use ifconfig/route.

: If you look at the command above, I have given as BIG TCPIP, not the tiny
: one.
: So, for BIG TCPIP, also if=en0 is not supported???

Correct. As Chris stated above and as the error message indicates.


: But the Helper view says even Tiny tcpip supports if. Infact I copied it
: from the Helper view.

So the helpviewer is correct. This option is supported by the tiny stack.

:>
:> >
:> > 3. ifconfig en0 11.0.0.2 up
:> > 4. route add 11.0.0.1 en0
:> > en0: bad Value
:> This is just the wrong arguments to route. Take a look for the proper
:> ones in the helpviewer.
: I am sorry to say that I could not find any help in this regard in the
: Helper view.

The route to the 11 network will be created automatically for you anyway
since you are directly connected to it (as per your ifconfig). In other
words, you shouldn’t have to add any additional route to reach 11.1.

After you mount driver and stack and do your ifconfig, what does
‘netstat -in’, ‘netstat -rn’ produce?

-seanb

-seanb