Cannot ping the gateway in QNX4.25 box
Andrey Kaganovsky
I am trying to setup TCP/IP on a QNX4.25 box connected to @Home network.
I previously had QNX4.24 installed on this box, and I expected that
exactly the same TCP/IP configuration is needed for 4.25. Well, this
seems not to be the case ...
The box's IP/netmask/hostname are 24.112.223.59, 255.255.252.0,
cr143860-b respectively as supplied by @Home. Here are my /etc/hosts and
/etc/resolv.conf:
/etc/hosts
*********
127.0.0.1 localhost localhost.my.domain
24.112.223.59 cr143860-b.ym1.on.wave.home.com cr143860-b
/etc/resolv.conf
****************
domain ym1.on.wave.home.com
nameserver 24.112.32.13
nameserver 24.112.2.14
Here is what I am doing:
slay -f Socket Socklet
Net &
Net.tulip -c21041 -I0 -l1 &
netmap -f
Socket cr143860-b &
ifconfig en1 24.112.223.59 netmask 255.255.252.0
route -v add -net 0.0.0.0 24.112.220.1
At that point I could ping, for instance, 24.112.221.116, but cannot
ping the @Home gateway 24.112.220.1.
Here are my routing tables:
netstat -nr
default 24.112.220.1 UG 0 4 en1
24.112.220 24.112.223.59 U 1 18 en1
127.0.0.1 127.0.0.1 UH 1 0 lo0
I would appreciate any help.
regards, Andray
Andrey Kaganovsky
1. The QNX 4.25 TCP/IP component's license seems to be bound to the
MAC address of the NIC which was present in the system at the time
the OS is being installed. When I replaced this NIC with absolutely
identical one, the TCP/IP turned out to be broken.
Is there a way to update the license to bind it to new NIC ?
2. The problem with @Home network (I cannot ping @Home gateway) seems
to go away after I boot another OS (VxWorks) from the floppy on
this very box. After I have done it, I have no problem with
accessing Internet from this box running QNX 4.25 with the
configuration below. At some point @Home service was disrupted, and
I lost ability to access gateway from QNX 4.25 again. After @Home
service was restored, I just boot VxWorks from the floppy again, and
then reboot with QNX 4.25.
The problem with accessing @Home seems to be specific to QNX (both
4.24 and 4.25). All the other OSses that I am running on this box
(FreeBSD, NT 4, SCO OpenServer 5, Solaris 7, VxWorks and pSOS) don't
have any problems when connecting to @Home. All my @Home addresses
are static, so networking setup is usully very simple. Well, not
in QNX case... Maybe somebody could give me a clue of how to get
QNX straight, I am not an expert in TCP/IP ...
regards, Andray
Alex Cellarius
Andrey Kaganovsky <and...@home.com> wrote:
> In case if somebody interested, here is what I have discovered.
>
> 1. The QNX 4.25 TCP/IP component's license seems to be bound to the
> MAC address of the NIC which was present in the system at the
time
> the OS is being installed. When I replaced this NIC with
absolutely
> identical one, the TCP/IP turned out to be broken.
>
> Is there a way to update the license to bind it to new NIC ?
Look at the /etc/config/netmap file.
There is probably a MAC address in there.
I think if you don't use QNX networking, you should be safe
deleting this file (or try renaming it to something else, to be
safe ;) )
Looking at your setup, I would suggest replacing the route
statement you have ( route -v add -net 0.0.0.0 24.112.220.1)
with
route add default 24.112.220.1
This is how I add a gateway.
If the above doesn't help, just to make sure it's not a
hardware issue, try booting the QNX demodisk and see if
that works.
--
Systems 104 (South Africa) http://www.systems104.co.za
Sent via Deja.com http://www.deja.com/
Before you buy.
Martin Zimmerman
> 1. The QNX 4.25 TCP/IP component's license seems to be bound to the
> MAC address of the NIC which was present in the system at the time
> the OS is being installed. When I replaced this NIC with absolutely
> identical one, the TCP/IP turned out to be broken.
>
> Is there a way to update the license to bind it to new NIC ?
This is INCORRECT. There is no linkage between the NIC MAC address and QNX
TCP/IP licensing.
The @Home network *does* create such a relationship via dhcp. A DHCP request
is sent and your IP is then associated with the MAC address of the NIC making
the request. You *must* run a proper DCHP client (in QNX this is dhcp.client),
to have this work properly.
You can trick the @home network, the relationship between MAC address and assigned
IP persists for a period of time and is then refreshed/renewed. You can boot one
OS that supports dhcp, obtain an IP and then reboot into another OS and simply use
that IP without DHCP. This will break as soon as the dhcp lease expired at the
@home end of things.
My reccomendation (I run @home on QNX with no issues):
1. remove the static IPs for @home from your /etc/hosts file.
2. remove the DNS server IPs from your /etc/resolv.conf file.
3. change your /etc/netstart to something similiar to this:
Socklet cr-whatever-weirdname &
dhcp.client -i en1 &
if_up en1
echo "en1 = \c" ; ifconfig en1 | awk '$1==inet" {print $2}'
inetd
Cheers,
Camz.
--
Martin Zimmerman ca...@passageway.com
Camz Software Enterprises www.passageway.com/camz/qnx/
QNX Programming & Consulting