View topic - Broacom BCM4401-B0
Broacom BCM4401-B0
18 posts
• Page 1 of 2 • 1, 2
Broacom BCM4401-B0
Hi,
Is there driver support for Broadcom BCM4401 (vendor id=14e4h, device
id=170ch) for RTOS?
TIA
Augie
Is there driver support for Broadcom BCM4401 (vendor id=14e4h, device
id=170ch) for RTOS?
TIA
Augie
- Augie
Re: Broacom BCM4401-B0
On 05/12/2007 2:35 PM, Augie wrote:
devn-bcm43xx.so in patch 685 should support it.
--
Ryan J. Allen
QNX Software Systems
Is there driver support for Broadcom BCM4401 (vendor id=14e4h, device
id=170ch) for RTOS?
devn-bcm43xx.so in patch 685 should support it.
--
Ryan J. Allen
QNX Software Systems
- Ryan J. Allen
Re: Broacom BCM4401-B0
Ryan,
Thanks...
I just installed that...
How do I setup QNX to use it?
When I did the install the networked never worked on this system.
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj6vqt$lun$1@inn.qnx.com...
Thanks...
I just installed that...
How do I setup QNX to use it?
When I did the install the networked never worked on this system.
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj6vqt$lun$1@inn.qnx.com...
On 05/12/2007 2:35 PM, Augie wrote:
Is there driver support for Broadcom BCM4401 (vendor id=14e4h, device
id=170ch) for RTOS?
devn-bcm43xx.so in patch 685 should support it.
--
Ryan J. Allen
QNX Software Systems
- Augie
Re: Broacom BCM4401-B0
On 05/12/2007 3:18 PM, Augie wrote:
It doesn't look like the patch updated the enumerators so you could
either start io-net with the driver yourself, mount the driver in after
io-net is running, or update the enumerators yourself.
--
Ryan J. Allen
QNX Software Systems
How do I setup QNX to use it?
It doesn't look like the patch updated the enumerators so you could
either start io-net with the driver yourself, mount the driver in after
io-net is running, or update the enumerators yourself.
--
Ryan J. Allen
QNX Software Systems
- Ryan J. Allen
Re: Broacom BCM4401-B0
On 05/12/2007 3:18 PM, Augie wrote:
It doesn't look like the patch updated the enumerators so you could
either start io-net with the driver yourself, mount the driver in after
io-net is running, or update the enumerators yourself.
--
Ryan J. Allen
QNX Software Systems
How do I setup QNX to use it?
It doesn't look like the patch updated the enumerators so you could
either start io-net with the driver yourself, mount the driver in after
io-net is running, or update the enumerators yourself.
--
Ryan J. Allen
QNX Software Systems
- Ryan J. Allen
Re: Broacom BCM4401-B0
Ryan,
I did..
slay io-net
io-net -d bcm43xx -p tcpip
Got no errors... but when I click on voyager it doesn't find www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj710v$mm6$1@inn.qnx.com...
I did..
slay io-net
io-net -d bcm43xx -p tcpip
Got no errors... but when I click on voyager it doesn't find www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj710v$mm6$1@inn.qnx.com...
On 05/12/2007 3:18 PM, Augie wrote:
How do I setup QNX to use it?
It doesn't look like the patch updated the enumerators so you could either
start io-net with the driver yourself, mount the driver in after io-net is
running, or update the enumerators yourself.
--
Ryan J. Allen
QNX Software Systems
- Augie
Re: Broacom BCM4401-B0
On 05/12/2007 3:41 PM, Augie wrote:
You'll have to set the IP and route with ifconfig and route, then add
dns to /etc/resolv.conf if you want to resolve names. If you have dhpc
on your network you can use dhcp.client to automatically get your
networking information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
Got no errors... but when I click on voyager it doesn't find www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
You'll have to set the IP and route with ifconfig and route, then add
dns to /etc/resolv.conf if you want to resolve names. If you have dhpc
on your network you can use dhcp.client to automatically get your
networking information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
- Ryan J. Allen
Re: Broacom BCM4401-B0
Ryan,
I tried ...
ifconfig en1 192.9.200.240 up
I got no such device or address
same result with
ifconfig en0 192.9.200.240 up
Are there commands different than QNX4?
Can I get a little help with the correct syntax for these?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj73ne$oir$1@inn.qnx.com...
I tried ...
ifconfig en1 192.9.200.240 up
I got no such device or address
same result with
ifconfig en0 192.9.200.240 up
Are there commands different than QNX4?
Can I get a little help with the correct syntax for these?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj73ne$oir$1@inn.qnx.com...
On 05/12/2007 3:41 PM, Augie wrote:
Got no errors... but when I click on voyager it doesn't find
www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
You'll have to set the IP and route with ifconfig and route, then add dns
to /etc/resolv.conf if you want to resolve names. If you have dhpc on
your network you can use dhcp.client to automatically get your networking
information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
- Augie
Re: Broacom BCM4401-B0
The 4401 is a Wi-Fi chip isn't it?
What does the output from "ifconfig" (no options) and "sloginfo" give you?
You also have to start the driver with the SSID and network key
specified in order to get the association with the access point set up
before you can add an IP address or expect DHCP to work...
"use devn-bcm43xx.so" gives you the options:
Syntax:
io-net -d bcm43xx [option[,option ...]] ... &
Options:
ssid=name 802.11 network name to use (ssid). Scans in bss
mode.
channel=num 802.11 channel to use. Scans in bss mode.
mode=mode 802.11 network mode: bss (access point), ibss (802.11
adhoc), or adhoc (802.11 adhoc). Default is bss
(access point).
station=name Station name for this machine. Defaults to
CS_HOSTNAME.
authtype=type Authentication scheme to use: open, sharedkey,
wpapsk or
wpa2psk. Default: open.
default_key=[1-4] Which of the keys given by key[1-4] to use for WEP.
key[1-4]=KEY Setup one of the 4 default WEP keys. Where KEY
is a hex
string of 10 (64/40bit WEP) or 26 (128bit WEP)
characters.
For example, key1=0x0102030405. Can also be
given as an
ascii string.
security=type Security type when not using WEP: tkip or aes
psk=shared key Pre-shared key. Must be between 8 and 64 ascii
characters.
ioport=port I/O port of the interface. Default: autodetect
irq=num IRQ of the interface. Default: autodetect
mac=XXXXXXXXXXXX MAC address of the controller. The default is
automatically detected on supported hardware.
verbose Be verbose.
pio Run driver in PIO mode. (default: bus master)
band=band Band to be used: auto, a or b. (Default auto)
Examples:
# Start io-net using this driver and the full TCP/IP stack:
io-net -d bcm43xx channel=10,ssid=work -p tcpip
ifconfig en0 10.184
# Start io-net using this driver and use 64bit WEP:
io-net -d bcm43xx
key1=0x0102030405,default_key=1,ssid=home,authtype=sharedkey
# Start io-net using this driver and WPAPSK with TKIP:
io-net -d bcm43xx
ssid=ssid_name,psk=shared_key,security=tkip,authtype=wpapsk
Robert.
Augie wrote:
What does the output from "ifconfig" (no options) and "sloginfo" give you?
You also have to start the driver with the SSID and network key
specified in order to get the association with the access point set up
before you can add an IP address or expect DHCP to work...
"use devn-bcm43xx.so" gives you the options:
Syntax:
io-net -d bcm43xx [option[,option ...]] ... &
Options:
ssid=name 802.11 network name to use (ssid). Scans in bss
mode.
channel=num 802.11 channel to use. Scans in bss mode.
mode=mode 802.11 network mode: bss (access point), ibss (802.11
adhoc), or adhoc (802.11 adhoc). Default is bss
(access point).
station=name Station name for this machine. Defaults to
CS_HOSTNAME.
authtype=type Authentication scheme to use: open, sharedkey,
wpapsk or
wpa2psk. Default: open.
default_key=[1-4] Which of the keys given by key[1-4] to use for WEP.
key[1-4]=KEY Setup one of the 4 default WEP keys. Where KEY
is a hex
string of 10 (64/40bit WEP) or 26 (128bit WEP)
characters.
For example, key1=0x0102030405. Can also be
given as an
ascii string.
security=type Security type when not using WEP: tkip or aes
psk=shared key Pre-shared key. Must be between 8 and 64 ascii
characters.
ioport=port I/O port of the interface. Default: autodetect
irq=num IRQ of the interface. Default: autodetect
mac=XXXXXXXXXXXX MAC address of the controller. The default is
automatically detected on supported hardware.
verbose Be verbose.
pio Run driver in PIO mode. (default: bus master)
band=band Band to be used: auto, a or b. (Default auto)
Examples:
# Start io-net using this driver and the full TCP/IP stack:
io-net -d bcm43xx channel=10,ssid=work -p tcpip
ifconfig en0 10.184
# Start io-net using this driver and use 64bit WEP:
io-net -d bcm43xx
key1=0x0102030405,default_key=1,ssid=home,authtype=sharedkey
# Start io-net using this driver and WPAPSK with TKIP:
io-net -d bcm43xx
ssid=ssid_name,psk=shared_key,security=tkip,authtype=wpapsk
Robert.
Augie wrote:
Ryan,
I tried ...
ifconfig en1 192.9.200.240 up
I got no such device or address
same result with
ifconfig en0 192.9.200.240 up
Are there commands different than QNX4?
Can I get a little help with the correct syntax for these?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj73ne$oir$1@inn.qnx.com...
On 05/12/2007 3:41 PM, Augie wrote:
Got no errors... but when I click on voyager it doesn't find
www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
You'll have to set the IP and route with ifconfig and route, then add dns
to /etc/resolv.conf if you want to resolve names. If you have dhpc on
your network you can use dhcp.client to automatically get your networking
information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
- Robert Craig
Re: Broacom BCM4401-B0
The 4401 is an ethernet chip and we don't have a driver for it.
"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:fj7ags$sf6$1@inn.qnx.com...
"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:fj7ags$sf6$1@inn.qnx.com...
The 4401 is a Wi-Fi chip isn't it?
What does the output from "ifconfig" (no options) and "sloginfo" give you?
You also have to start the driver with the SSID and network key specified
in order to get the association with the access point set up before you
can add an IP address or expect DHCP to work...
"use devn-bcm43xx.so" gives you the options:
Syntax:
io-net -d bcm43xx [option[,option ...]] ... &
Options:
ssid=name 802.11 network name to use (ssid). Scans in bss
mode.
channel=num 802.11 channel to use. Scans in bss mode.
mode=mode 802.11 network mode: bss (access point), ibss
(802.11
adhoc), or adhoc (802.11 adhoc). Default is bss
(access point).
station=name Station name for this machine. Defaults to
CS_HOSTNAME.
authtype=type Authentication scheme to use: open, sharedkey,
wpapsk or
wpa2psk. Default: open.
default_key=[1-4] Which of the keys given by key[1-4] to use for WEP.
key[1-4]=KEY Setup one of the 4 default WEP keys. Where KEY is a
hex
string of 10 (64/40bit WEP) or 26 (128bit WEP)
characters.
For example, key1=0x0102030405. Can also be given
as an
ascii string.
security=type Security type when not using WEP: tkip or aes
psk=shared key Pre-shared key. Must be between 8 and 64 ascii
characters.
ioport=port I/O port of the interface. Default: autodetect
irq=num IRQ of the interface. Default: autodetect
mac=XXXXXXXXXXXX MAC address of the controller. The default is
automatically detected on supported hardware.
verbose Be verbose.
pio Run driver in PIO mode. (default: bus master)
band=band Band to be used: auto, a or b. (Default auto)
Examples:
# Start io-net using this driver and the full TCP/IP stack:
io-net -d bcm43xx channel=10,ssid=work -p tcpip
ifconfig en0 10.184
# Start io-net using this driver and use 64bit WEP:
io-net -d bcm43xx
key1=0x0102030405,default_key=1,ssid=home,authtype=sharedkey
# Start io-net using this driver and WPAPSK with TKIP:
io-net -d bcm43xx
ssid=ssid_name,psk=shared_key,security=tkip,authtype=wpapsk
Robert.
Augie wrote:
Ryan,
I tried ...
ifconfig en1 192.9.200.240 up
I got no such device or address
same result with
ifconfig en0 192.9.200.240 up
Are there commands different than QNX4?
Can I get a little help with the correct syntax for these?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj73ne$oir$1@inn.qnx.com...
On 05/12/2007 3:41 PM, Augie wrote:
Got no errors... but when I click on voyager it doesn't find
www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
You'll have to set the IP and route with ifconfig and route, then add
dns to /etc/resolv.conf if you want to resolve names. If you have dhpc
on your network you can use dhcp.client to automatically get your
networking information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
- Hugh Brown
Re: Broacom BCM4401-B0
Yes, it is not a wireless board...
The driver doesn't work with this chip???
Any chance of upgrading the driver to support these? (There are a ton of
systems out there with this chip).
I also installed several Linux versions on this system and they all
supported it.
TIA
Augie
"Hugh Brown" <hsbrown@qnx.com> wrote in message
news:fj8u10$3bi$1@inn.qnx.com...
The driver doesn't work with this chip???
Any chance of upgrading the driver to support these? (There are a ton of
systems out there with this chip).
I also installed several Linux versions on this system and they all
supported it.
TIA
Augie
"Hugh Brown" <hsbrown@qnx.com> wrote in message
news:fj8u10$3bi$1@inn.qnx.com...
The 4401 is an ethernet chip and we don't have a driver for it.
"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:fj7ags$sf6$1@inn.qnx.com...
The 4401 is a Wi-Fi chip isn't it?
What does the output from "ifconfig" (no options) and "sloginfo" give
you?
You also have to start the driver with the SSID and network key specified
in order to get the association with the access point set up before you
can add an IP address or expect DHCP to work...
"use devn-bcm43xx.so" gives you the options:
Syntax:
io-net -d bcm43xx [option[,option ...]] ... &
Options:
ssid=name 802.11 network name to use (ssid). Scans in bss
mode.
channel=num 802.11 channel to use. Scans in bss mode.
mode=mode 802.11 network mode: bss (access point), ibss
(802.11
adhoc), or adhoc (802.11 adhoc). Default is bss
(access point).
station=name Station name for this machine. Defaults to
CS_HOSTNAME.
authtype=type Authentication scheme to use: open, sharedkey,
wpapsk or
wpa2psk. Default: open.
default_key=[1-4] Which of the keys given by key[1-4] to use for WEP.
key[1-4]=KEY Setup one of the 4 default WEP keys. Where KEY is
a hex
string of 10 (64/40bit WEP) or 26 (128bit WEP)
characters.
For example, key1=0x0102030405. Can also be given
as an
ascii string.
security=type Security type when not using WEP: tkip or aes
psk=shared key Pre-shared key. Must be between 8 and 64 ascii
characters.
ioport=port I/O port of the interface. Default: autodetect
irq=num IRQ of the interface. Default: autodetect
mac=XXXXXXXXXXXX MAC address of the controller. The default is
automatically detected on supported hardware.
verbose Be verbose.
pio Run driver in PIO mode. (default: bus master)
band=band Band to be used: auto, a or b. (Default auto)
Examples:
# Start io-net using this driver and the full TCP/IP stack:
io-net -d bcm43xx channel=10,ssid=work -p tcpip
ifconfig en0 10.184
# Start io-net using this driver and use 64bit WEP:
io-net -d bcm43xx
key1=0x0102030405,default_key=1,ssid=home,authtype=sharedkey
# Start io-net using this driver and WPAPSK with TKIP:
io-net -d bcm43xx
ssid=ssid_name,psk=shared_key,security=tkip,authtype=wpapsk
Robert.
Augie wrote:
Ryan,
I tried ...
ifconfig en1 192.9.200.240 up
I got no such device or address
same result with
ifconfig en0 192.9.200.240 up
Are there commands different than QNX4?
Can I get a little help with the correct syntax for these?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj73ne$oir$1@inn.qnx.com...
On 05/12/2007 3:41 PM, Augie wrote:
Got no errors... but when I click on voyager it doesn't find
www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
You'll have to set the IP and route with ifconfig and route, then add
dns to /etc/resolv.conf if you want to resolve names. If you have dhpc
on your network you can use dhcp.client to automatically get your
networking information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
- Augie
Re: Broacom BCM4401-B0
You will have to go through your sales rep if you want a driver for this
adapter.
"Augie" <augiehenriques@hotmail.com> wrote in message
news:fj8uvj$3pe$1@inn.qnx.com...
adapter.
"Augie" <augiehenriques@hotmail.com> wrote in message
news:fj8uvj$3pe$1@inn.qnx.com...
Yes, it is not a wireless board...
The driver doesn't work with this chip???
Any chance of upgrading the driver to support these? (There are a ton of
systems out there with this chip).
I also installed several Linux versions on this system and they all
supported it.
TIA
Augie
"Hugh Brown" <hsbrown@qnx.com> wrote in message
news:fj8u10$3bi$1@inn.qnx.com...
The 4401 is an ethernet chip and we don't have a driver for it.
"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:fj7ags$sf6$1@inn.qnx.com...
The 4401 is a Wi-Fi chip isn't it?
What does the output from "ifconfig" (no options) and "sloginfo" give
you?
You also have to start the driver with the SSID and network key
specified in order to get the association with the access point set up
before you can add an IP address or expect DHCP to work...
"use devn-bcm43xx.so" gives you the options:
Syntax:
io-net -d bcm43xx [option[,option ...]] ... &
Options:
ssid=name 802.11 network name to use (ssid). Scans in bss
mode.
channel=num 802.11 channel to use. Scans in bss mode.
mode=mode 802.11 network mode: bss (access point), ibss
(802.11
adhoc), or adhoc (802.11 adhoc). Default is bss
(access point).
station=name Station name for this machine. Defaults to
CS_HOSTNAME.
authtype=type Authentication scheme to use: open, sharedkey,
wpapsk or
wpa2psk. Default: open.
default_key=[1-4] Which of the keys given by key[1-4] to use for
WEP.
key[1-4]=KEY Setup one of the 4 default WEP keys. Where KEY is
a hex
string of 10 (64/40bit WEP) or 26 (128bit WEP)
characters.
For example, key1=0x0102030405. Can also be given
as an
ascii string.
security=type Security type when not using WEP: tkip or aes
psk=shared key Pre-shared key. Must be between 8 and 64 ascii
characters.
ioport=port I/O port of the interface. Default: autodetect
irq=num IRQ of the interface. Default: autodetect
mac=XXXXXXXXXXXX MAC address of the controller. The default is
automatically detected on supported hardware.
verbose Be verbose.
pio Run driver in PIO mode. (default: bus master)
band=band Band to be used: auto, a or b. (Default auto)
Examples:
# Start io-net using this driver and the full TCP/IP stack:
io-net -d bcm43xx channel=10,ssid=work -p tcpip
ifconfig en0 10.184
# Start io-net using this driver and use 64bit WEP:
io-net -d bcm43xx
key1=0x0102030405,default_key=1,ssid=home,authtype=sharedkey
# Start io-net using this driver and WPAPSK with TKIP:
io-net -d bcm43xx
ssid=ssid_name,psk=shared_key,security=tkip,authtype=wpapsk
Robert.
Augie wrote:
Ryan,
I tried ...
ifconfig en1 192.9.200.240 up
I got no such device or address
same result with
ifconfig en0 192.9.200.240 up
Are there commands different than QNX4?
Can I get a little help with the correct syntax for these?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj73ne$oir$1@inn.qnx.com...
On 05/12/2007 3:41 PM, Augie wrote:
Got no errors... but when I click on voyager it doesn't find
www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
You'll have to set the IP and route with ifconfig and route, then add
dns to /etc/resolv.conf if you want to resolve names. If you have
dhpc on your network you can use dhcp.client to automatically get your
networking information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
- Hugh Brown
Re: Broacom BCM4401-B0
Hugh,
Thanks.
I see the source code for the Network drivers is open source.
Is there a chance someone is working on this?
It might be possible for me to develop the driver for this card...
I'm sure it won't be a huge difference from the one supported...
Augie
"Hugh Brown" <hsbrown@qnx.com> wrote in message
news:fj9drc$e2f$1@inn.qnx.com...
Thanks.
I see the source code for the Network drivers is open source.
Is there a chance someone is working on this?
It might be possible for me to develop the driver for this card...
I'm sure it won't be a huge difference from the one supported...
Augie
"Hugh Brown" <hsbrown@qnx.com> wrote in message
news:fj9drc$e2f$1@inn.qnx.com...
You will have to go through your sales rep if you want a driver for this
adapter.
"Augie" <augiehenriques@hotmail.com> wrote in message
news:fj8uvj$3pe$1@inn.qnx.com...
Yes, it is not a wireless board...
The driver doesn't work with this chip???
Any chance of upgrading the driver to support these? (There are a ton of
systems out there with this chip).
I also installed several Linux versions on this system and they all
supported it.
TIA
Augie
"Hugh Brown" <hsbrown@qnx.com> wrote in message
news:fj8u10$3bi$1@inn.qnx.com...
The 4401 is an ethernet chip and we don't have a driver for it.
"Robert Craig" <rcraig_at_qnx@nowhere.com> wrote in message
news:fj7ags$sf6$1@inn.qnx.com...
The 4401 is a Wi-Fi chip isn't it?
What does the output from "ifconfig" (no options) and "sloginfo" give
you?
You also have to start the driver with the SSID and network key
specified in order to get the association with the access point set up
before you can add an IP address or expect DHCP to work...
"use devn-bcm43xx.so" gives you the options:
Syntax:
io-net -d bcm43xx [option[,option ...]] ... &
Options:
ssid=name 802.11 network name to use (ssid). Scans in bss
mode.
channel=num 802.11 channel to use. Scans in bss mode.
mode=mode 802.11 network mode: bss (access point), ibss
(802.11
adhoc), or adhoc (802.11 adhoc). Default is bss
(access point).
station=name Station name for this machine. Defaults to
CS_HOSTNAME.
authtype=type Authentication scheme to use: open, sharedkey,
wpapsk or
wpa2psk. Default: open.
default_key=[1-4] Which of the keys given by key[1-4] to use for
WEP.
key[1-4]=KEY Setup one of the 4 default WEP keys. Where KEY
is a hex
string of 10 (64/40bit WEP) or 26 (128bit WEP)
characters.
For example, key1=0x0102030405. Can also be
given as an
ascii string.
security=type Security type when not using WEP: tkip or aes
psk=shared key Pre-shared key. Must be between 8 and 64 ascii
characters.
ioport=port I/O port of the interface. Default: autodetect
irq=num IRQ of the interface. Default: autodetect
mac=XXXXXXXXXXXX MAC address of the controller. The default is
automatically detected on supported hardware.
verbose Be verbose.
pio Run driver in PIO mode. (default: bus master)
band=band Band to be used: auto, a or b. (Default auto)
Examples:
# Start io-net using this driver and the full TCP/IP stack:
io-net -d bcm43xx channel=10,ssid=work -p tcpip
ifconfig en0 10.184
# Start io-net using this driver and use 64bit WEP:
io-net -d bcm43xx
key1=0x0102030405,default_key=1,ssid=home,authtype=sharedkey
# Start io-net using this driver and WPAPSK with TKIP:
io-net -d bcm43xx
ssid=ssid_name,psk=shared_key,security=tkip,authtype=wpapsk
Robert.
Augie wrote:
Ryan,
I tried ...
ifconfig en1 192.9.200.240 up
I got no such device or address
same result with
ifconfig en0 192.9.200.240 up
Are there commands different than QNX4?
Can I get a little help with the correct syntax for these?
TIA
Augie
"Ryan J. Allen" <ryallen@qnx.com> wrote in message
news:fj73ne$oir$1@inn.qnx.com...
On 05/12/2007 3:41 PM, Augie wrote:
Got no errors... but when I click on voyager it doesn't find
www.qnx.com...
Any ideas?
How do I setup gateway... etc...?
You'll have to set the IP and route with ifconfig and route, then add
dns to /etc/resolv.conf if you want to resolve names. If you have
dhpc on your network you can use dhcp.client to automatically get
your networking information from the dhcp server.
--
Ryan J. Allen
QNX Software Systems
- Augie
Re: Broacom BCM4401-B0
Augie <augiehenriques@hotmail.com> wrote:
If you're refering to the networking project on Foundry27,
this source it to the next gen stack. The drivers therein
aren't compatible with io-net. However, you might be able
to port over the NetBSD bce driver to the new stack.
There's a technote on how to do this here.
http://community.qnx.com/integration/vi ... m=exsy1001
-seanb
Hugh,
Thanks.
I see the source code for the Network drivers is open source.
Is there a chance someone is working on this?
It might be possible for me to develop the driver for this card...
I'm sure it won't be a huge difference from the one supported...
If you're refering to the networking project on Foundry27,
this source it to the next gen stack. The drivers therein
aren't compatible with io-net. However, you might be able
to port over the NetBSD bce driver to the new stack.
There's a technote on how to do this here.
http://community.qnx.com/integration/vi ... m=exsy1001
-seanb
- seanb
- QNX Master
- Posts: 133
- Joined: Fri Jul 28, 2006 5:36 pm
Re: Broacom BCM4401-B0
Something wrong with that link?
"Sean Boudreau" <seanb@qnx.com> wrote in message
news:fjbjgt$6u$1@inn.qnx.com...
"Sean Boudreau" <seanb@qnx.com> wrote in message
news:fjbjgt$6u$1@inn.qnx.com...
Augie <augiehenriques@hotmail.com> wrote:
Hugh,
Thanks.
I see the source code for the Network drivers is open source.
Is there a chance someone is working on this?
It might be possible for me to develop the driver for this card...
I'm sure it won't be a huge difference from the one supported...
If you're refering to the networking project on Foundry27,
this source it to the next gen stack. The drivers therein
aren't compatible with io-net. However, you might be able
to port over the NetBSD bce driver to the new stack.
There's a technote on how to do this here.
http://community.qnx.com/integration/vi ... m=exsy1001
-seanb
- Augie
18 posts
• Page 1 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 1 guest