I have two orinoco wireless card for two PC104 systems separately. Both
should commnunicate directly via an Orinoco Acess Point 200 located in my
office. The problem I encountered is that the system always routes to the
wireless network in the campus instead via the Orinoco AP in the office. And
I checked with the network manager of the campus, and there is nothing wrong
in his side.
I configure the wireless card this way:
1, create a file /etc/rc.d/rc.local to invoke the orinoco driver; and call
/etc/net.cfg
2, in /etc/net.cfg, I define IP/Netmask as the following:
[global]
hostname xxxx
domain xxxx
nameserver xxxx
nameserver xxxx
route xxxx
lookup file bind
[en0]
type ethernet
mode dhcp
manual_ip xxxx
manual_netmask xxxx
Do I miss other configurations? Could anybody please tell me what is wrong
and how to correct it?
Thanks.
Jeff Chang <jianjunc@cae.wisc.edu> wrote:
I have two orinoco wireless card for two PC104 systems separately. Both
should commnunicate directly via an Orinoco Acess Point 200 located in my
office. The problem I encountered is that the system always routes to the
wireless network in the campus instead via the Orinoco AP in the office. And
I checked with the network manager of the campus, and there is nothing wrong
in his side.
In your rc.local script make sure you force the name of the network you
want to connect with…
io-net -d orinoco network=mynetwork
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
I did that.
“Chris McKillop” <cdm@qnx.com> wrote in message
news:c7c83t$rvc$1@inn.qnx.com…
Jeff Chang <> jianjunc@cae.wisc.edu> > wrote:
I have two orinoco wireless card for two PC104 systems separately. Both
should commnunicate directly via an Orinoco Acess Point 200 located in
my
office. The problem I encountered is that the system always routes to
the
wireless network in the campus instead via the Orinoco AP in the office.
And
I checked with the network manager of the campus, and there is nothing
wrong
in his side.
In your rc.local script make sure you force the name of the network you
want to connect with…
io-net -d orinoco network=mynetwork
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
… In rc.local, I use “netmanager -f /etc/net.cfg” to set IP, Netmask etc
that are defined in net.cfg.
“Chris McKillop” <cdm@qnx.com> wrote in message
news:c7c83t$rvc$1@inn.qnx.com…
Jeff Chang <> jianjunc@cae.wisc.edu> > wrote:
I have two orinoco wireless card for two PC104 systems separately. Both
should commnunicate directly via an Orinoco Acess Point 200 located in
my
office. The problem I encountered is that the system always routes to
the
wireless network in the campus instead via the Orinoco AP in the office.
And
I checked with the network manager of the campus, and there is nothing
wrong
in his side.
In your rc.local script make sure you force the name of the network you
want to connect with…
io-net -d orinoco network=mynetwork
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Jeff Chang <jianjunc@cae.wisc.edu> wrote:
… In rc.local, I use “netmanager -f /etc/net.cfg” to set IP, Netmask etc
that are defined in net.cfg.
That doesn’t matter if you are coming in via the wrong access point.
I assume the output of “nicinfo” shows you associated with the wrong one?
chris
\
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Yes. The Network name is not what I defined in rc.local, and the channel is
not the channel set in the local access point.
It’s kind of weird.
“Chris McKillop” <cdm@qnx.com> wrote in message
news:c7ek7a$pa5$1@inn.qnx.com…
Jeff Chang <> jianjunc@cae.wisc.edu> > wrote:
… In rc.local, I use “netmanager -f /etc/net.cfg” to set IP, Netmask
etc
that are defined in net.cfg.
That doesn’t matter if you are coming in via the wrong access point.
I assume the output of “nicinfo” shows you associated with the wrong one?
chris
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Jeff Chang <jianjunc@cae.wisc.edu> wrote:
Yes. The Network name is not what I defined in rc.local, and the channel is
not the channel set in the local access point.
It’s kind of weird.
Can you post the contents of your rc.local?
chris
\
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
This is the rc.local I am using:
echo “Slaying Existing PC-Card Driver”
slay -v devp-pccard
sleep 2
echo “Starting PCMCIA Card Carrier Driver”
devp-pccard -a 0x300:0x320 -v
echo “Starting ORINOCO Wireless Ethernet Card Driver”
Setup the wireless ethernet connection
#Stop the current network driver
echo “Slaying the exisiting io-net Network Interface”
slay -v io-net
sleep 2
#Load the orinoco driver
128-bit encryption
io-net -d orinoco key1=xxxx,default_key=1,network=xxx -ptcpip stacksize=xxxx
sleep 2
netmanager -f /etc/net.cfg
Thanks.
“Chris McKillop” <cdm@qnx.com> wrote in message
news:c7ga3t$6i5$1@inn.qnx.com…
Jeff Chang <> jianjunc@cae.wisc.edu> > wrote:
Yes. The Network name is not what I defined in rc.local, and the channel
is
not the channel set in the local access point.
It’s kind of weird.
Can you post the contents of your rc.local?
chris
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
128-bit encryption
io-net -d orinoco key1=xxxx,default_key=1,network=xxx -ptcpip stacksize=xxxx
Any chance that the key you are using isn’t the same as your access point
but is the right one for the other access point? The firmware on the
device will try to match to other networks if the specified one cannot
be found or authenticated.
chris
\
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
I believe they are the same. But I will double check.
“Chris McKillop” <cdm@qnx.com> wrote in message
news:c7j870$c0c$1@inn.qnx.com…
128-bit encryption
io-net -d orinoco key1=xxxx,default_key=1,network=xxx -ptcpip
stacksize=xxxx
Any chance that the key you are using isn’t the same as your access point
but is the right one for the other access point? The firmware on the
device will try to match to other networks if the specified one cannot
be found or authenticated.
chris
\
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/