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.
Xiaodan Tang wrote:
Dave Edwards <> Dave.firstname.lastname@example.org> > wrote in message
news:> 3E2929A9.email@example.com> …
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.
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
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.
Dave Edwards <> Dave.firstname.lastname@example.org> > wrote:
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