netstat and route

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

How do ‘netstat’ and ‘route’ work in qrtp?

$ netstat
netstat: no namelist
$ netstat -A
netstat: no namelist
$ netstat -a
netstat: no namelist
$ netstat -n
netstat: no namelist
$

$ use route
route [-n] [-q] [-v] command [[modifiers] args]

Options:
-n Prevent attempts to print host and network names symbolically
-v (verbose) Print additional details.
-q Suppress all output.

Where:
add Add a route.
flush Remove all routes.
delete Delete a specific route.
change Change aspects of a route (such as its gateway).
get Lookup and display the route for a destination.
monitor Continuously report any changes to the routing information.
$ route monitor
route: socket: No such file or directory

\

Gordon Man

2

netstat and route with with the big stack implimentation (npm-tcpip.so)
They don’t work with the tiny stack (npm-ttcpip.so) which is used
by default.

Peter

gmman@qnx.com wrote:
: How do ‘netstat’ and ‘route’ work in qrtp?

: $ netstat
: netstat: no namelist
: $ netstat -A
: netstat: no namelist
: $ netstat -a
: netstat: no namelist
: $ netstat -n
: netstat: no namelist
: $

: $ use route
: route [-n] [-q] [-v] command [[modifiers] args]

: Options:
: -n Prevent attempts to print host and network names symbolically
: -v (verbose) Print additional details.
: -q Suppress all output.

: Where:
: add Add a route.
: flush Remove all routes.
: delete Delete a specific route.
: change Change aspects of a route (such as its gateway).
: get Lookup and display the route for a destination.
: monitor Continuously report any changes to the routing information.
: $ route monitor
: route: socket: No such file or directory


: –
: Gordon Man

3

How do I change to big stack implimentation? Thanks in advance.

Peter Martin <peterm@qnx.com> wrote:
: netstat and route with with the big stack implimentation (npm-tcpip.so)
: They don’t work with the tiny stack (npm-ttcpip.so) which is used
: by default.

: Peter
:
: gmman@qnx.com wrote:
: : How do ‘netstat’ and ‘route’ work in qrtp?

: : $ netstat
: : netstat: no namelist
: : $ netstat -A
: : netstat: no namelist
: : $ netstat -a
: : netstat: no namelist
: : $ netstat -n
: : netstat: no namelist
: : $

: : $ use route
: : route [-n] [-q] [-v] command [[modifiers] args]

: : Options:
: : -n Prevent attempts to print host and network names symbolically
: : -v (verbose) Print additional details.
: : -q Suppress all output.

: : Where:
: : add Add a route.
: : flush Remove all routes.
: : delete Delete a specific route.
: : change Change aspects of a route (such as its gateway).
: : get Lookup and display the route for a destination.
: : monitor Continuously report any changes to the routing information.
: : $ route monitor
: : route: socket: No such file or directory


: : –
: : Gordon Man

–
Gordon Man

4

gmman@qnx.com wrote:
: How do I change to big stack implimentation? Thanks in advance.

I think (I’m not the expert so I’ll probably get corrected if
I’m wrong) you can edit the file /etc/system/enum/include/net
and change the line:

set(IONET_CMD, io-net -pttcpip -ppppmgr)

to

set(IONET_CMD, io-net -ptcpip -ppppmgr)

and reboot.

: Peter Martin <peterm@qnx.com> wrote:
: : netstat and route with with the big stack implimentation (npm-tcpip.so)
: : They don’t work with the tiny stack (npm-ttcpip.so) which is used
: : by default.

: : Peter
: :
: : gmman@qnx.com wrote:
: : : How do ‘netstat’ and ‘route’ work in qrtp?

: : : $ netstat
: : : netstat: no namelist
: : : $ netstat -A
: : : netstat: no namelist
: : : $ netstat -a
: : : netstat: no namelist
: : : $ netstat -n
: : : netstat: no namelist
: : : $

: : : $ use route
: : : route [-n] [-q] [-v] command [[modifiers] args]

: : : Options:
: : : -n Prevent attempts to print host and network names symbolically
: : : -v (verbose) Print additional details.
: : : -q Suppress all output.

: : : Where:
: : : add Add a route.
: : : flush Remove all routes.
: : : delete Delete a specific route.
: : : change Change aspects of a route (such as its gateway).
: : : get Lookup and display the route for a destination.
: : : monitor Continuously report any changes to the routing information.
: : : $ route monitor
: : : route: socket: No such file or directory


