networking

I have the following problem:

route and ifconfig are (in most cases) returning the error:

route: socket: no such file or directory
ifconfig: socket: no such file or directory

also,

I set up the network trough etc/net.cfg, but initially, my LAN card is
not being setup (I need to run io-net manually to put up the device).

although I’m sure that the routing is well described in net.cfg I can’t
access the machines that on other OSes are accessible with the same
routing…

has anybody had this situation?



Sent via Deja.com http://www.deja.com/
Before you buy.

Alexander Popov <long@web.bg> wrote:

I have the following problem:

route and ifconfig are (in most cases) returning the error:

route: socket: no such file or directory
ifconfig: socket: no such file or directory

Is there a /dev/socket when you get these errors?

I set up the network trough etc/net.cfg, but initially, my LAN card is
not being setup (I need to run io-net manually to put up the device).

Errrr…I wouldn’t mess with net.cfg by hand but would instead use
the GUI that maintains that file, phlip. After you run io-net by
hand (assuming your are using -pttcpip) you can just run netmanager
after the io-net process is run.

chris

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

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

In article <8s100d$86b$1@nntp.qnx.com>,
Chris McKillop <cdm@qnx.com> wrote:

Alexander Popov <> long@web.bg> > wrote:
I have the following problem:

route and ifconfig are (in most cases) returning the error:

route: socket: no such file or directory
ifconfig: socket: no such file or directory


Is there a /dev/socket when you get these errors?

yes there is but inside it there are only 3 files :

2 - lenght 0
autoconnect - lenght 0
pppmgr - lenght 0

I set up the network trough etc/net.cfg, but initially, my LAN card
is
not being setup (I need to run io-net manually to put up the
device).


Errrr…I wouldn’t mess with net.cfg by hand but would instead use
the GUI that maintains that file, phlip. After you run io-net by
hand (assuming your are using -pttcpip) you can just run netmanager
after the io-net process is run.

then how can I make the QNX see my LAN card - are there any init scripts
that do this at boot time? (The LAN is supported - it’s 3COM509B) but
initially phlip is not seting the interface…

chris





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

<<

Sent via Deja.com http://www.deja.com/
Before you buy.

Alexander Popov <long@web.bg> wrote:

In article <8s100d$86b$> 1@nntp.qnx.com> >,
Chris McKillop <> cdm@qnx.com> > wrote:
Alexander Popov <> long@web.bg> > wrote:
I have the following problem:

route and ifconfig are (in most cases) returning the error:

route: socket: no such file or directory
ifconfig: socket: no such file or directory


Is there a /dev/socket when you get these errors?

yes there is but inside it there are only 3 files :

2 - lenght 0
autoconnect - lenght 0
pppmgr - lenght 0

This is because by default RTP started “ttcpip” stands for
“tiny stack”, which do not support ifconfig/route.
Interface Address/Routing table can only be set on the
command line (of io-net) or by netmanager.

I set up the network trough etc/net.cfg, but initially, my LAN card
is
not being setup (I need to run io-net manually to put up the
device).


Errrr…I wouldn’t mess with net.cfg by hand but would instead use
the GUI that maintains that file, phlip. After you run io-net by
hand (assuming your are using -pttcpip) you can just run netmanager
after the io-net process is run.

then how can I make the QNX see my LAN card - are there any init scripts
that do this at boot time? (The LAN is supported - it’s 3COM509B) but
initially phlip is not seting the interface…

You put this 3 line in /etc/rc.d/rc.local

slay io-net
io-net -d -p ttcpip -p pppmgr
netmanager

If you create the rc.local, don’t forget “chmod a+x” on it.

-xtang

What is the prefered method of changing to from the tiny stack to the full
stack? Other threads recommend that you change /etc/system/enum/include/net
from pttcpip to ptcpip. This one and a couple others recommend that you add
rc.local. I changed net and this works for me but I get a problem:

Netmanager Error: Could not get configuration (en0). could not assign
requested address file. ./swapfile added as swap device
…/swapfile successfully added as swap device

That is the last message before going into photon. From the context of the
messages it looks like there might be a missing “\n” in one of the messages.

But also, there doesn’t seem to be a problem with networking once I get
started. I can ftp in from other hosts, and I can ping and telnet, etc. I
can netstat.

Also, everyone seems to be suggesting to modify a file called
/etc/rc.d/rc.local. What about the file rc.sysinit there? Was that not
meant to be the replacement for sysinit?

Scott

Xiaodan Tang wrote:

