Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Start script for two network cards: (18 Items)
   
Start script for two network cards  
I have a qnx6.3.2 PC104 computer stack with two network cards, one is the onboard ethernet card, the other the orinoco 
wifi network card. Basically, i wanna use the wifi card for msg passing with other qnx machines, while the wired card 
for debugging usage. I have two problems:

1. I use the following boot scripts to start the wired network qnet:
    io-net -d ns83815 -p tcpip -p qnet &
    waitfor /dev/io-net/en0 
    waitfor /dev/socket/2

    ifconfig en0 *.*.*.*
and it works fine. but i used
    devp-pccard
    io-net -d orinoco -p tcpip

the machine gave the error during its boot:
    unable to init dll devn-orinoco: No such device.

But when the machine finishes starting, i typed the above two commands again, the orinoco wifi card starts to work. i 
have no ideas about this.

2. There are two network interfaces, so i should assign two different ip address for each interface? for the wired 
network case, the above scripts are okay. how about when coming the assign the ip to the wifi network card? use en1? or 
??

Thank you
Eric
RE: Start script for two network cards  
1) I wonder if you're starting things too early...  Is it possible that
you're trying to launch the Orinoco driver before devp-pccard has
completed?  If you add in a "waitfor /dev/pccard" after devp-pccard,
does that make any difference?

Also, just to make sure...  You aren't running two versions of the stack
on startup are you?  If you want to have two separate interfaces, you
have to either specify both on the command line (with separate -d
options) or "mount" the interfaces after io-net has started.  

2)  Interfaces in io-net are numbered sequentially from 0 as they're
loaded in.  You can either use dhcp.client or manually assign the
interface an IP address.  Make sure that the two interfaces are on
separate subnets though.  If you assign addresses on the same subnet to
different interfaces, you'll get peculiar results.


	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Tuesday, June 17, 2008 7:25 AM
To: builds-networking
Subject: Start script for two network cards

I have a qnx6.3.2 PC104 computer stack with two network cards, one is
the onboard ethernet card, the other the orinoco wifi network card.
Basically, i wanna use the wifi card for msg passing with other qnx
machines, while the wired card for debugging usage. I have two problems:

1. I use the following boot scripts to start the wired network qnet:
    io-net -d ns83815 -p tcpip -p qnet &
    waitfor /dev/io-net/en0 
    waitfor /dev/socket/2

    ifconfig en0 *.*.*.*
and it works fine. but i used
    devp-pccard
    io-net -d orinoco -p tcpip

the machine gave the error during its boot:
    unable to init dll devn-orinoco: No such device.

But when the machine finishes starting, i typed the above two commands
again, the orinoco wifi card starts to work. i have no ideas about this.

2. There are two network interfaces, so i should assign two different ip
address for each interface? for the wired network case, the above
scripts are okay. how about when coming the assign the ip to the wifi
network card? use en1? or ??

Thank you
Eric


_______________________________________________
Builds
http://community.qnx.com/sf/go/post9277
Re: RE: Start script for two network cards  
thx, Robet. now my scripts are like this:

    io-net -d ns83815 -p tcpip -p qnet &
    waitfor /dev/io-net/en0 
    waitfor /dev/socket/2
    
    ifconfig en0 *.*.*.* 
    netmask 255.255.0.0


	devp-pccard
	waitfor /proc/boot/devp-pccard (i put this binary here on the target)
	io-net -d orinoco channel=11,network=nusuav,mode=adhoc -p tcpip 
	sleep 2
	ifconfig en1 192.168.1.10 netmask 255.255.255.0


still the same error. thx for ur suggestions.

Eric
RE: RE: Start script for two network cards  
Hi Eric:
	There are a couple of problems here...
The

waitfor /dev/pccard

must be as typed.  What this does is wait for the devp-pccard binary to
start up and register /dev/pccard (as opposed to looking for the
binary).  The /dev/pccard entry is what the libs look for in order to
get access to the pccard information.