: : : –
: : : Gordon Man

: –
: Gordon Man

5

Steve Tomkins <stomkins@qnx.com> wrote:
: gmman@qnx.com wrote:
: : How do I change to big stack implimentation? Thanks in advance.

: I think (I’m not the expert so I’ll probably get corrected if
: I’m wrong) you can edit the file /etc/system/enum/include/net
: and change the line:
: set(IONET_CMD, io-net -pttcpip -ppppmgr)
: to
: set(IONET_CMD, io-net -ptcpip -ppppmgr)
: and reboot.

I’m not sure how all the things get started automatically, but there
is a difference with the tiny stack from the big stack in that you
need to run ifconfig on it.

I would suggest the following until a better suggestion is provided:

slay io-net
io-net -ptcpip -ppppmgr &
ifconfig en0 up [and any other options you want]

You should now be able to run netstat, with the bigstack.

Peter

: : Peter Martin <peterm@qnx.com> wrote:
: : : netstat and route with with the big stack implimentation (npm-tcpip.so)
: : : They don’t work with the tiny stack (npm-ttcpip.so) which is used
: : : by default.

: : : Peter
: : :
: : : gmman@qnx.com wrote:
: : : : How do ‘netstat’ and ‘route’ work in qrtp?

6

Peter Martin <peterm@qnx.com> wrote:
: Steve Tomkins <stomkins@qnx.com> wrote:
: : gmman@qnx.com wrote:
: : : How do I change to big stack implimentation? Thanks in advance.

: : I think (I’m not the expert so I’ll probably get corrected if
: : I’m wrong) you can edit the file /etc/system/enum/include/net
: : and change the line:
: : set(IONET_CMD, io-net -pttcpip -ppppmgr)
: : to
: : set(IONET_CMD, io-net -ptcpip -ppppmgr)
: : and reboot.

: I’m not sure how all the things get started automatically, but there
: is a difference with the tiny stack from the big stack in that you
: need to run ifconfig on it.

: I would suggest the following until a better suggestion is provided:

: slay io-net
: io-net -ptcpip -ppppmgr &
: ifconfig en0 up [and any other options you want]

: You should now be able to run netstat, with the bigstack.

I think there was an omission of the setuid bit on netstat in the
release.

chmod u+s netstat.

or run as root.

-seanb

7

Peter Martin <peterm@qnx.com> wrote:
: Steve Tomkins <stomkins@qnx.com> wrote:
: : gmman@qnx.com wrote:
: : : How do I change to big stack implimentation? Thanks in advance.

: : I think (I’m not the expert so I’ll probably get corrected if
: : I’m wrong) you can edit the file /etc/system/enum/include/net
: : and change the line:
: : set(IONET_CMD, io-net -pttcpip -ppppmgr)
: : to
: : set(IONET_CMD, io-net -ptcpip -ppppmgr)
: : and reboot.

: I’m not sure how all the things get started automatically, but there
: is a difference with the tiny stack from the big stack in that you
: need to run ifconfig on it.

: I would suggest the following until a better suggestion is provided:

: slay io-net
: io-net -ptcpip -ppppmgr &

in the above step you should run -d as well
(I guess I overlooked that one key part…)

pidin ar prior to slaying off io-net will show you what you are
currently running and the options you have passed the driver.

opps,

Peter

: ifconfig en0 up [and any other options you want]

: You should now be able to run netstat, with the bigstack.

: Peter

: : : Peter Martin <peterm@qnx.com> wrote:
: : : : netstat and route with with the big stack implimentation (npm-tcpip.so)
: : : : They don’t work with the tiny stack (npm-ttcpip.so) which is used
: : : : by default.

: : : : Peter
: : : :
: : : : gmman@qnx.com wrote:
: : : : : How do ‘netstat’ and ‘route’ work in qrtp?

8

Can’t set suid - it says read-only filesystem (on real path).

Sean Boudreau wrote:

Peter Martin <> peterm@qnx.com> > wrote:
: Steve Tomkins <> stomkins@qnx.com> > wrote:
: : > gmman@qnx.com > wrote:
: : : How do I change to big stack implimentation? Thanks in advance.

: : I think (I’m not the expert so I’ll probably get corrected if
: : I’m wrong) you can edit the file /etc/system/enum/include/net
: : and change the line:
: : set(IONET_CMD, io-net -pttcpip -ppppmgr)
: : to
: : set(IONET_CMD, io-net -ptcpip -ppppmgr)
: : and reboot.

