Hello to all gurus out there!
How can I make QNX RtP to load tcpip instead of ttcpip at boot time?
For some reason the ttcpip is loaded but it causes problems with
dhcp.client. IP-address is correct but netmask is wrong (always
255.255.255.0) and default gateway missing.
If I do
slay dhcp.client
slay io-net
nettrap -p tcpip -i -v start
dhcp.client -d -i en0 -m
from shell after bootup has finished everything gets set correctly.
I would like to know what file I should edit to make tcpip the default
protocol stack?
I have tried adding the nettrap and dhcp.client commands to /etc/rc.d/rc
but it would seem that io-net and dhcp.client are loaded before it is run
and all I get is two instances of io-net and dhcp.client with obvious
results (i.e. no effect). Of course, I could add the slay commands to rc
but I would prefer a “cleaner” solution.
The on-line manuals are somewhat sparse in this area. At least I haven’t
been able to find a description of the boot procedure.
Any hints would be appreciated.
Regards,
Martti Laaksonen
Martti Laaksonen <mlaakson@pp.htv.fi> wrote:
: The on-line manuals are somewhat sparse in this area. At least I haven’t
: been able to find a description of the boot procedure.
We’re working on a System Adminstration manual that should help with
questions like yours.
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems Ltd.
Martti Laaksonen <mlaakson@pp.htv.fi> wrote:
Hello to all gurus out there!
How can I make QNX RtP to load tcpip instead of ttcpip at boot time?
For some reason the ttcpip is loaded but it causes problems with
dhcp.client. IP-address is correct but netmask is wrong (always
255.255.255.0) and default gateway missing.
If I do
slay dhcp.client
slay io-net
nettrap -p tcpip -i -v start
dhcp.client -d -i en0 -m
from shell after bootup has finished everything gets set correctly.
I would like to know what file I should edit to make tcpip the default
protocol stack?
I have tried adding the nettrap and dhcp.client commands to /etc/rc.d/rc
but it would seem that io-net and dhcp.client are loaded before it is run
and all I get is two instances of io-net and dhcp.client with obvious
results (i.e. no effect). Of course, I could add the slay commands to rc
but I would prefer a “cleaner” solution.
The on-line manuals are somewhat sparse in this area. At least I haven’t
been able to find a description of the boot procedure.
Any hints would be appreciated.
$ cd /etc/system/enum/include
$ grep IONET_CMD *
net: set(IONET_CMD, io-net -pttcpip -ppppmgr)
-xtang
Regards,
Martti Laaksonen
xtang@ottawa.com (Xiaodan Tang) wrote in <8ra5sn$mar$2@nntp.qnx.com>:
$ cd /etc/system/enum/include
$ grep IONET_CMD *
net: set(IONET_CMD, io-net -pttcpip -ppppmgr)
Thanks for that one.
There still remains one issue with the networking, though.
The full tcp/ip stack is now loaded during boot up and ip parameters get
set accordingly with dhcp.client. The problem manifests itself when I try
to do e.g. ping, nothing happens until the command timeouts.
Doing
netstat -rn
reveals that the interface for the default route is set to lo0 instead of
en0 (yet, gw address is correct)!
OK, then doing
route delete default
route add default
corrects things so that the default route interface is set to en0 and we’re
out there (or here).
Syslog has the following to say about the situation:
Oct 4 18:38:51 localhost syslogd: restart
Oct 04 18:39:00 nto dhclient: Error creating default route: File exists
Anyone willing to touch this one?
Thanks in advance,
Martti Laaksonen
Martti Laaksonen <mlaakson@pp.htv.fi> wrote:
: xtang@ottawa.com (Xiaodan Tang) wrote in <8ra5sn$mar$2@nntp.qnx.com>:
:>
:>$ cd /etc/system/enum/include
:>$ grep IONET_CMD *
:>net: set(IONET_CMD, io-net -pttcpip -ppppmgr)
:>
: Thanks for that one.
: There still remains one issue with the networking, though.
: The full tcp/ip stack is now loaded during boot up and ip parameters get
: set accordingly with dhcp.client. The problem manifests itself when I try
: to do e.g. ping, nothing happens until the command timeouts.
: Doing
: netstat -rn
: reveals that the interface for the default route is set to lo0 instead of
: en0 (yet, gw address is correct)!
How many cards do you have in this machine?
Can you post the output from ‘netstat -in’ and ‘netstat -rn’ in this state.
-seanb