Samuel, Last time I checked the Soekris boxes werre using National Semiconductor for the Ethernet. You will need the natsemi.o module.
Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brock Nanson Sent: Friday, July 05, 2002 12:30 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [leaf-user] RE: Problem to get wisp working! > Date: Thu, 04 Jul 2002 19:23:51 -0300 > From: Samuel Abreu de Paula <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [leaf-user] RE: Problem to get wisp working! > > Ok, it's /dev/sda1 here, cos i use a CF Reader(USB) to access > the CF! For linux, the CF it's a emul like a scsi device! so > the /dev/sda is my > CF in Linux! > > Thankz... but i did the Wisp boot in my aaeon! > The CF has to be CHS, not LBA, the format of the first > partition must be > FAT16 < 32mb (in my case), and i use the newer version of syslinux! > > =) > > Now, one more question, wisp use IPTABLES??? in a iptables -L > show none > rules! Samuel, Let me preface this by saying you are now further along with wisp than I am. After successfully booting it I spent literally 2 minutes poking around the menus before pulling the plug until I can get access to an AP for real testing. So in the absence of any other replies I'll try my best. By the way, I'm glad to hear that wisp has joined sourceforge... I had wondered initially why it wasn't there (here)! Wisp is based on Bering if I understand correctly. I think you can access the 'old' bering menus from the new main menu. I would (because I use bering) tend to work from there. I don't recall seeing shorewall in the package, so I don't know what sort of firewalling is in effect. My impression was that there was no firewall capabilities as distributed. I don't know if that means it runs with iptables or ipchains... If you don't get an error with that command, I would assume iptables are supported, but that no rules have been created (?). I would be curious to know if shorewall could just 'drop in' to wisp and if so, why it isn't there already (unless I just missed it). In another message you ask about 'Hermes' assigned as a nickname. I think that is set in wireless.opts which should be found through the bering menu (pcmcia). If the wireless tools are present, iwconfig could be used at the command prompt to change this temporarily. See the link to the man page on Jacques Nilo's sourceforge site. As for the onboard NIC in the soekris SBC, you will need the matching module for the chipset. Again this would likely be done by adding the correct module(s) to /lib/modules and the corresponding entry(s) in /etc/modules. If you haven't already experimented with Bering, I'd suggest you start there and get a feel for how it works before adding the complexity of wisp. My brief encounter with wisp suggested some significant additions to bering! Brock ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Bringing you mounds of caffeinated joy. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
