RE: [Leaf-user] re: PCMCIA for 2.2.16
Hi Richard I have a version of the pcmcia from which works with my old Eiger kernel 2.2 (not Eigerstein if thats different) which works fine when I set it up correctly, only problem is the package does not have the pcnet_cs.o module . So if we can get a complete pcmcia compilation with all of the standard pcmcia drivers, it would help. Only problem I have at present is the time obtain the software and to setup a system and understand what I need to do to compile the kernel et al. Any help here would be useful. Peter -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Richard G. Minutillo Sent: 12 July 2001 15:50 To: Peter Stokes Cc: [EMAIL PROTECTED] Subject: Re: [Leaf-user] re: PCMCIA for 2.2.16 True, but is the wireless option even turned on in the Eiger kernel? Maybe, because I do recall some other emails about getting wireless to work with LRP. Maybe a search of the archives? I think it was an Orinoco success story... Richard Peter Stokes wrote: Hi Thanks to Richard for the PCMCIA link which works great with my IBM PCCard, but there was no wvlan_cs.o in the tarball. Anyone know how to email Bill Dudley, I could not find an email on the site. Thanks Peter ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] EigerStein DMZ v1.1 Proxy ARP installation
If I follow you correctly, you are looking to put the old machines in the DMZ (on eth2), in order to preserve their current IP addresses. I am running a Proxy ARP setup using the Eigerstein2Beta distro, with modified scripts from the LRP-CD distro (the only one advertised to work with Proxy ARP). I am not aware of a complete distro for this setup --- if there was one, I wouldn't have needed to build my by hand. In any event, I don't believe you have much to worry about when it comes to masquerading on eth2. There is a dab masq functionality for UDP services built into the DMZ scripts, but that is easy enough to disable, as Charles spelled out here: http://www.geocrawler.com/archives/3/7325/2001/6/350/5991180/ Scroll thru that message, to the part that starts I think I know hy because he _did_ :) That will turn off the udp masq leaving you with a DMZ that is controlled by only the settings in your DMZ_OPEN_DEST section. FWIW, I was a rank noob to not only LRP, but *nix in general when I undertook this, and an *I* got it working without /subjective=on too much /subjective=off trouble. :) Good luck, Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lonnie Cumberland Sent: Thursday, July 12, 2001 10:39 AM To: [EMAIL PROTECTED] Subject: [Leaf-user] EigerStein DMZ v1.1 Proxy ARP installation Hello All, I have been looking at the EigerStein DMZ v1.1 Proxy ARP installation and am trying to find a completed distrabution that does not have the masqurading ethernet 2 card stuff in the scripts. does anyone have a complete distribution that I could get with just the DMZ Proxy-ARP or some information on where to locate the scripts that I need. I am currently using the static version of the Eigersten LRP which has masqurading and works very well along with being very easy to install. I now have a need for the Proxy-ARP version because I will be installing an LRP that will allow the existing computers to keep there OLD static IP's Any ideas would be helpful? Thanks again, Lonnie -- Lonnie Cumberland OutStep Technologies Incorporated TEL:(313) 832-7366 FAX:(313) 832-7366 URL: http://www.outstep.com EMAIL: [EMAIL PROTECTED] : [EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] re: PCMCIA for 2.2.16
My bad. The orinoco_cs driver has not been back ported to the 2.2.x kernel yet. I've downloaded the PCMCIA Card Services tarball. I will compile it against 2.2.19 for you. But I have no way to test it. (No pcmcia or Wavelan/Orinico radios) It will take some time as my development system is slow. At 09:15 AM 07/12/2001 -0700, Mike Sensney wrote At 02:43 PM 07/12/2001 +0100, Peter Stokes wrote: Hi Thanks to Richard for the PCMCIA link which works great with my IBM PCCard, but there was no wvlan_cs.o in the tarball. Anyone know how to email Bill Dudley, I could not find an email on the site. It looks like the whole site is his. Check out http://www.casano.com The link at the bottom of the page is mailto:[EMAIL PROTECTED] According to Jean Tourrilhes, the wvlan_cs driver has been superceded by the orinoco_cs driver. http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan-IEEE.html Here is info on the new driver. http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Orinoco.html
RE: [Leaf-user] re: PCMCIA for 2.2.16
Hi Mike Just thought I would point out that Bill has put the wireless drivers onto his site now. So I thought I could save you some work in the short term. It would be good to get a version for the latest and greatest at some stage however as Bill has no longer monitoring LRP and his versions will not be changing in the medium term it appears. Peter -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Sensney Sent: 12 July 2001 18:10 To: [EMAIL PROTECTED] Subject: RE: [Leaf-user] re: PCMCIA for 2.2.16 My bad. The orinoco_cs driver has not been back ported to the 2.2.x kernel yet. I've downloaded the PCMCIA Card Services tarball. I will compile it against 2.2.19 for you. But I have no way to test it. (No pcmcia or Wavelan/Orinico radios) It will take some time as my development system is slow. At 09:15 AM 07/12/2001 -0700, Mike Sensney wrote At 02:43 PM 07/12/2001 +0100, Peter Stokes wrote: Hi Thanks to Richard for the PCMCIA link which works great with my IBM PCCard, but there was no wvlan_cs.o in the tarball. Anyone know how to email Bill Dudley, I could not find an email on the site. It looks like the whole site is his. Check out http://www.casano.com The link at the bottom of the page is mailto:[EMAIL PROTECTED] According to Jean Tourrilhes, the wvlan_cs driver has been superceded by the orinoco_cs driver. http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan-IEEE.html Here is info on the new driver. http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Orinoco.html ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Eiger2beta 4 w/PPPoP DNS script change error
I updated my /etc/ipfilter.conf file for the DNS flood script protection as
follows:
# Added by Charles Steinkuehler to allow more flexible internal server setup
# A function to configure the filters for firewalling
ipfilter_firewall_cfg () {
local ADDR
local DEST
local NET
#
# set default policies
#
# ONLY DENY FORWARDING ETC IF YOU KNOW WHAT YOU ARE DOING! If
# you turn off the filters, the box will become opaque to any traffic!
#
ipfilter_policy DENY
# Clear any garbage rules out of the filters
ipfilter_flush
# Block known IPs who do TCP port 53 floods
# Added to block list of IPs on 7/7/01
IP_LIST=`cat /etc/dns_floods`
for IP in $IP_LIST; do
$IPCH -I input -j DENY -p tcp -s $IP/32 -d $EXTERN_IP/32 53 -i
$EXTERN_IF
done; unset IP
I have the dns_flood file built. After I edited the ipfilter.conf file and
dns_flood file, I saved the files, went to the # promp and issued
amberton: -root-
# svi network ipfilter flush
then
amberton: -root-
# svi network ipfilter reload
The script runs and blocks those DNS floods in my log file. I then backed up
everything on the lrp and was fine. 5 days later I had to reboot and the
script did not block the DNS flood. I had to issue the flush and reload
command for it to block the floods.
Is this correct or should this load on boot?
___
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] RE: [Leaf-user] EigerStein DMZ v1.1 Proxy ARP installation
Just comment out the interfaces you don't need in /etc/network.conf and make this right # Interfaces to start on boot go here - ie ppp0 eth0 IF_AUTO=eth0 eth1 Quote from Charles about Extended Scripts V1.1: DMZ_SWITCH=YES is for a conventional routed OR static NAT DMZ DMZ_SWITCH=PRIVATE is for port-forwarded DMZ's. Lonnie Cumberland wrote: Hi There, Actually I was also interested in only needing 2 ethernet cards as the scripts that I have seen seem to need 3. I also wanted to not use masqurading on the 192.168.x.x at all and just be allowed to let let my machines behind the firewall keep their existing static IP's but still be behind the firewall. I will look over the information that you have sent me. Thanks again, Lonnie If I follow you correctly, you are looking to put the old machines in the DMZ (on eth2), in order to preserve their current IP addresses. I am running a Proxy ARP setup using the Eigerstein2Beta distro, with modified scripts from the LRP-CD distro (the only one advertised to work with Proxy ARP). I am not aware of a complete distro for this setup --- if there was one, I wouldn't have needed to build my by hand. In any event, I don't believe you have much to worry about when it comes to masquerading on eth2. There is a dab masq functionality for UDP services built into the DMZ scripts, but that is easy enough to disable, as Charles spelled out here: http://www.geocrawler.com/archives/3/7325/2001/6/350/5991180/ Scroll thru that message, to the part that starts I think I know hy because he _did_ :) That will turn off the udp masq leaving you with a DMZ that is controlled by only the settings in your DMZ_OPEN_DEST section. FWIW, I was a rank noob to not only LRP, but *nix in general when I undertook this, and an *I* got it working without /subjective=on too much /subjective=off trouble. :) Good luck, Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lonnie Cumberland Sent: Thursday, July 12, 2001 10:39 AM To: [EMAIL PROTECTED] Subject: [Leaf-user] EigerStein DMZ v1.1 Proxy ARP installation Hello All, I have been looking at the EigerStein DMZ v1.1 Proxy ARP installation and am trying to find a completed distrabution that does not have the masqurading ethernet 2 card stuff in the scripts. does anyone have a complete distribution that I could get with just the DMZ Proxy-ARP or some information on where to locate the scripts that I need. I am currently using the static version of the Eigersten LRP which has masqurading and works very well along with being very easy to install. I now have a need for the Proxy-ARP version because I will be installing an LRP that will allow the existing computers to keep there OLD static IP's Any ideas would be helpful? Thanks again, Lonnie -- Lonnie Cumberland OutStep Technologies Incorporated ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] EigerStein DMZ v1.1 Proxy ARP installation
Actually I was also interested in only needing 2 ethernet cards as the scripts that I have seen seem to need 3. If all you want is the Proxy-arp DMZ, just ignore the internal network interface. Of course, if you only have 2 NIC's installed, you'll have to change a few things (DMZ is setup for eth2 by default, which you don't have). Off the top of my head: Swap instances of eth1 eth2 in network.conf (ie internal network=eth2, DMZ network=eth1) Remove eth2 from the IF_AUTO list, so the scripts don't try to automatically configure it Everything *should* work... Of course, you'll have some firewall rules masquerading your (non-existant) internal network on eth2 to the internet, but the rules don't hurt anything (except burning a few CPU cycles, which you should have pleanty of, even with a 486). Holler if you run into trouble with the above changes, or still have problems once you've altered the DMZ for eth1. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] How to compile source into LRP?
Lance Peterson wrote: I tried to add the full blown tar utility to LRP by compiling the source on the LRP machine but I received the following error: ./configure: permission denied. Not sure why you would need GNU tar, but anyway Likely that means it's not an executable file, or you don't have permissions to run it. I used Putty pscp to copy all the source files over from Windows to the LRP machine with the -r and -p flags set to maintain sub directories and file permissions. The copy seems to have worked fine. What permissions? UNIX has rwxrwxrwx plus some others; DOS has almost none of these. Where would execuable permissions come from (DOS has none). Best to go get that *.tar.gz file and unpack it under UNIX; *.tar.gz preserves permissons. I am logged in as root. Am I limited to adding only xxx.lrp modules??? I'm not sure what you mean by this. Logged in where? *.lrp files are not modules and modules are not *.lrp files... modules are located in /lib/modules and are *.o files. *.lrp files are binary packages precompiled for LRP. ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Re: [Leaf-user] EigerStein DMZ v1.1 Proxy ARP installation
Thanks everyone for the help and I will start trying to get things set up with all of this great information. The only last thing is that my current LRP installations are the Eigerstein-Static versions that I have placed onto a small hard disk on to the router so that I do not have to boot from a floppy. Which version do I need to get that contains these scripts? Is this the Eigetstein Beta or the CDROM version that I have heard about? In any case, I want to also have it boot off of the small MSDOS hard disk just like my old faithful masquarading firewall does so I presume that I do not need any special re-compiled version, or do I? Thanks for the help all, Lonnie Actually I was also interested in only needing 2 ethernet cards as the scripts that I have seen seem to need 3. If all you want is the Proxy-arp DMZ, just ignore the internal network interface. Of course, if you only have 2 NIC's installed, you'll have to change a few things (DMZ is setup for eth2 by default, which you don't have). Off the top of my head: Swap instances of eth1 eth2 in network.conf (ie internal network=eth2, DMZ network=eth1) Remove eth2 from the IF_AUTO list, so the scripts don't try to automatically configure it Everything *should* work... Of course, you'll have some firewall rules masquerading your (non-existant) internal network on eth2 to the internet, but the rules don't hurt anything (except burning a few CPU cycles, which you should have pleanty of, even with a 486). Holler if you run into trouble with the above changes, or still have problems once you've altered the DMZ for eth1. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user -- Lonnie Cumberland President/CEO OutStep Technologies Incorporated TEL:(313) 832-7366 FAX:(313) 832-7366 URL: http://www.outstep.com EMAIL: [EMAIL PROTECTED] : [EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] lrpstat with eiger2beta
hello all... i have been trying to get all the packages working before i burn a cd image... and i was trying to setup the lrpStat on Eiger2Beta...after i install this then i can go to the Netmon.html on the lrp server and it loads up correctly but there is never any databeing displayed... maybe i have somesettings like the ownership of the files wrong.i dont know buti followed these directions for setting it up: http://nw-hoosier.dyndns.org/rlohman/linux/eiger-cfg-lrpstat.html the only thing that i added to this "howto" was to add this to the host.allow file: "ALL: 192.168.1.0/255.255.255.0" does anyone know what i have done wrong? does anyone have this working on eiger2beta (i am sure someone does)? thanks for any help. [EMAIL PROTECTED]
[Leaf-user] Network Card Problem (Module SIS900.o )!?
Dear all expert, I have purchased a new motherboard with on-board NIC but can't load the module when using the LRP. I have found the source code on the vendor web pages, (i.e. http://www.sis.com.tw/support/download/linux.htm) but I don't know how to comply to get the required module. I have found one module on some web pages but it is not up-to-dated. Please give some suggestions !? Best Regards, Eddy. ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] lrpstat with eiger2beta
Hi, M8d wrote: i have been trying to get all the packages working before i burn a cd image... and i was trying to setup the lrpStat on Eiger2Beta... after i install this then i can go to the Netmon.html on the lrp server and it loads up correctly but there is never any data being displayed... maybe i have some settings like the ownership of the files wrong.i dont know but i followed these directions for setting it up: http://nw-hoosier.dyndns.org/rlohman/linux/eiger-cfg-lrpstat.html First of all, you should probably go to http://lrp.hejl.de or http://leaf.sf.net/devel/hejl and get the current version of lrpStat (0.10Beta), if you didn't upgrade already. Version 0.6 that's on the page you mentioned is rather old. Then, the howto fails to mention that you should probably do a chmod 755 /sbin/stat.sh (or at least check to see if the file has the executable bit set). If you didn't reboot somewhere along the way, you'll need to send a SIGHUP to inetd after you changed /etc/inetd.conf. I'm not quite sure what has to be done to ensure that the change in the hosts.allow file will take effect - the sure way would be to reboot at the end of the whole setting up process. (Everybody: what has to be done to activate changes in /etc/hosts.allow without needing to reboot?). You also failed to mention if you modified the Netmon.html file to match your network devices (even though that shouldn't cause what you describe, at least eth0 should display some data). If that doesn't help, please try the suggestions mentioned on http://leaf.sf.net/devel/hejl/troubleshooting.html especially connecting to port 60183 using telnet to see if any data is gathered and sent to the client at all. I hope that helps. Don't hesitate to contact me directly if lrpStat doesn't work, preferably with the information stated on the troubleshooting page mentioned above. Martin ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Network Card Problem (Module SIS900.o )!?
Well...You can upgrade to 2.2.19 Ewald Wasscher has a new kernel and modules ready for download. Including the sis900.o module. http://leaf.sourceforge.net/devel/ewaldw/kernel/2.2.19-1-LRP/ You will have to replace both kernel and modules on your LEAF disk. Choose an appropriate kernel for your usage and rename it linux. (If you guess wrong, choose another. :) At 12:58 PM 07/13/2001 +0800, Eddy Wong wrote Dear all expert, I have purchased a new motherboard with on-board NIC but can't load the module when using the LRP. I have found the source code on the vendor web pages, (i.e. http://www.sis.com.tw/support/download/linux.htm) but I don't know how to comply to get the required module. I have found one module on some web pages but it is not up-to-dated. Please give some suggestions !? Best Regards, Eddy. ___ Leaf-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/leaf-user --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.264 / Virus Database: 136 - Release Date: 07/02/2001
