Folks!
I have a network driver that registers itself as wlan0. I wish to use
some of the wireless extensions to the ifconfig command.
Does anyone have an idea on how I can register this interface so that
ifconfig will not report that it does not exist?
Nicinfo -r works however ifconfig wlan0 reports:
No such device or address
Thanks in advance
Dave
If it’s an ethernet driver, stick to “en”. If it’s not,
you’ll have to write a “wlan” to ip convertor.
-seanb
Dave Edwards <Dave.edwards@abicom-international.com> wrote:
Folks!
I have a network driver that registers itself as wlan0. I wish to use
some of the wireless extensions to the ifconfig command.Does anyone have an idea on how I can register this interface so that
ifconfig will not report that it does not exist?Nicinfo -r works however ifconfig wlan0 reports:
No such device or address
Thanks in advance
Dave
Hi Sean,
Unfortunatley I cannot use the en type at that point.
On another note, I’ve also notices that nic.h has a lot of wifi
definitions in it. What program/utility is intended to use these extensions?
Dave
Sean Boudreau wrote:
If it’s an ethernet driver, stick to “en”. If it’s not,
you’ll have to write a “wlan” to ip convertor.-seanb
Dave Edwards <> Dave.edwards@abicom-international.com> > wrote:
Folks!
I have a network driver that registers itself as wlan0. I wish to use
some of the wireless extensions to the ifconfig command.
Does anyone have an idea on how I can register this interface so that
ifconfig will not report that it does not exist?
Nicinfo -r works however ifconfig wlan0 reports:
No such device or address
Thanks in advance
Dave
Dave Edwards <Dave.edwards@abicom-international.com> wrote:
Hi Sean,
Unfortunatley I cannot use the en type at that point.
On another note, I’ve also notices that nic.h has a lot of wifi
definitions in it. What program/utility is intended to use these extensions?
It can be used by anyone. Our WIFI drivers (devn-prism, devn-orinoco) use
them for configuration purposes. The nicinfo utility will use a few of
them to gather information like ssid, channel, etc.
I am guessing your device pushes out full 802.11 frames? If so, you will
have to write your own filter layer that deals with the management frames
and then converts the data frames into en data for the upper parts of
the stack to manage.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Dave Edwards <Dave.edwards@abicom-international.com> wrote in message
news:3E2929A9.7020200@abicom-international.com…
Hi Sean,
Unfortunatley I cannot use the en type at that point.
You sort of miss the point.
It looks like your driver is regist with “up_type” to “wlan”.
This basiclly telling io-net that you will generate a “wlan”
packet and send up.
Since nobody (include the tcpip stack) understand what
is a “wlan” packet, your driver sort of setting their on its
own. Any packet it “tx_up()”, will got a return value of
0, means nobody will take that packet, and your driver
suppose to check this, and free it.
This is the reason that nicinfo will work (the /dev/io-net/wlan0
is created by io-net everytime someone do a regist). But
“netstat -ni” will see no “wlan0” interface.
As Sean suggest, either you have to regist with “up_type”
is “en”; (which of cause, the packet your driver tx_up()
must have a “ethernet packet frame” ) Or, if you can’t,
(say there is no such concept of “MAC address” in your
hardware), then the alternative is you have to regist another
“_REG_CONVERTOR” with up_type “ip” and bot_type
“wlan”. This converter will receive a “wlan” packet, and
turn it into an “ip” packet, and tx_up it.
-xtang
On another note, I’ve also notices that nic.h has a lot of wifi
definitions in it. What program/utility is intended to use these
extensions?Dave
Sean Boudreau wrote:
If it’s an ethernet driver, stick to “en”. If it’s not,
you’ll have to write a “wlan” to ip convertor.-seanb
Dave Edwards <> Dave.edwards@abicom-international.com> > wrote:
Folks!
I have a network driver that registers itself as wlan0. I wish to use
some of the wireless extensions to the ifconfig command.
Does anyone have an idea on how I can register this interface so that
ifconfig will not report that it does not exist?
Nicinfo -r works however ifconfig wlan0 reports:
No such device or address
Thanks in advance
Dave
I better add something to this,
Above my Wireless interface I have filtering and routing modules, these
then pass data according to the destination interface. On top of all
this I have a module that accepts packets from the “bridge” and
transfers them to a pseudo Ethernet driver.
Our approach is done this way for a number of reasons. Firstly we wanted
a single IP address for the device and not one per interface. Secondly,
since most of the traffic will not be destined for the unit, it makes
sense to effectivley filter it out, this is done by our bridge module
which sits under the pseudo ethernet device.
On the LAN side, we have a modified realtek driver that registers itself
as WAN0, this, like the WLAN is converted to a Bridge format. The bridge
module then determine where to send the packet.
Dave
Xiaodan Tang wrote:
Dave Edwards <> Dave.edwards@abicom-international.com> > wrote in message
news:> 3E2929A9.7020200@abicom-international.com> …Hi Sean,
Unfortunatley I cannot use the en type at that point.
You sort of miss the point.It looks like your driver is regist with “up_type” to “wlan”.
This basiclly telling io-net that you will generate a “wlan”
packet and send up.Since nobody (include the tcpip stack) understand what
is a “wlan” packet, your driver sort of setting their on its
own. Any packet it “tx_up()”, will got a return value of
0, means nobody will take that packet, and your driver
suppose to check this, and free it.This is the reason that nicinfo will work (the /dev/io-net/wlan0
is created by io-net everytime someone do a regist). But
“netstat -ni” will see no “wlan0” interface.As Sean suggest, either you have to regist with “up_type”
is “en”; (which of cause, the packet your driver tx_up()
must have a “ethernet packet frame” ) Or, if you can’t,
(say there is no such concept of “MAC address” in your
hardware), then the alternative is you have to regist another
“_REG_CONVERTOR” with up_type “ip” and bot_type
“wlan”. This converter will receive a “wlan” packet, and
turn it into an “ip” packet, and tx_up it.-xtang
On another note, I’ve also notices that nic.h has a lot of wifi
definitions in it. What program/utility is intended to use theseextensions?
Dave
Sean Boudreau wrote:If it’s an ethernet driver, stick to “en”. If it’s not,
you’ll have to write a “wlan” to ip convertor.-seanb
Dave Edwards <> Dave.edwards@abicom-international.com> > wrote:
Folks!
I have a network driver that registers itself as wlan0. I wish to use
some of the wireless extensions to the ifconfig command.
Does anyone have an idea on how I can register this interface so that
ifconfig will not report that it does not exist?
Nicinfo -r works however ifconfig wlan0 reports:
No such device or address
Thanks in advance
Dave
\
Chris,
We’ve written a HostAP driver for the prism chipset. This supports all
the features that are required by 802.11 in BSS mode. The device runs as
an AccessPoint and provides good throughput for our own and standard
802.11 clients (Better than 6Mbit/sec).
My questions are really about local IP performance and configuration
issues. I don’t really want to have to rewite work that has already been
done , so I just wanted to check what was available.
On a side note, you mentioned the PrismII driver. I’ve not seen it in
any recent distribution, what’s it’s current status?
Dave
Chris McKillop wrote:
Dave Edwards <> Dave.edwards@abicom-international.com> > wrote:
Hi Sean,
Unfortunatley I cannot use the en type at that point.
On another note, I’ve also notices that nic.h has a lot of wifi
definitions in it. What program/utility is intended to use these extensions?
It can be used by anyone. Our WIFI drivers (devn-prism, devn-orinoco) use
them for configuration purposes. The nicinfo utility will use a few of
them to gather information like ssid, channel, etc.I am guessing your device pushes out full 802.11 frames? If so, you will
have to write your own filter layer that deals with the management frames
and then converts the data frames into en data for the upper parts of
the stack to manage.chris
We’ve written a HostAP driver for the prism chipset. This supports all
the features that are required by 802.11 in BSS mode. The device runs as
an AccessPoint and provides good throughput for our own and standard
802.11 clients (Better than 6Mbit/sec).My questions are really about local IP performance and configuration
issues. I don’t really want to have to rewite work that has already been
done , so I just wanted to check what was available.On a side note, you mentioned the PrismII driver. I’ve not seen it in
any recent distribution, what’s it’s current status?
Excellent stuff! The devn-prism driver will make it’s first public
appearance in 6.2.1. It is purly a client driver and is 100% reliant on
the prism firmware and command-set to function. I assume you guys are putting
the prism into pass-thru mode?
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Hi Chris,
We’re using the HostAP mode of the chipset. This will pass most
information up the stack and then you have to do the 802.11 management
stuff. It’s fairly straightforward and works well with io-net’s
architecture.
On a performance note, what throughput can you achieve with the QNX
drivers? Most .11b stuff rarely performs better than 5Mbit/sec.
Dave
Excellent stuff! The devn-prism driver will make it’s first public
appearance in 6.2.1. It is purly a client driver and is 100% reliant on
the prism firmware and command-set to function. I assume you guys are putting
the prism into pass-thru mode?chris
On a performance note, what throughput can you achieve with the QNX
drivers? Most .11b stuff rarely performs better than 5Mbit/sec.
600-650Kbit/s best case. Although it really depends on the environment the
test is run in.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris,
Do you mean Kbit or Kbyte? I assume Kbyte, this would tally up with what
we’ve seen. Although the firmware version on the radio makes a big
difference, the later releases actually slow the device down.
Dave
Chris McKillop wrote:
On a performance note, what throughput can you achieve with the QNX
drivers? Most .11b stuff rarely performs better than 5Mbit/sec.
600-650Kbit/s best case. Although it really depends on the environment the
test is run in.chris
Dave Edwards <Dave.edwards@abicom-international.com> wrote:
Chris,
Do you mean Kbit or Kbyte? I assume Kbyte, this would tally up with what
we’ve seen. Although the firmware version on the radio makes a big
difference, the later releases actually slow the device down.
Yes, sorry. kbyte/s. 
I have also found that the orinoco’s just have
better radios all-around. Although the firmware isn’t as fast, it has
much better range.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/