It's difficult to know when the madwifi drivers are not associated. This
throws everything off when troubleshooting. The only way to know whether
the radio is associated with an access point is to run the debugging tools
to find out what state the driver is in. This creates a lot of debugging
information and is generally messy. In addition not everyone knows how to
turn on the debugging tools. This information is also difficult to parse
during boot time and there needs to be a better way to determine that the
card is associated with an access point. In addition no debugging
information is generated if the code which prints debug statements is not
executed. This makes it difficult for network boot scripts to know when to
do certain things.
For example when the DHCP client tries to access the network but the card is
not associated it will fail. This leaves the user in a state where he
doesn't know why the network connection failed. In addition, the fact that
DHCP tries to connect when the card is not associated signals a problem with
the programming. This problem arose because of the history of networking.
Ethernet did not associate and did not need a check like this.
Is there a current solution to this?
If not: How do I propose this to the right person? Anyone interested in
funding me to fix this problem?
Software Engineer and Systems Administrator
Get latest updates about Open Source Projects, Conferences and News.