-rw-r--r-- | noncore/settings/networksettings/TODO | 13 |
1 files changed, 1 insertions, 12 deletions
diff --git a/noncore/settings/networksettings/TODO b/noncore/settings/networksettings/TODO index 9bde0dd..2130184 100644 --- a/noncore/settings/networksettings/TODO +++ b/noncore/settings/networksettings/TODO @@ -10,47 +10,36 @@ Types: -IPChains? When entering the wep keys, I think we should be able to see what we are typing, but not to show the keys when the field is not in focus. Otherwise, it's real hard to know if you typed the right wep key, and you have to look in the actual wireless.opts file to really know if you did it right. When Zaurus is in cradle, USB interface is connected and reported as UP by the Network Setting application, clicking on Information button does not popup a window. It used to work before, but now it's broken in the latest feed... --30-second pause closing NetSetting's Configure screen - --Default Network Type for 802.11b should be Infrastructure - --After configuring NetworkSettings for the first time, the WEP key fails to -be iwconfig'd to the eth0 interface (Symbol 802.11b card on my Z). - -Z hangs on PCMCIA-eject of Symbol 802.11b card (card seems to be in an odd state after first boot following reflash; see Additional Info) test WEP Add WEP transimtion rate 1 or 2 5.5 1 Auto -udchcp needs to output the dhcp information so interfaces can read it +udhcpc needs to output the dhcp information so interfaces can read it interfacesetupimp really doesn't need a interface* pointer PPP module needs to scan pppd.tdb to see what is currently active WLAN - add possiblity to input text or hex without knowing "s:" - Handle "any" and any the same way in config -Interface setupimp needs to use kernel calls. - Add a route/DNS editor under the ViewAdvancedInfo button Use a true TCP/IP widget -Make it so that pcmcia doesn't need to be stopped/started for wlan - Automaticly update the main list of interfaces: > That would be me. :-D netlink, can you point me in the right > direction where I can get more info on it? (I figured there was some > kenel call) You can look up the meaning of the packets you receive, or you can just go |