Alexander Popov <> long@web.bg> > wrote:
In article <8s100d$86b$> 1@nntp.qnx.com> >,
Chris McKillop <> cdm@qnx.com> > wrote:
Alexander Popov <> long@web.bg> > wrote:
I have the following problem:

route and ifconfig are (in most cases) returning the error:

route: socket: no such file or directory
ifconfig: socket: no such file or directory


Is there a /dev/socket when you get these errors?

yes there is but inside it there are only 3 files :

2 - lenght 0
autoconnect - lenght 0
pppmgr - lenght 0

This is because by default RTP started “ttcpip” stands for
“tiny stack”, which do not support ifconfig/route.
Interface Address/Routing table can only be set on the
command line (of io-net) or by netmanager.



I set up the network trough etc/net.cfg, but initially, my LAN card
is
not being setup (I need to run io-net manually to put up the
device).


Errrr…I wouldn’t mess with net.cfg by hand but would instead use
the GUI that maintains that file, phlip. After you run io-net by
hand (assuming your are using -pttcpip) you can just run netmanager
after the io-net process is run.

then how can I make the QNX see my LAN card - are there any init scripts
that do this at boot time? (The LAN is supported - it’s 3COM509B) but
initially phlip is not seting the interface…

You put this 3 line in /etc/rc.d/rc.local

slay io-net
io-net -d -p ttcpip -p pppmgr
netmanager

If you create the rc.local, don’t forget “chmod a+x” on it.

-xtang

J. Scott Franko <jsfranko@switch.com> wrote:

What is the prefered method of changing to from the tiny stack to the full
stack? Other threads recommend that you change /etc/system/enum/include/net
from pttcpip to ptcpip. This one and a couple others recommend that you add
rc.local. I changed net and this works for me but I get a problem:

Netmanager Error: Could not get configuration (en0). could not assign
requested address file. ./swapfile added as swap device
./swapfile successfully added as swap device

If you change it in the enum directory, netmanager will fail since it is
ment to be run with the small stack.

Also, everyone seems to be suggesting to modify a file called
/etc/rc.d/rc.local. What about the file rc.sysinit there? Was that not
meant to be the replacement for sysinit?

The idea is that rc.local is a local script you maintain, the rest of
them will be changed/upgrade between patches/releases and will always
run your rc.local. If you leave them alone you will never miss anything
when you upgrade.

chris

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

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

Chris McKillop wrote:

J. Scott Franko <> jsfranko@switch.com> > wrote:
What is the prefered method of changing to from the tiny stack to the full
stack? Other threads recommend that you change /etc/system/enum/include/net
from pttcpip to ptcpip. This one and a couple others recommend that you add
rc.local. I changed net and this works for me but I get a problem:

Netmanager Error: Could not get configuration (en0). could not assign
requested address file. ./swapfile added as swap device
./swapfile successfully added as swap device


If you change it in the enum directory, netmanager will fail since it is
ment to be run with the small stack.

So the recommended way is to slay and rerun? Will that change in the final
release? Is it me, or does it seem much harder to administer QRTP than QNX4?
Seems much different that handling our own startup script (sysinit) in QNX4.
Seems like more things are harder to reach. In QNX4, I started the network if I
wanted it, but now NTO starts the network for me, and if I don’t like what its
running, I have to kill it before I can start my own configuration. Maybe it’s
just me.

Also, everyone seems to be suggesting to modify a file called
/etc/rc.d/rc.local. What about the file rc.sysinit there? Was that not
meant to be the replacement for sysinit?


The idea is that rc.local is a local script you maintain, the rest of
them will be changed/upgrade between patches/releases and will always
run your rc.local. If you leave them alone you will never miss anything
when you upgrade.

Ok, thats fair. I’m having another problem though. I added /usr/sbin/inetd to
rc.local, and it didn’t seem to start up. But it works if I do it by hand from
root login. I’m going to go back and add the slay ionet and restart before inetd
in rc.local and remove the change to Net and see if it works.

chris

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

J. Scott Franko <jsfranko@switch.com> wrote:

If you change it in the enum directory, netmanager will fail since it is
ment to be run with the small stack.


So the recommended way is to slay and rerun? Will that change in the final
release? Is it me, or does it seem much harder to administer QRTP than QNX4?
Seems much different that handling our own startup script (sysinit) in QNX4.
Seems like more things are harder to reach. In QNX4, I started the network if I
wanted it, but now NTO starts the network for me, and if I don’t like what its
running, I have to kill it before I can start my own configuration. Maybe it’s
just me.