The second problem is that you're starting up two version of io-net and
this isn't going to give you the expected behaviour.  
Give this a try:

/proc/boot/devp-pccard

waitfor /dev/pccard
io-net -d ns83815 -d orinoco channel=11,network=nusuav,mode=adhoc -p
tcpip -p qnet &
waitfor /dev/io-net/en0 
wauitfor /dev/io-net/en1
waitfor /dev/socket
    
ifconfig en0 *.*.*.* netmask 255.255.0.0
ifconfig en1 *.*.*.* netmask 255.255.0.0



I suspect that this isn't going to fix the Orinoco problem since you're
sleep 2 should have been adequate. Is there any information in sloginfo?
(Is slogger up and running before you're script starts)?  You can also
add -vvv options to each of the drivers to get additional output for
debugging.  If the command works at the command line after the system is
booted, then there's another dependency that's being missed out on.

	Hope that helps,
		Robert.


-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Wednesday, June 18, 2008 3:31 AM
To: builds-networking
Subject: Re: RE: Start script for two network cards

thx, Robet. now my scripts are like this:

    io-net -d ns83815 -p tcpip -p qnet &
    waitfor /dev/io-net/en0 
    waitfor /dev/socket/2
    
    ifconfig en0 *.*.*.* 
    netmask 255.255.0.0


	devp-pccard
	waitfor /proc/boot/devp-pccard (i put this binary here on the
target)
	io-net -d orinoco channel=11,network=nusuav,mode=adhoc -p tcpip 
	sleep 2
	ifconfig en1 192.168.1.10 netmask 255.255.255.0


still the same error. thx for ur suggestions.

Eric


_______________________________________________
Builds
http://community.qnx.com/sf/go/post9371
Re: RE: RE: Start script for two network cards  
thx, Robert.

The script "io-net -d ns83815 -d orinoco channel=11,network=nusuav,mode=adhoc -p tcpip -p qnet &"

is going to assign two interfaces to the two network cards, right? a little confused is that the -p option, here can 
ns83815 work with tcpip and qnet while orinoco only work with tcpip or also with qnet?

Another problem about the orinoco, would it be that i need to put the devn-orinoco.so into some particular directory? 

thx
Eric
RE: RE: RE: Start script for two network cards  
Hi Eric:
	If you want to restrict the usage of qnet to a single interface
(the ns83815), you can use the following line

io-net -d ns83815 -d orinoco channel=11,network=nusuav,mode=adhoc -p
tcpip -p qnet bind=en0


And yes, devn-orinoco.so needs to be in the same place as you're ns83815
binary.

	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Thursday, June 19, 2008 8:06 AM
To: builds-networking
Subject: Re: RE: RE: Start script for two network cards

thx, Robert.

The script "io-net -d ns83815 -d orinoco
channel=11,network=nusuav,mode=adhoc -p tcpip -p qnet &"

is going to assign two interfaces to the two network cards, right? a
little confused is that the -p option, here can ns83815 work with tcpip
and qnet while orinoco only work with tcpip or also with qnet?

Another problem about the orinoco, would it be that i need to put the
devn-orinoco.so into some particular directory? 

thx
Eric

_______________________________________________
Builds
http://community.qnx.com/sf/go/post9421
Re: RE: RE: RE: Start script for two network cards  
thx again, Robert.

I put devn-orinoco.so in the same directory as devn-ns83815--/x86/dll
but still the same error:
   unable to load dll /x86/dll/orinoco: Library cannot be found
   unable to access "/dev/io-net/en1"

and when i tried "sloginfo":
   Unable to open /dev/slog: No such file or directory.

however, when the target finished booting, i typed "io-net -d orinoco -p tcpip" without specifying its directory, the 
orinoco card worked.
Appreciate your help.

Eric
Re: RE: RE: RE: Start script for two network cards  
> however, when the target finished booting, i typed "io-net -d orinoco -p tcpip
> " without specifying its directory, the orinoco card worked.

sorry, plz ignore this. i still kept the previous one under /proc/boot.

RE: RE: RE: RE: Start script for two network cards  
Hi Eric:

	You need to run "slogger" before you start io-net to get
sloginfo to work.

	I take it from the follow on e-mail that the orinoco driver
wasn't in the correct directory?  

	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Thursday, June 19, 2008 11:10 AM
To: builds-networking
Subject: Re: RE: RE: RE: Start script for two network cards

thx again, Robert.

I put devn-orinoco.so in the same directory as devn-ns83815--/x86/dll
but still the same error:
   unable to load dll /x86/dll/orinoco: Library cannot be found
   unable to access "/dev/io-net/en1"

and when i tried "sloginfo":
   Unable to open /dev/slog: No such file or directory.

however, when the target finished booting, i typed "io-net -d orinoco -p
tcpip" without specifying its directory, the orinoco card worked.
Appreciate your help.

Eric

_______________________________________________
Builds
http://community.qnx.com/sf/go/post9434
Re: RE: RE: RE: RE: Start script for two network cards  
Hi, Robert, here is the output of my sloginfo.txt:

Time             Sev Major Minor Args
Feb 17 21:30:41    5    18     0 devp-pccard: Found Vendor 104c - Device ac51
Feb 17 21:30:42    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:42    5    18     0 GetStatus Socket 1 returned CardState 80 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 
1
Feb 17 21:30:42    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 0 -
VccLevel 0 - CtlInd 0 - State 80 - IREQRouting 0 - IFType 1
Feb 17 21:30:42    5    18     0 Socket state 80
Feb 17 21:30:42    5    18     0 Card Inserted
Feb 17 21:30:42    5    18     0 5.0V Card
Feb 17 21:30:42    5    18     0 io_open for id = 30007
Feb 17 21:30:42    2    18     0 io_close_ocb
Feb 17 21:30:42    5    18     0 io_open for id = 7
Feb 17 21:30:43    2    18     0 Timer expired 2
Feb 17 21:30:43    5    18     0 Powered up 2
Feb 17 21:30:43    5    14     0 tcpip starting
Feb 17 21:30:43    3    14     0 Using pseudo random generator.  See "random" option
Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:43    5    18     0 devp-pccard: Memory window req. 0
Feb 17 21:30:43    5    18     0 devp-pccard: Memory window act. 1e001000
Feb 17 21:30:43    2    18     0 LAN Node ID 00 02 2d 07 22 5e 
Feb 17 21:30:43    5    18     0 Config Base 3e0
Feb 17 21:30:43    5    18     0 Rmask 1
Feb 17 21:30:43    5    18     0 Rmask 0
Feb 17 21:30:43    5    18     0 Rmask 0
Feb 17 21:30:43    5    18     0 Rmask 0
Feb 17 21:30:43    5    18     0 IRQ1 = 7f - IRQ2 = ffff
Feb 17 21:30:43    5    18     0 I/O 0 - Len 64 - ip 8071ff0
Feb 17 21:30:43    5    18     0 IRQ 7
Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:43    5    18     0 I/O port 300
Feb 17 21:30:43    5    18     0 Config base 3e0 - Index 1 - Window 0 - Page 0
Feb 17 21:30:43    5    18     0 Base - 40105000 - p = 401053e0
Feb 17 21:30:44    2    18     0 Timer expired 3
Feb 17 21:30:44    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:44    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType
 1
Feb 17 21:30:44    5    18     0 GetSocket Socket 1 returned SCIntMask 0 - Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:44    5    18     0 Socket state c0
Feb 17 21:30:44    5    18     0 Card Inserted
Feb 17 21:30:45    2    18     0 Timer expired 3
Feb 17 21:30:45    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:45    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType
 1
Feb 17 21:30:46    2    18     0 Timer expired 3
Feb 17 21:30:47    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:47    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType
 1
Feb 17 21:30:48    2    18     0 Timer expired 3
Feb 17 21:30:48    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1

Feb 17 21:30:48    5    18     0 GetStatus Socket 1 returned CardState c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType
 1
Feb 17 21:30:49    2    18     0 Timer expired 3
Feb 17 21:30:49    5    18     0 GetStatus Socket 0 returned CardState 0 - CtlInd 0 - State 0 - IREQRouting 0 -...
View Full Message
RE: RE: RE: RE: RE: Start script for two network cards  
Hi Eric:

	I've asked around and it looks like the network driver is trying
to access the card before it's been enumerated....

Make sure that you have

waitfor /dev/pccard

and add

sleep(3)

after it in the script before you start io-net.


	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Friday, June 20, 2008 3:17 AM
To: builds-networking
Subject: Re: RE: RE: RE: RE: Start script for two network cards

Hi, Robert, here is the output of my sloginfo.txt:

Time             Sev Major Minor Args
Feb 17 21:30:41    5    18     0 devp-pccard: Found Vendor 104c - Device
ac51
Feb 17 21:30:42    5    18     0 GetStatus Socket 0 returned CardState 0
- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1
Feb 17 21:30:42    5    18     0 GetStatus Socket 1 returned CardState
80 - CtlInd 0 - State 0 - IREQRouting 0 - IFType 1
Feb 17 21:30:42    5    18     0 GetSocket Socket 1 returned SCIntMask 0
- Vcontrol 10 - VppLevels 0 -
VccLevel 0 - CtlInd 0 - State 80 - IREQRouting 0 - IFType 1
Feb 17 21:30:42    5    18     0 Socket state 80
Feb 17 21:30:42    5    18     0 Card Inserted
Feb 17 21:30:42    5    18     0 5.0V Card
Feb 17 21:30:42    5    18     0 io_open for id = 30007
Feb 17 21:30:42    2    18     0 io_close_ocb
Feb 17 21:30:42    5    18     0 io_open for id = 7
Feb 17 21:30:43    2    18     0 Timer expired 2
Feb 17 21:30:43    5    18     0 Powered up 2
Feb 17 21:30:43    5    14     0 tcpip starting
Feb 17 21:30:43    3    14     0 Using pseudo random generator.  See
"random" option
Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0
- Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:43    5    18     0 devp-pccard: Memory window req. 0
Feb 17 21:30:43    5    18     0 devp-pccard: Memory window act.
1e001000
Feb 17 21:30:43    2    18     0 LAN Node ID 00 02 2d 07 22 5e 
Feb 17 21:30:43    5    18     0 Config Base 3e0
Feb 17 21:30:43    5    18     0 Rmask 1
Feb 17 21:30:43    5    18     0 Rmask 0
Feb 17 21:30:43    5    18     0 Rmask 0
Feb 17 21:30:43    5    18     0 Rmask 0
Feb 17 21:30:43    5    18     0 IRQ1 = 7f - IRQ2 = ffff
Feb 17 21:30:43    5    18     0 I/O 0 - Len 64 - ip 8071ff0
Feb 17 21:30:43    5    18     0 IRQ 7
Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0
- Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:43    5    18     0 GetSocket Socket 1 returned SCIntMask 0
- Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:43    5    18     0 I/O port 300
Feb 17 21:30:43    5    18     0 Config base 3e0 - Index 1 - Window 0 -
Page 0
Feb 17 21:30:43    5    18     0 Base - 40105000 - p = 401053e0
Feb 17 21:30:44    2    18     0 Timer expired 3
Feb 17 21:30:44    5    18     0 GetStatus Socket 0 returned CardState 0
- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1
Feb 17 21:30:44    5    18     0 GetStatus Socket 1 returned CardState
c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:44    5    18     0 GetSocket Socket 1 returned SCIntMask 0
- Vcontrol 10 - VppLevels 22 -
VccLevel 2 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:44    5    18     0 Socket state c0
Feb 17 21:30:44    5    18     0 Card Inserted
Feb 17 21:30:45    2    18     0 Timer expired 3
Feb 17 21:30:45    5    18     0 GetStatus Socket 0 returned CardState 0
- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1
Feb 17 21:30:45    5    18     0 GetStatus Socket 1 returned CardState
c0 - CtlInd 0 - State c0 - IREQRouting 0 - IFType 1
Feb 17 21:30:46    2    18     0 Timer expired 3
Feb 17 21:30:47    5    18     0 GetStatus Socket 0 returned CardState 0
- CtlInd 0 - State 0 - IREQRouting 0 - IFType 1
Feb 17 21:30:47    5    18     0 GetStatus Socket 1 returned CardState
c0 - CtlInd 0 -...
View Full Message
Re: RE: RE: RE: RE: RE: Start script for two network cards  
Hi, Robert, My whole script is belows:

# Start up some consoles
	devc-con -n1 &
	reopen /dev/con1
	devc	
    display_msg Welcome 
# Start the pci server
	display_msg "start sedres pci-bios "
	seedres	
	pci-bios &
	waitfor /dev/pci
	
# Start up the CompactFlash Disk drivers 
	display_msg "auto mount CF card hd0t77...."
    devb-eide blk automount=hd0t77:/ eide nobmstr &
    
# Wait for th uav/bin for the rest of the commands (up to 200 secs)
	display_msg "waitfor /x86/bin....."
	waitfor /x86/bin 10	

#Start up TCP/IP and QNET
	slogger
	sleep 5
	
	sloginfo -c
	/proc/boot/devp-pccard -vvvv &
	waitfor /dev/pccard 59
#	sloginfo > sloginfo.txt
	io-net -d ns83815 -d orinoco channel=11,network=mywork,mode=adhoc -p tcpip -p qnet bind=en0
	waitfor /dev/io-net/en0 
	waitfor /dev/io-net/en1
	waitfor /dev/socket
	
	ifconfig en0 *.*.*.* netmask 255.255.0.0
	ifconfig en1 *.*.*.* netmask 255.255.255.0
	   
# Start some common servers
    display_msg "some drivers , especially devc-ser8250, starts...."
	qconn &
	pipe &
	mqueue &
	devc-pty &
	
    devc-ser8250 -u 1 -b 57600 3f8,4&
    devc-ser8250 -u 2 -b 115200 2f8,3&
    devc-ser8250 -u 3 -b 115200 3e8,9&
#	devc-ser8250 -u 4 -b 115200 2e8,3&
        
   .........

RE: RE: RE: RE: RE: RE: Start script for two network cards  
Just a thought.

Maybe put "pin" in your image, and try run it after "waitfor /dev/pccard
59", see if "pin" can detect any device. If it can't, put "sleep 5"
before "pin".
Like this.

	/proc/boot/devp-pccard -vvvv &
	waitfor /dev/pccard 59
	/proc/boot/sleep 5
	/proc/boot/pin
	#	sloginfo > sloginfo.txt
	io-net -d ns83815 -d orinoco
channel=11,network=mywork,mode=adhoc -p tcpip -p qnet bind=en0  

-xtang

> -----Original Message-----
> From: Eric Dong [mailto:eric.dongxx@gmail.com]
> Sent: June 21, 2008 12:18 AM
> To: builds-networking
> Subject: Re: RE: RE: RE: RE: RE: Start script for two network cards
> 
> Hi, Robert, My whole script is belows:
> 
> # Start up some consoles
> 	devc-con -n1 &
> 	reopen /dev/con1
> 	devc
>     display_msg Welcome
> # Start the pci server
> 	display_msg "start sedres pci-bios "
> 	seedres
> 	pci-bios &
> 	waitfor /dev/pci
> 
> # Start up the CompactFlash Disk drivers
> 	display_msg "auto mount CF card hd0t77...."
>     devb-eide blk automount=hd0t77:/ eide nobmstr &
> 
> # Wait for th uav/bin for the rest of the commands (up to 200 secs)
> 	display_msg "waitfor /x86/bin....."
> 	waitfor /x86/bin 10
> 
> #Start up TCP/IP and QNET
> 	slogger
> 	sleep 5
> 
> 	sloginfo -c
> 	/proc/boot/devp-pccard -vvvv &
> 	waitfor /dev/pccard 59
> #	sloginfo > sloginfo.txt
> 	io-net -d ns83815 -d orinoco
channel=11,network=mywork,mode=adhoc -p
> tcpip -p qnet bind=en0
> 	waitfor /dev/io-net/en0
> 	waitfor /dev/io-net/en1
> 	waitfor /dev/socket
> 
> 	ifconfig en0 *.*.*.* netmask 255.255.0.0
> 	ifconfig en1 *.*.*.* netmask 255.255.255.0
> 
> # Start some common servers
>     display_msg "some drivers , especially devc-ser8250, starts...."
> 	qconn &
> 	pipe &
> 	mqueue &
> 	devc-pty &
> 
>     devc-ser8250 -u 1 -b 57600 3f8,4&
>     devc-ser8250 -u 2 -b 115200 2f8,3&
>     devc-ser8250 -u 3 -b 115200 3e8,9&
> #	
devc-ser8250 -u 4 -b 115200 2e8,3&
> 
>    .........
> 
> 
> 
> _______________________________________________
> Builds
> http://community.qnx.com/sf/go/post9498
Re: RE: RE: RE: RE: RE: RE: Start script for two network cards  
thx, i tried like this from another guy's idea, and it worked fine now.

 sloginfo -c
/proc/boot/devp-pccard -vvvv &
waitfor /dev/pccard 59
# sloginfo > sloginfo.txt
io-net -d ns83815 -p tcpip -p qnet bind=en0
waitfor /dev/io-net/en0
waitfor /dev/socket

ifconfig en0 *.*.*.* netmask 255.255.0.0

mount -o channel=11,network=mywork,mode=adhoc -Tio-net devn-orinoco.so
waitfor /dev/io-net/en1
ifconfig en1 *.*.*.* netmask 255.255.255.0

seemed changed the io-net with mount would make effects?

Eric
RE: RE: RE: RE: RE: RE: RE: Start script for two network cards  
Hi Eric:
	Only thing I can think of again is timing.  The time it takes to
set up and configure the first interface is what's needed for the pccard
server to settle so that it's ready when the Orinoco is mounted...

	Robert.

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Monday, June 23, 2008 8:49 AM
To: builds-networking
Subject: Re: RE: RE: RE: RE: RE: RE: Start script for two network cards

thx, i tried like this from another guy's idea, and it worked fine now.

 sloginfo -c
/proc/boot/devp-pccard -vvvv &
waitfor /dev/pccard 59
# sloginfo > sloginfo.txt
io-net -d ns83815 -p tcpip -p qnet bind=en0
waitfor /dev/io-net/en0
waitfor /dev/socket

ifconfig en0 *.*.*.* netmask 255.255.0.0

mount -o channel=11,network=mywork,mode=adhoc -Tio-net devn-orinoco.so
waitfor /dev/io-net/en1
ifconfig en1 *.*.*.* netmask 255.255.255.0

seemed changed the io-net with mount would make effects?

Eric

_______________________________________________
Builds
http://community.qnx.com/sf/go/post9512
Re: RE: RE: RE: RE: RE: RE: RE: Start script for two network cards  
well, seems not fully solved:
the adhoc network could not work now, i tried "nicinfo"
only the wired ethernet network card showed its message, without the wireless orinoco.  since when i only "io-net -d 
orinoco -p tcpip", "nicinfo" would show the orinoco's info.
so, the orinoco card still could not work, i.e. "mount -o channel=11,......-p tcpip" didnot fully start the orinoco card
.

Eric
Re: RE: RE: RE: RE: RE: RE: RE: Start script for two network cards  
> well, seems not fully solved:
> the adhoc network could not work now, i tried "nicinfo"
> only the wired ethernet network card showed its message, without the wireless 
> orinoco.  since when i only "io-net -d orinoco -p tcpip", "nicinfo" would show
>  the orinoco's info.
> so, the orinoco card still could not work, i.e. "mount -o channel=11,......-p 
> tcpip" didnot fully start the orinoco card.
> 
> Eric


some updates, the problem now is that qnx machines in the wlan could not ping thru one another in the adhoc mode.
when i tried "nicinfo -r en1" it would display the nicinfo of the orinoco card like follows:

ORiNOCO 802.11 Wireless Ethernet Controller

  Physical Node ID ........................... 00022D 01B57F
  Current Physical Node ID ................... 00022D 01B57F
  Current Operation Rate ..................... 11.00 Mb/s half-duplex
  Active Interface Type ...................... Unknown
  Maximum Transmittable data Unit ............ 1514
  Maximum Receivable data Unit ............... 1514
  Hardware Interrupt ......................... 0x3
  I/O Aperture ............................... 0x300 - 0x33f
  Promiscuous Mode ........................... Off
  Multicast Support .......................... Enabled

  Station Name ............................... 
  Network Name (SSID) ........................ 
  Channel: ................................... 4294967295
  BSS Type ................................... Unknown

  Packets Transmitted OK ..................... 0
  Bytes Transmitted OK ....................... 300

  Packets Received OK ........................ 3
  Bytes Received OK .......................... 0 

so, what are the possible reasons here? thx

Eric
RE: RE: RE: RE: RE: RE: RE: RE: Start script for two network cards  
Hi Eric:
	This is a driver problem so you need to post the information in
the drivers forum.  (Which I believe that you've already done with the
"WLAN among qnx" thread).

	Robert

-----Original Message-----
From: Eric Dong [mailto:eric.dongxx@gmail.com] 
Sent: Tuesday, June 24, 2008 9:30 AM
To: builds-networking
Subject: Re: RE: RE: RE: RE: RE: RE: RE: Start script for two network
cards

> well, seems not fully solved:
> the adhoc network could not work now, i tried "nicinfo"
> only the wired ethernet network card showed its message, without the
wireless 
> orinoco.  since when i only "io-net -d orinoco -p tcpip", "nicinfo"
would show
>  the orinoco's info.
> so, the orinoco card still could not work, i.e. "mount -o
channel=11,......-p 
> tcpip" didnot fully start the orinoco card.
> 
> Eric


some updates, the problem now is that qnx machines in the wlan could not
ping thru one another in the adhoc mode.
when i tried "nicinfo -r en1" it would display the nicinfo of the
orinoco card like follows:

ORiNOCO 802.11 Wireless Ethernet Controller

  Physical Node ID ........................... 00022D 01B57F
  Current Physical Node ID ................... 00022D 01B57F
  Current Operation Rate ..................... 11.00 Mb/s half-duplex
  Active Interface Type ...................... Unknown
  Maximum Transmittable data Unit ............ 1514
  Maximum Receivable data Unit ............... 1514
  Hardware Interrupt ......................... 0x3
  I/O Aperture ............................... 0x300 - 0x33f
  Promiscuous Mode ........................... Off
  Multicast Support .......................... Enabled

  Station Name ............................... 
  Network Name (SSID) ........................ 
  Channel: ................................... 4294967295
  BSS Type ................................... Unknown

  Packets Transmitted OK ..................... 0
  Bytes Transmitted OK ....................... 300

  Packets Received OK ........................ 3
  Bytes Received OK .......................... 0 

so, what are the possible reasons here? thx

Eric

_______________________________________________
Builds
http://community.qnx.com/sf/go/post9565