This is to help track and resolve bugs with the DebianLinuxAccessPoint and DebianApImage projects. If you think you've found a bug in how the image works please list it here along with all the information I might need to fix it. Thanks -- AdamShand.
Feature Requests
ExtrusionDetection (Snort)
Automatic rules update for ExtrusionDetection
- Test traffic shaping, investigate inbound traffic shaping
Test NoCatAuth CaptivePortal mode
- Setup Exim with TLS for mail proxying (warn about earthlink)
- Setup transparent proxy for port 80 and port 25
- Add the debian package for Wavemon (new in unstable)
- Install Bastille for security (maybe gr-security as well?)
- Install tripwire or osiris
- Is webmin a good idea?
- Add CBQ (debian package shaper)
ssl support on nocat auth page -EricJohanson
Touch screen support.
Can this be done without X? non-X-scribble? - Real time reporting...
- setting up image to work with other devices (EG: SBCs with different PCMCIA bridges)
Setting up a default message on telnet/ssh; "you are not logged in via nocat, please goto http://aa.bb.cc.dd/"
- ADHoc mode! This would be VERY helpful for SWN folks..... I've heard rumors that we want to use ADHoc for PtP links...
Open Bugs
From TerrySchmidt:
- Screen doesn't turn off (might be my bios settings)
- How do you make grub bootable? (without loading lilo first and then booting and choosing grub)
working on it, if anyone else wants to figure this out it would be appreciated. -- AdamShand
From EricJohanson:
- /etc/lilo.conf.install does not point to correct kernel image; (both 2.2.x and 2.4.x)
- warnings loading modules; /var/log/something is readonly on kernel boot
- My screen *does* turn off, once I tweaked the bios
- Why can't I ping/traceroute out via the NAT?
- having lynx installed would help debugging 'net connections
- What does this mean? Any why is it saying it sooooo much?
[[[ Jan 5 05:02:44 fuji kernel: Clearing TIM bit for AID 1 Jan 5 05:02:45 fuji kernel: wlan0: dropped received packet from 00:02:2d:04:e4:62 with no ToDS flag (type=0x02, subtype=0x04) Jan 5 05:02:45 fuji kernel: wlan0: RX status=0x0000 (port=0, type=0, fcserr=0) silence=4 signal=153 rate=20 rxflow=0 Jan 5 05:02:45 fuji kernel: FC type=2:4 dur=0x0102 seq=0xe1f0 data_len=0 Jan 5 05:02:45 fuji kernel: A1=00:30:ab:0e:fa:af A2=00:02:2d:04:e4:62 A3=00:30:ab:0e:fa:af A4=00:00:00:00:00:00 Jan 5 05:02:45 fuji kernel: dst=00:30:ab:0e:fa:af src=00:02:2d:04:e4:62 len=0 Jan 5 05:02:45 fuji kernel: handle_pspoll: BSSID=00:30:ab:0e:fa:af, TA=00:02:2d:04:e4:62 Jan 5 05:02:45 fuji kernel: aid=1 Jan 5 05:02:45 fuji kernel: Clearing TIM bit for AID 1 Jan 5 05:02:46 fuji kernel: wlan0: dropped received packet from 00:02:2d:04:e4:62 with no ToDS flag (type=0x02, subtype=0x04) Jan 5 05:02:46 fuji kernel: wlan0: RX status=0x0000 (port=0, type=0, fcserr=0) silence=3 signal=153 rate=20 rxflow=0 Jan 5 05:02:46 fuji kernel: FC type=2:4 dur=0x0102 seq=0xe2c0 data_len=0 Jan 5 05:02:46 fuji kernel: A1=00:30:ab:0e:fa:af A2=00:02:2d:04:e4:62 A3=00:30:ab:0e:fa:af A4=fc:f0:75:98:b3:f0 Jan 5 05:02:46 fuji kernel: dst=00:30:ab:0e:fa:af src=00:02:2d:04:e4:62 len=0 Jan 5 05:02:46 fuji kernel: handle_pspoll: BSSID=00:30:ab:0e:fa:af, TA=00:02:2d:04:e4:62 Jan 5 05:02:46 fuji kernel: aid=1 Jan 5 05:02:46 fuji kernel: Clearing TIM bit for AID 1 Jan 5 05:02:47 fuji kernel: wlan0: dropped received packet from 00:02:2d:04:e4:62 with no ToDS flag (type=0x02, subtype=0x04) Jan 5 05:02:47 fuji kernel: wlan0: RX status=0x0000 (port=0, type=0, fcserr=0) silence=4 signal=150 rate=20 rxflow=0 Jan 5 05:02:47 fuji kernel: FC type=2:4 dur=0x0102 seq=0xe390 data_len=0 Jan 5 05:02:47 fuji kernel: A1=00:30:ab:0e:fa:af A2=00:02:2d:04:e4:62 A3=00:30:ab:0e:fa:af A4=03:0a:00:10:00:80 Jan 5 05:02:47 fuji kernel: dst=00:30:ab:0e:fa:af src=00:02:2d:04:e4:62 len=0 Jan 5 05:02:47 fuji kernel: handle_pspoll: BSSID=00:30:ab:0e:fa:af, TA=00:02:2d:04:e4:62 Jan 5 05:02:47 fuji kernel: aid=1 Jan 5 05:02:47 fuji kernel: Clearing TIM bit for AID 1 ]]] I get 1-2 of these per second. /var/log on my system is over 300 megs. 
Unable to Duplicate
- DNS Server doesn't load upon bootup
- DHCP Server doesn't load upon bootup
Resolved Bugs
- Needs update to 2.4.16 (10 Dec 2001)
- Disable -- MARK -- in syslog ("-m 0") (10 Dec 2001)
- Add simple batch file or configuration to switch to bridging instead of NAT (see /usr/local/bin/bridge-setup.sh 10 Dec 2001)