Well, actually, you can just turn it off totally by removing the net
include file in /etc/system/enum and just run it once in /etc/rc.d/rc.local.
I would actually like to see it work such that io-net and the drivers are
started but protocols get mounted after the enumerators are finished.

mount -Tio-net /x86/lib/dll/npm-tcpip.so

in rc.local.

chris

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

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

Chris McKillop wrote:

J. Scott Franko <> jsfranko@switch.com> > wrote:

If you change it in the enum directory, netmanager will fail since it is
ment to be run with the small stack.


So the recommended way is to slay and rerun? Will that change in the final
release? Is it me, or does it seem much harder to administer QRTP than QNX4?
Seems much different that handling our own startup script (sysinit) in QNX4.
Seems like more things are harder to reach. In QNX4, I started the network if I
wanted it, but now NTO starts the network for me, and if I don’t like what its
running, I have to kill it before I can start my own configuration. Maybe it’s
just me.


Well, actually, you can just turn it off totally by removing the net
include file in /etc/system/enum and just run it once in /etc/rc.d/rc.local.

Would the net file possible get put back during an upgrade install?

I would actually like to see it work such that io-net and the drivers are
started but protocols get mounted after the enumerators are finished.

mount -Tio-net /x86/lib/dll/npm-tcpip.so

Is this done in other OS’s? Are there other admin books I can read from other OS’s
to get a handle on how QRTP is admin’d? Is any of this stuff in the helpviewer docs
in a tutorial or whitepaper style fashion? Just having a description of all the tools
is too overwhelming to allow one to come up to speed quickly and do useful
configuration of the system. It’s like throwing wood, hammer and nails in front of me
and telling me that I can pound nails in the wood with the hammer, and then expecting
me to frame a house.

I’ve been reading the docs, both on programming issues and admin issues, and it is
good stuff. But sometimes it stops short of what I want to know.

I suppose a lot of this is just me griping about my initial frustration at learning
something new. I’ll give it some time. And I realize that you guys are still working
on solidifying some of this stuff. But I want to know it all now! ;O)

Keep up the good work!

Scott

in rc.local.



chris

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

<!doctype html public “-//w3c//dtd html 4.0 transitional//en”>

"J. Scott Franko" wrote:.
>

So the recommended way is to slay and rerun?  Will that change in the final
release?  Is it me, or does it seem much harder to administer QRTP than QNX4?
Seems much different that handling our own startup script (sysinit) in QNX4.
Seems like more things are harder to reach.  In QNX4, I started the network if I
wanted it, but now NTO starts the network for me, and if I don't like what its
running, I have to kill it before I can start my own configuration.  Maybe it's
just me.

No, I'm also confused about the startup/admin configuration of QNXRTP.
Maybe I have not yet understood it.

For example:
  My video card is not detected during startup, since crttrap hangs on devcyrix.so.
Nevermid, QSSL helped me to make a trap file by hand so my video card
will be recognized, works well. But when I boot the trap file is overwritten
and is just hangs again.  I can't figure out how to hardcode the admin files for my video setup.

 

>
> >
> > Also, everyone seems to be suggesting to modify a file called
> > /etc/rc.d/rc.local.   What about the file rc.sysinit there?  Was that not
> > meant to be the replacement for sysinit?
> >
>
> The idea is that rc.local is a local script you maintain, the rest of
> them will be changed/upgrade between patches/releases and will always
> run your rc.local.  If you leave them alone you will never miss anything
> when you upgrade.
>

Ok, thats fair.  I'm having another problem though.  I added /usr/sbin/inetd to
rc.local, and it didn't seem to start up.  But it works if I do it by hand from
root login.  I'm going to go back and add the slay ionet and restart before inetd
in rc.local and remove the change to Net and see if it works.

Same here, I can't get my rc.local to get run.

regards
 

--
Per Åkesson
Carmenta AB
SWEDEN
 

In article <8s1tgg$p4k$1@nntp.qnx.com>,
Xiaodan Tang <xtang@ottawa.com> wrote:

Alexander Popov <> long@web.bg> > wrote:
In article <8s100d$86b$> 1@nntp.qnx.com> >,
Chris McKillop <> cdm@qnx.com> > wrote:
Alexander Popov <> long@web.bg> > wrote:
I have the following problem:

route and ifconfig are (in most cases) returning the error:


You put this 3 line in /etc/rc.d/rc.local