: I’m not sure how all the things get started automatically, but there
: is a difference with the tiny stack from the big stack in that you
: need to run ifconfig on it.

: I would suggest the following until a better suggestion is provided:

: slay io-net
: io-net -ptcpip -ppppmgr &
: ifconfig en0 up [and any other options you want]

: You should now be able to run netstat, with the bigstack.

I think there was an omission of the setuid bit on netstat in the
release.

chmod u+s netstat.

or run as root.

-seanb

9

Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:
: Can’t set suid - it says read-only filesystem (on real path).

Hit the space while booting and use the mount rw option, set it, reboot.
Or copy to somewhere else. Or run as root.

-seanb

10

Hi Peter,

I’m getting the same “no namelist” diagnostic from ifconfig. Should I
presume that the change to the large stack is what I need as well to re-set my mtu
so that I can connect to sites such as the Public Repository, slashdot, Google,
MSNBC and others? My ISP has their router set to an mtu of 576 and if I use 1500
there are not very many sites that I can reach. More to the point, I can reach the
sites (host ZZZ contacted …) but the data can’t get back to me (… waiting for
reply [forever!]). I will test this after work today but am looking for some
encouraging input before I start. (;

lsw

Peter Martin wrote:

Peter Martin <> peterm@qnx.com> > wrote:
: Steve Tomkins <> stomkins@qnx.com> > wrote:
: : > gmman@qnx.com > wrote:
: : : How do I change to big stack implimentation? Thanks in advance.

: : I think (I’m not the expert so I’ll probably get corrected if
: : I’m wrong) you can edit the file /etc/system/enum/include/net
: : and change the line:
: : set(IONET_CMD, io-net -pttcpip -ppppmgr)
: : to
: : set(IONET_CMD, io-net -ptcpip -ppppmgr)
: : and reboot.

: I’m not sure how all the things get started automatically, but there
: is a difference with the tiny stack from the big stack in that you
: need to run ifconfig on it.

: I would suggest the following until a better suggestion is provided:

: slay io-net
: io-net -ptcpip -ppppmgr &

in the above step you should run -d as well
(I guess I overlooked that one key part…)

pidin ar prior to slaying off io-net will show you what you are
currently running and the options you have passed the driver.

opps,

Peter

: ifconfig en0 up [and any other options you want]

: You should now be able to run netstat, with the bigstack.

: Peter

: : : Peter Martin <> peterm@qnx.com> > wrote:
: : : : netstat and route with with the big stack implimentation (npm-tcpip.so)
: : : : They don’t work with the tiny stack (npm-ttcpip.so) which is used
: : : : by default.

: : : : Peter
: : : :
: : : : > gmman@qnx.com > wrote:
: : : : : How do ‘netstat’ and ‘route’ work in qrtp?

11

Lynn S. Weeks <lweeks@netscape.net> wrote:
: Hi Peter,

: I’m getting the same “no namelist” diagnostic from ifconfig. Should I
: presume that the change to the large stack is what I need as well to re-set my mtu

The ‘no namelist’ message is from netstat and is either because you
are not running the large stack or not running netstat as root. See
previous postings in this thread for root remedy. Do a ‘pidin me’
and look at the io-net entries, at the end it will show all dll’s
io-net has loaded. This will show which stack you are running
(npm-ttcpip.so vs npm-tcpip.so).


: so that I can connect to sites such as the Public Repository, slashdot, Google,
: MSNBC and others? My ISP has their router set to an mtu of 576 and if I use 1500
: there are not very many sites that I can reach. More to the point, I can reach the
: sites (host ZZZ contacted …) but the data can’t get back to me (… waiting for
: reply [forever!]). I will test this after work today but am looking for some
: encouraging input before I start. (;

If the router (or all routers along the way) were fragmenting correctly
it should work with either stack but that’s another story.

You have 2 options: use the large stack which automatically knocks
down its mtu for external networks or use the small stack and pass
the ‘mtu=576’ option to your driver. eg:

As root:

slay io-net

io-net -d -ptcpip

ifconfig en0 X.X.X.X

route add default Y.Y.Y.Y

or

slay io-net

io-net -d mtu=576 -pttcpip if=en0:X.X.X.X,default=Y.Y.Y.Y

-seanb

12

Steve Tomkins wrote:

gmman@qnx.com > wrote:
: How do I change to big stack implimentation? Thanks in advance.

I think (I’m not the expert so I’ll probably get corrected if
I’m wrong) you can edit the file /etc/system/enum/include/net
and change the line:

set(IONET_CMD, io-net -pttcpip -ppppmgr)

to

set(IONET_CMD, io-net -ptcpip -ppppmgr)

and reboot.

Well, I tried this with /etc/system/enum/include/net and
/pkgs/base/qnx/os/drivers2.1/etc/system/enum/include/net (after mounting
/pkgs rw).

No joy, it still starts the tiny stack.

Whats the “Right Way ™” of starting RTP with the full stack ?

Thanks

-Th

13

Thomas Hentschel <thomas@hentschel.net> wrote:

Steve Tomkins wrote:

gmman@qnx.com > wrote:
: How do I change to big stack implimentation? Thanks in advance.

I think (I’m not the expert so I’ll probably get corrected if
I’m wrong) you can edit the file /etc/system/enum/include/net
and change the line:

set(IONET_CMD, io-net -pttcpip -ppppmgr)

to

set(IONET_CMD, io-net -ptcpip -ppppmgr)

and reboot.

Well, I tried this with /etc/system/enum/include/net and
/pkgs/base/qnx/os/drivers2.1/etc/system/enum/include/net (after mounting
/pkgs rw).

No joy, it still starts the tiny stack.

Whats the “Right Way ™” of starting RTP with the full stack ?

That line, is the only place to set how io-net start.
Are you sure you got it right? What happenes after you boot, do
a “cat /etc/system/enum/include/net”? Is it still showing “-p tcpip” ?
Can you change the line, say put “set(IONET_CMD, io-net -ptcpip)”,
and reboot, see what happened?

The reason this is so messy is because you are editing a file in
file system package, which means, you will get a copy be created
in /var/pkg/spill, and even if you go edit the /pkgs/… one,
the fs-pkg still going to pick up the /var/pkg/spill/ file.
That’s why we encourge people use /etc/rc.d/rc.local instead of
playing with these file.

As for “Right Way”, I really don’t know. It’s a desition of
“enum” guys.

-xtang

14

Xiaodan Tang wrote:

Thomas Hentschel <> thomas@hentschel.net> > wrote:
Steve Tomkins wrote:

gmman@qnx.com > wrote:
: How do I change to big stack implimentation? Thanks in advance.

I think (I’m not the expert so I’ll probably get corrected if
I’m wrong) you can edit the file /etc/system/enum/include/net
and change the line:

set(IONET_CMD, io-net -pttcpip -ppppmgr)

to

set(IONET_CMD, io-net -ptcpip -ppppmgr)

and reboot.

Well, I tried this with /etc/system/enum/include/net and
/pkgs/base/qnx/os/drivers2.1/etc/system/enum/include/net (after mounting
/pkgs rw).

No joy, it still starts the tiny stack.

Whats the “Right Way ™” of starting RTP with the full stack ?

That line, is the only place to set how io-net start.
Are you sure you got it right? What happenes after you boot, do
a “cat /etc/system/enum/include/net”? Is it still showing “-p tcpip” ?
Can you change the line, say put “set(IONET_CMD, io-net -ptcpip)”,
and reboot, see what happened?

$ cat /pkgs/base/qnx/os/drivers2.1/etc/system/enum/include/net

macro definitions for network

all
set(IONET_CMD, io-net -ptcpip -ppppmgr)

$ cat /etc/system/enum/include/net

macro definitions for network

all
set(IONET_CMD, io-net -ptcpip -ppppmgr)

$ ps -a | grep io-net
61454 61454 1 io-net -pttcpip -ppppmgr


The reason this is so messy is because you are editing a file in
file system package, which means, you will get a copy be created
in /var/pkg/spill, and even if you go edit the /pkgs/… one,
the fs-pkg still going to pick up the /var/pkg/spill/ file.
That’s why we encourge people use /etc/rc.d/rc.local instead of
playing with these file.

$ cat /var/pkg/spill/etc/system/enum/include/net

macro definitions for network

all
set(IONET_CMD, io-net -ptcpip -ppppmgr)


Well, IMHO, which stack to use could be an option in the Networg Cfg.
Applet.

If I use /etc/rc.d/rc.local, is it still going to use /etc/net.cfg ?

As for “Right Way”, I really don’t know. It’s a desition of
“enum” guys.

Would be nice for one of the “enum” guys to speak up > :slight_smile:

-Th

15

I vote for a ‘set as default’ tickbox too…