|
|
Networking issues with QNX 4
|
|
05/13/2010 2:05 PM
post54592
|
Networking issues with QNX 4
Good afternoon all,
I have recently installed the latest QNX iso from the website and am currently trying configure the networking. I
have successfully been able to ping internally to the box, but when I try it to an outside device, say, a external
harddrive w/ ethernet ports, I get nothing. I figure it could be an issue where I might have to configure my network
card? but I am not too sure. I would really appreciate any help towards this.
Thank you,
~Julian
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 2:14 PM
post54593
|
Re: Networking issues with QNX 4
If you can post the output from 'show_pci -v' we should be able to tell you
how to start your network adapter.
On 10-05-13 2:05 PM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Good afternoon all,
> I have recently installed the latest QNX iso from the website and am
> currently trying configure the networking. I have successfully been able to
> ping internally to the box, but when I try it to an outside device, say, a
> external harddrive w/ ethernet ports, I get nothing. I figure it could be an
> issue where I might have to configure my network card? but I am not too sure.
> I would really appreciate any help towards this.
>
> Thank you,
>
> ~Julian
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54592
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 2:34 PM
post54596
|
Re: Networking issues with QNX 4
Thank you Mr Brown for your help.
I tried to copy the contents of the file but when I did "nettrap -vvvvvv start net.file 2>&1" following the show_pci -
v command.. I get a "tr164a: TR hardware init function failure code=0008" error. My cpu then freezes and I have to
reboot. Any suggestions?
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 2:37 PM
post54597
|
Re: Networking issues with QNX 4
OK, just run 'show_pci' and send me the Vendor and Device IDs that show up
for Network.
On 10-05-13 2:34 PM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Thank you Mr Brown for your help.
> I tried to copy the contents of the file but when I did "nettrap -vvvvvv
> start net.file 2>&1" following the show_pci -v command.. I get a "tr164a: TR
> hardware init function failure code=0008" error. My cpu then freezes and I
> have to reboot. Any suggestions?
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54596
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:02 PM
post54604
|
Re: Networking issues with QNX 4
Ok, thanks once again.
So under show_pci -v
I get PCI version 3.00
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 2e30h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 2e31h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27d8h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27d0h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27d2h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27c8h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27c9h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27cah
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27cbh
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27cch
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 244eh
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27b8h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27dfh
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27c0h
Vendor ID = 8086h, INTEL CORPORATION
Device ID = 27dah
Vendor ID = 10deh
Device ID = 641h
Vendor ID = 10ech
Device ID = 8168h
Vendor ID = 10ech
Device ID = 8169h
IRQ routing = bus = 0 motherboard device =1
Vendor = 8086h, INTEL corporation
Device ID = 2e31h
IRQ routing = bus = 0 motherboard device =30
Vendor = 8086h,
Device ID = 244eh
IRQ routing = bus = 0 motherboard device =31
Vendor = 8086h, INTEL corporation
Device ID = 27b8h
Vendor = 8086h, INTEL corporation
Device ID = 27dfh
Vendor = 8086h, INTEL corporation
Device ID = 27c0h
Vendor = 8086h, INTEL corporation
Device ID = 27dah
IRQ routing = bus = 0 motherboard device =29
Vendor = 8086h, INTEL corporation
Device ID = 27c8h
Vendor = 8086h, INTEL corporation
Device ID = 27c9h
Vendor = 8086h, INTEL corporation
Device ID = 27cah
Vendor = 8086h, INTEL corporation
Device ID = 27cbh
Vendor = 8086h, INTEL corporation
Device ID = 27cch
IRQ routing = bus = 0 motherboard device =27
Vendor = 8086h, INTEL corporation
Device ID = 27d8h
IRQ routing = bus = 0 motherboard device =28
Vendor = 8086h, INTEL corporation
Device ID = 27d0h
Vendor = 8086h, INTEL corporation
Device ID = 27d2h
IRQ routing = bus = 0 slot = 32 device = 0
No card configured in slot
IRQ routing = bus = 4 slot = 1 device = 2
Vendor = 10ech
Device ID = 8169h
IRQ routing = bus = 4 slot = 2 device = 1
No card configured in slot
IRQ routing = bus = 3 motherboard device = 0
Vendor = 10ech
did 8168h
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:10 PM
post54606
|
Re: Networking issues with QNX 4
You have the Realtek 8169 Ethernet controllers, so you will have to run the
Net.rtl8169 driver. You have 2 devices, so you will have to start the driver
as follows:
Net.rtl8169 -V10ec -d8168 &
Net.rtl8169 -V10ec -d8169 -l2 &
Please note the capital 'V' and lower case 'd'.
On 10-05-13 3:02 PM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Ok, thanks once again.
>
> So under show_pci -v
>
> I get PCI version 3.00
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 2e30h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 2e31h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27d8h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27d0h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27d2h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27c8h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27c9h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27cah
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27cbh
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27cch
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 244eh
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27b8h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27dfh
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27c0h
>
> Vendor ID = 8086h, INTEL CORPORATION
> Device ID = 27dah
>
> Vendor ID = 10deh
> Device ID = 641h
>
> Vendor ID = 10ech
> Device ID = 8168h
>
> Vendor ID = 10ech
> Device ID = 8169h
>
> IRQ routing = bus = 0 motherboard device =1
> Vendor = 8086h, INTEL corporation
> Device ID = 2e31h
>
> IRQ routing = bus = 0 motherboard device =30
> Vendor = 8086h,
> Device ID = 244eh
>
> IRQ routing = bus = 0 motherboard device =31
> Vendor = 8086h, INTEL corporation
> Device ID = 27b8h
> Vendor = 8086h, INTEL corporation
> Device ID = 27dfh
> Vendor = 8086h, INTEL corporation
> Device ID = 27c0h
> Vendor = 8086h, INTEL corporation
> Device ID = 27dah
>
> IRQ routing = bus = 0 motherboard device =29
> Vendor = 8086h, INTEL corporation
> Device ID = 27c8h
> Vendor = 8086h, INTEL corporation
> Device ID = 27c9h
> Vendor = 8086h, INTEL corporation
> Device ID = 27cah
> Vendor = 8086h, INTEL corporation
> Device ID = 27cbh
> Vendor = 8086h, INTEL corporation
> Device ID = 27cch
>
> IRQ routing = bus = 0 motherboard device =27
> Vendor = 8086h, INTEL corporation
> Device ID = 27d8h
>
> IRQ routing = bus = 0 motherboard device =28
> Vendor = 8086h, INTEL corporation
> Device ID = 27d0h
> Vendor = 8086h, INTEL corporation
> Device ID = 27d2h
>
> IRQ routing = bus = 0 slot = 32 device = 0
> No card configured in slot
>
> IRQ routing = bus = 4 slot = 1 device = 2
> Vendor = 10ech
> Device ID = 8169h
>
> IRQ routing = bus = 4 slot = 2 device = 1
> No card configured in slot
>
> IRQ routing = bus = 3 motherboard device = 0
> Vendor = 10ech
> did 8168h
>
>
>
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54604
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:20 PM
post54609
|
Re: Networking issues with QNX 4
So I tried to run Net.rtl8169 -V10ec -d8168 & and I got:
"Net.rtl18169 INITIALIZATION ERROR 4"
However, when I did Net.rtl8169 -V10ec -d8169 -l2 & , I got
%1 - 20904 Done (1) Net.rt18169 -V10ec -d8168
%2 + 21286 Running Net.rt18169 -V10ec -d8169 -12
When I tried to ping my outside external, I still get a hang.
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:23 PM
post54610
|
Re: Networking issues with QNX 4
You have to start Net first, then the network drivers and then TCP/IP.
Net &
Net.rtl8169 -V10ec -d8168 &
Net.rtl8169 -V10ec -d8169 -l2 &
Socket nodename &
Once you have done this, you can run ifconfig or dhcp.client.
On 10-05-13 3:20 PM, "Julian Babel" <community-noreply@qnx.com> wrote:
> So I tried to run Net.rtl8169 -V10ec -d8168 & and I got:
>
> "Net.rtl18169 INITIALIZATION ERROR 4"
>
> However, when I did Net.rtl8169 -V10ec -d8169 -l2 & , I got
>
> %1 - 20904 Done (1) Net.rt18169 -V10ec -d8168
> %2 + 21286 Running Net.rt18169 -V10ec -d8169 -12
>
> When I tried to ping my outside external, I still get a hang.
>
>
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54609
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:31 PM
post54613
|
Re: Networking issues with QNX 4
Do I need to start up nettrap query first as well? as
nettrap query
Net &
etc etc?
Because using Net & to start up the network gives me this message
27598 Done (255) Net NG NET: Parse_Args() failed.
I'll continue to see what I come up with though.
Thanks to your help, I know I am getting close so thank you very much as well.
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:33 PM
post54614
|
Re: Networking issues with QNX 4
No, don't run nettrap at all. If you run 'sin' and Net is already running,
then don't start it again. The same applies to the drivers.
On 10-05-13 3:31 PM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Do I need to start up nettrap query first as well? as
>
> nettrap query
> Net &
> etc etc?
>
> Because using Net & to start up the network gives me this message
>
> 27598 Done (255) Net NG NET: Parse_Args() failed.
>
> I'll continue to see what I come up with though.
>
> Thanks to your help, I know I am getting close so thank you very much as well.
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54613
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:45 PM
post54617
|
Re: Networking issues with QNX 4
Mr Brown,
Thanks for your help. I will work on this a little more but if you are around tomorrow, I will let you know how
things turn out in the morning.
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:50 PM
post54618
|
Re: Networking issues with QNX 4
Sorry Mr. Brown,
Silly question but I will ask anyway... I set my socket to be 30... so when I set up tcp/ip do I need to say socket30
&?
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 3:53 PM
post54619
|
Re: Networking issues with QNX 4
I'm not sure what you mean by "I set my socket to be 30."
On 10-05-13 3:50 PM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Sorry Mr. Brown,
> Silly question but I will ask anyway... I set my socket to be 30... so when
> I set up tcp/ip do I need to say socket30 &?
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54618
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 4:01 PM
post54621
|
Re: Networking issues with QNX 4
Sorry,
Poor technical skills when you are trying to multitask by speaking to other people...haha.
So I did the following...
Net &
Net.rtl8169 -V10ec -d8168 &
Net.rtl8169 -V10ec -d8169 -l2 &
Socket.30 &
I got several initialization errors but noticed that my socket was not found (Socket.30 was not found). I'm starting to
think that even though the drivers are set up, my port may not be on? or in other words, my socket isnt configured?
turned "on?"
What do you think?
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/13/2010 4:05 PM
post54623
|
Re: Networking issues with QNX 4
No, you cannot start Socket like that. The shell will try to find Socket.30
and not Socket, unless you renamed the Socket program to Socket.30.
Otherwise, it your node is 30, then you must start 'Socket 30 &'.
On 10-05-13 4:01 PM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Sorry,
> Poor technical skills when you are trying to multitask by speaking to other
> people...haha.
>
> So I did the following...
>
> Net &
> Net.rtl8169 -V10ec -d8168 &
> Net.rtl8169 -V10ec -d8169 -l2 &
> Socket.30 &
>
> I got several initialization errors but noticed that my socket was not found
> (Socket.30 was not found). I'm starting to think that even though the drivers
> are set up, my port may not be on? or in other words, my socket isnt
> configured? turned "on?"
>
> What do you think?
>
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54621
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 8:46 AM
post54668
|
Re: Networking issues with QNX 4
Good Morning Mr Brown,
Thanks for all your help.
I have done the following with the corresponding messages
>>Net &
%1 + 31037 Done (255) Net NG Net: Parse_args() Failed
>>Net.rtl8169 -V10ec -d8168 &
%1 + 31120 Running Net.rtl8169 -V10ec -d8168
#Net.rtl8169: Initialization error 4
Net.rtl8169 -V10ec -d8169 l2 &
%1 - 31120 Done (1) Net.rtl8169 -V10ec -d8168
%2 + 31553 Running Net.rtl8169 -V10ec -d8169 l2
#Net.rtl8169: Initialization error 4
Socket 30 &
Socket: Unable to attach name /qnx/socket
%1 + 32665 Done (1) Socket 30
%2 - 31553 Done (1) Net.rtl8169 -V10ec -d8169 l2
Any thoughts?
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 9:46 AM
post54678
|
Re: Networking issues with QNX 4
If you boot your machine and run 'sin', is Net already running? Also check
to see if there are any instances of Net.rtl8169 running. If so, then you
don't need to start Net. Look at your /etc/config/sysinit.node file and see
what it is doing.
On 10-05-14 8:46 AM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Good Morning Mr Brown,
> Thanks for all your help.
>
> I have done the following with the corresponding messages
>
>>> Net &
> %1 + 31037 Done (255) Net NG Net: Parse_args() Failed
>
>>> Net.rtl8169 -V10ec -d8168 &
>
> %1 + 31120 Running Net.rtl8169 -V10ec -d8168
>
> #Net.rtl8169: Initialization error 4
>
> Net.rtl8169 -V10ec -d8169 l2 &
> %1 - 31120 Done (1) Net.rtl8169 -V10ec -d8168
> %2 + 31553 Running Net.rtl8169 -V10ec -d8169 l2
>
> #Net.rtl8169: Initialization error 4
>
> Socket 30 &
>
> Socket: Unable to attach name /qnx/socket
> %1 + 32665 Done (1) Socket 30
> %2 - 31553 Done (1) Net.rtl8169 -V10ec -d8169 l2
>
>
> Any thoughts?
>
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54668
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 10:02 AM
post54681
|
Re: Networking issues with QNX 4
So it looks like Net is running and two Net.rt18169 are running...When looking in my sysinit file I have this
#Image: /boot/sys/boot -v
#Image: /boot/sys/Proc32 -l 30
#Image: /boot/sys/Slib32
#Image: /boot/sys/Slib16
#Image: /bin/Fsys -Hdisk160
#Image: /bin/Fsys.atapi fsys -Ndsk0 -n0=hd0. -n5=cd0.
#Image: /bin/mount -p /dev/hd0.0 /dev/hd0.0t77 /
#Image: /bin/sinit TERM=qnxm
#export NODE=30
export KBD=en_US_101.kbd
export ABLANG=en
export CON_KBD=USA
export TZ=est05edt04,M4.1.0/2,M10.5.0/2
/bin/rtc -l hw
Dev &
emu87 &
Pipe &
/bin/Dev.ser -N/dev/ser1 3f8,4 &
Dev.ansi -Q -n6 &
reopen /dev/con1
kbd $CON_KBD
prefix -A /dev/console=/dev/con1
Dev.par &
Dev.pty -n16 &
Iso9660fsys /cd0.0=/dev/cd0.0 &
# Define the default CD Rom
/bin/prefix -A /cd=//0/cd0.0
/bin/Net -d8 &
/bin/Net.rtl8169 -l1 -pe800 -i11 &
/bin/Net.rt18169 -l2 -pd800 -i11 &
netmap -f
nameloc &
chkfsys -P /
if test -f /etc/config/bin/tcpip.$NODE
then
. /etc/config/bin/tcpip.$NODE
fi
if test -f /etc/config/bin/ph.$NODE
then
. /etc/config/bin/ph.$NODE
else
tinit -t /dev/con1 &
tinit -T /dev/con[2-6] &
fi
I'm thinking I dont need those two instances of Net.rtl8169 in the code...I could comment the first one ...-l1 out...but
should I maybe include the subnet masks and ip address in the code so that it is hardcoded in the sys file?
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 10:08 AM
post54684
|
Re: Networking issues with QNX 4
If you only need one network running, then comment one of them out. You can
edit the tcpip.$NODE file to start Socket.
On 10-05-14 10:02 AM, "Julian Babel" <community-noreply@qnx.com> wrote:
> So it looks like Net is running and two Net.rt18169 are running...When looking
> in my sysinit file I have this
>
> #Image: /boot/sys/boot -v
> #Image: /boot/sys/Proc32 -l 30
> #Image: /boot/sys/Slib32
> #Image: /boot/sys/Slib16
> #Image: /bin/Fsys -Hdisk160
> #Image: /bin/Fsys.atapi fsys -Ndsk0 -n0=hd0. -n5=cd0.
> #Image: /bin/mount -p /dev/hd0.0 /dev/hd0.0t77 /
> #Image: /bin/sinit TERM=qnxm
> #export NODE=30
> export KBD=en_US_101.kbd
> export ABLANG=en
> export CON_KBD=USA
> export TZ=est05edt04,M4.1.0/2,M10.5.0/2
> /bin/rtc -l hw
> Dev &
> emu87 &
> Pipe &
> /bin/Dev.ser -N/dev/ser1 3f8,4 &
> Dev.ansi -Q -n6 &
> reopen /dev/con1
> kbd $CON_KBD
> prefix -A /dev/console=/dev/con1
> Dev.par &
> Dev.pty -n16 &
> Iso9660fsys /cd0.0=/dev/cd0.0 &
> # Define the default CD Rom
> /bin/prefix -A /cd=//0/cd0.0
> /bin/Net -d8 &
> /bin/Net.rtl8169 -l1 -pe800 -i11 &
> /bin/Net.rt18169 -l2 -pd800 -i11 &
> netmap -f
> nameloc &
> chkfsys -P /
> if test -f /etc/config/bin/tcpip.$NODE
> then
> . /etc/config/bin/tcpip.$NODE
> fi
> if test -f /etc/config/bin/ph.$NODE
> then
> . /etc/config/bin/ph.$NODE
> else
> tinit -t /dev/con1 &
> tinit -T /dev/con[2-6] &
> fi
>
>
> I'm thinking I dont need those two instances of Net.rtl8169 in the code...I
> could comment the first one ...-l1 out...but should I maybe include the subnet
> masks and ip address in the code so that it is hardcoded in the sys file?
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54681
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 10:25 AM
post54689
|
Re: Networking issues with QNX 4
I commented out the one line with:
/bin/Net.rtl8169 -l2 -pd800 -i11 &
Since I don't need to run the net, and I commented out the Net l2 line, and also looking at the sin I guess we've
determined that the drivers are in fact running but it's the socket that may be issue? You said I can edit the tcpip.$
NODE lines? does that mean I should replace it with tcpip.30?
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 10:30 AM
post54690
|
Re: Networking issues with QNX 4
Look at the /etc/config/bin/tcpip.$NODE file, where $NODE is the node number
of your machine. Eg. tcpip.1. Edit this file to suite your requirements.
On 10-05-14 10:25 AM, "Julian Babel" <community-noreply@qnx.com> wrote:
> I commented out the one line with:
>
> /bin/Net.rtl8169 -l2 -pd800 -i11 &
>
> Since I don't need to run the net, and I commented out the Net l2 line, and
> also looking at the sin I guess we've determined that the drivers are in fact
> running but it's the socket that may be issue? You said I can edit the
> tcpip.$NODE lines? does that mean I should replace it with tcpip.30?
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54689
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 10:56 AM
post54712
|
Re: Networking issues with QNX 4
Ok, so looked within tcpip.30 and did some minor editing
#! /bin/ksh
/usr/ucb/Socklet -p 1 node$NODE &
/usr/ucb/ifconfig lo0 localhost up
/usr/ucb/ifconfig en1 node$NODE up
/usr/ucb/inetd /etc/config/inetd.30 &
I was thinking that should fix my problem, but alas, no luck. I'm starting to run out of options. I did deal with tcp
network issues with my other boxes, but I was able to edit the code within the sysinit file. The difference between
those boxes and these is that I was using Digicards, whereas this will be my first ethernet box. Why it doesn't seem to
recognize the socket, I am a bit confused.
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 11:03 AM
post54718
|
Re: Networking issues with QNX 4
Is node30 defined in your /etc/hosts file? Is en1 the interface that is
running? Look at 'netstat -in' to see what interface is configured. You can
also look at the TCP/IP documentation to see how to setup an TCP/IP
connection.
On 10-05-14 10:56 AM, "Julian Babel" <community-noreply@qnx.com> wrote:
> Ok, so looked within tcpip.30 and did some minor editing
>
> #! /bin/ksh
> /usr/ucb/Socklet -p 1 node$NODE &
> /usr/ucb/ifconfig lo0 localhost up
> /usr/ucb/ifconfig en1 node$NODE up
> /usr/ucb/inetd /etc/config/inetd.30 &
>
> I was thinking that should fix my problem, but alas, no luck. I'm starting to
> run out of options. I did deal with tcp network issues with my other boxes,
> but I was able to edit the code within the sysinit file. The difference
> between those boxes and these is that I was using Digicards, whereas this will
> be my first ethernet box. Why it doesn't seem to recognize the socket, I am a
> bit confused.
>
>
>
> _______________________________________________
>
> QNX4 Community Support
> http://community.qnx.com/sf/go/post54712
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 11:24 AM
post54722
|
Re: Networking issues with QNX 4
node30 is defined in the host file
en1 is the interface used
netstat -in gives me the following:
Name: Mtu Network address
en1 1500 <link> 0.26.f2.ac.bd.9
en1 1500 192.168.1 192.168.1.30
ppp0* 1500 <link>
lo0 1536 <link>
lo0 1536 127 127.0.0.1
I'll look for the tcp/ip documentation..I thought I tried that but i'll give it another shot. Also..I know i've been
saying socket but I get pings from 192.1168.1.30 but say..I want it to my external driver which is .50...I can't reach
out. I'll try the documentation as well though.
|
|
|
|
|
|
|
Re: Networking issues with QNX 4
|
|
05/14/2010 12:03 PM
post54732
|
Re: Networking issues with QNX 4
So I tried to go back into sysinit.30 and I did the following
I added this at the end of the current script
sleep4
nettrap
sleep4
#network
/etc/netstart
/usr/ucb/ifconfig en1 192.168.1.30 netmask 255.255.255.0
/usr/ucb/route add default 192.168.1.255
/usr/ucb/route/ add -net 192.168.1.30 192.168.1.255
sleep 2
I rebooted and unfortunately it hung..think I need to do some more tweaking?
|
|
|
|
|
|