slay io-net
io-net -d -p ttcpip -p pppmgr
netmanager

If you create the rc.local, don’t forget “chmod a+x” on it.

-xtang

thanks, but it didn’t seem to work…

I think the /etc/rc.d/rc.local is not being execute…
When I put these three lines in rc.local nothing happens,
but this works when I put them in (lets say) /root/.profile…

also, I desperately need to enable the multicasting of the LAN,
haw can this be done with the tiny stack


Sent via Deja.com http://www.deja.com/
Before you buy.

One more thing :

inetd.conf is set to start telnet, and the telnetd is loaded but I cant
access the target trough telnet… it says: Unable to connect to remote
host: Connection refused… tha same error is displayed when I try
locally to connect to 127.0.0.1


Sent via Deja.com http://www.deja.com/
Before you buy.

I have the same problem. But if, after bootup, you log in to root and type
/usr/sbin/inetd, inetd will start up, and you can then access with telnet
and phindows, and ftp. But, my rc.local file has this same thing, and it
doesn’t seem to run, and no error messages. I don’t know how to see the
console anymore since ditto doesn’t seem to be a part of the platform.
Also, ps doesn’t seem to be standard. No ps -ef or ps -aux. ps -A doesn’t
show the inetd after I run it by hand, but it does work after that.

Scott

Alexander Popov wrote:

One more thing :

inetd.conf is set to start telnet, and the telnetd is loaded but I cant
access the target trough telnet… it says: Unable to connect to remote
host: Connection refused… tha same error is displayed when I try
locally to connect to 127.0.0.1

Sent via Deja.com > http://www.deja.com/
Before you buy.

I take back the part about rc.local not working. I reread a few threads on
this subject and found the part I had missed about giving execute priviledge to
rc.local:

as root:

chmod a+x rc.local

I got an extra message at startup about extra commands or something, I guess
this was the indication that rc.local was running.

I still don’t know how to access the console, or why ps doesn’t operate like in
system V or bsd.

“J. Scott Franko” wrote:

I have the same problem. But if, after bootup, you log in to root and type
/usr/sbin/inetd, inetd will start up, and you can then access with telnet
and phindows, and ftp. But, my rc.local file has this same thing, and it
doesn’t seem to run, and no error messages. I don’t know how to see the
console anymore since ditto doesn’t seem to be a part of the platform.
Also, ps doesn’t seem to be standard. No ps -ef or ps -aux. ps -A doesn’t
show the inetd after I run it by hand, but it does work after that.

Scott

Alexander Popov wrote:

One more thing :

inetd.conf is set to start telnet, and the telnetd is loaded but I cant
access the target trough telnet… it says: Unable to connect to remote
host: Connection refused… tha same error is displayed when I try
locally to connect to 127.0.0.1

Sent via Deja.com > http://www.deja.com/
Before you buy.

In article <39E5BBA2.E41FF2EC@switch.com>,
“J. Scott Franko” <jsfranko@switch.com> wrote:

I take back the part about rc.local not working. I reread a few
threads on
this subject and found the part I had missed about giving execute
priviledge to
rc.local:

as root:

chmod a+x rc.local

I got an extra message at startup about extra commands or something,
I guess
this was the indication that rc.local was running.

I still don’t know how to access the console, or why ps doesn’t
operate like in
system V or bsd.

“J. Scott Franko” wrote:

I have the same problem. But if, after bootup, you log in to root
and type
/usr/sbin/inetd, inetd will start up, and you can then access with
telnet
and phindows, and ftp. But, my rc.local file has this same thing,
and it
doesn’t seem to run, and no error messages. I don’t know how to
see the
console anymore since ditto doesn’t seem to be a part of the
platform.
Also, ps doesn’t seem to be standard. No ps -ef or ps -aux. ps -A
doesn’t
show the inetd after I run it by hand, but it does work after that.

Scott

Alexander Popov wrote:

One more thing :

inetd.conf is set to start telnet, and the telnetd is loaded but
I cant
access the target trough telnet… it says: Unable to connect to
remote
host: Connection refused… tha same error is displayed when I
try
locally to connect to 127.0.0.1

Sent via Deja.com > http://www.deja.com/
Before you buy.

Well you’re right :slight_smile:)

now everithing goes fine except /:))/:

when I set up the interface I use 192.168.204.51 and netmanager
automatically sets the netmask to 255.255.255.0 and I need it to be
255.255.0.0… can I get trough it or this is a feature of
netmanager…


Sent via Deja.com http://www.deja.com/
Before you buy.

“J. Scott Franko” wrote:

I take back the part about rc.local not working. I reread a few threads on
this subject and found the part I had missed about giving execute priviledge to
rc.local:

as root:

chmod a+x rc.local

Well, it seems I did a

chmod ug+x rc.local

so perhaps that’s why it didn’t execute.

After setting execute bit for other group it works.

regards


Per Åkesson
Carmenta AB
SWEDEN

Alexander Popov wrote:

In article <> 39E5BBA2.E41FF2EC@switch.com> >,
“J. Scott Franko” <> jsfranko@switch.com> > wrote:
I take back the part about rc.local not working. I reread a few
threads on
this subject and found the part I had missed about giving execute
priviledge to
rc.local:

as root:

chmod a+x rc.local

I got an extra message at startup about extra commands or something,
I guess
this was the indication that rc.local was running.

[snip]

Well you’re right > :slight_smile:> )

now everithing goes fine except /:))/:

when I set up the interface I use 192.168.204.51 and netmanager
automatically sets the netmask to 255.255.255.0 and I need it to be
255.255.0.0… can I get trough it or this is a feature of
netmanager…

You can log into root in Photon and run Network cfg from the shelf (phlip),
and it will let you change the netmask in the first tab.

Or you could add the following to your rc.local, after you startup the
ionet

ifconfig en0 netmask 255.255.0.0 up

for ex:

ifconfig en0 192.3.23.2 netmask 255.255.0.0 up

I did this by hand and it changed the netmask for me. It doesn’t work if
you leave out .

Scott

Sent via Deja.com > http://www.deja.com/
Before you buy.

Alexander Popov <long@web.bg> wrote:

also, I desperately need to enable the multicasting of the LAN,
haw can this be done with the tiny stack

No, you must use the big stack. Also, not all the drivers current
support multicast. So if you use the big stack and pass in your driver
options…(for example, with a 3COM card)

io-net -d el900 mutlicast=1 -ptcpip
ifconfig …
route …

chris

\

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

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

Chris McKillop wrote:

J. Scott Franko <> jsfranko@switch.com> > wrote:

If you change it in the enum directory, netmanager will fail since it is
ment to be run with the small stack.


So the recommended way is to slay and rerun? Will that change in the final
release? Is it me, or does it seem much harder to administer QRTP than QNX4?
Seems much different that handling our own startup script (sysinit) in QNX4.
Seems like more things are harder to reach. In QNX4, I started the network if I
wanted it, but now NTO starts the network for me, and if I don’t like what its
running, I have to kill it before I can start my own configuration. Maybe it’s
just me.


Well, actually, you can just turn it off totally by removing the net
include file in /etc/system/enum and just run it once in /etc/rc.d/rc.local.
I would actually like to see it work such that io-net and the drivers are
started but protocols get mounted after the enumerators are finished.

The above doesn’t work. ./swapfile doesn’t get created. Is that a problem?

If its ok, then the only problem is the need to sleep after calling io-net, as
described below:

I tired it with net there, and rc.config to slay io-net, and start it again, and
ifconfig and found that my configuration set in phlip had half disappeared. The
device tab lost its info, but the network tab still contained its settings. I used
ifconfig by hand once, and I set it in phlip once, but both times it dissappeard on
reboot.

So I put an ifconfig and a route add default in my rc.local, and it worked once. Then
I moved the net file to orig_net and rebooted, and it failed the ifconfig and route
saying socket: file or directory not found, and I didn’t see the messages about adding
…/swapfile.

Then I put net back and got the ./swapfile messages back, but ifconfig and route were
again complaining about no such directory or file, refering to socket, which I assume
was /dev/socket diretory created by io-net. I put a 2 second sleep after running
io-net and that didnt’ work. Finally a 5 second sleep worked.

Here’s my rc.local file now (with ip’s changed to protect the innocent):

slay -f io-net
io-net -del900 -p tcpip -p pppmgr
sleep 5
ifconfig en0 <my_ip> netmask 255.255.255.0 up
route add default <my_gateway>
/usr/sbin/inetd

This works. Some previous examples had said to use -p ttcpip but i think that was a
typoe as that is the “tiny” stack. The helpviewer page on io-net doesn’t list tcpip
(only ttcpip and 2 others) as an option in is -p section, but this works.

Hope this helps some people get the giant stack started!

Scott

mount -Tio-net /x86/lib/dll/npm-tcpip.so

in rc.local.

chris

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