[Leaf-user] Configuring the DMZ machine
Hello, I have an LRP set-up running Eigerstein with both a private network and a DMZ network. The DMZ is using the default private IP addresses (the DMZ machine is at 192.168.2.1). It was all working swell until today when I decided to move from Redhat 5.2 to 7.2. I backed everything that mattered up, but neglected to write down my Network configuration details. It took a lot of futzing around the first time to get it working and I haven't found any reference to what the Gateway, DNS, and netmask should be set to on the DMZ server. Please help. Thanks. Allen Harris ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] using the e3 editor in Oxygen
David- I actually don't have enough experience with *nix text editors to have a preference. When I started up Oxygen for the first time it went through a script, part of which asked me to choose which editor I wanted to use. I chose e3 not out of any personal preference but because it was first in the list. I've been reading this mailing list for over a year so I know that e3 can be configured to emulate many popular text editors but since I specified e3 when Oxygen asked me which I wanted to use I assumed I would be using 'generic' e3. Due to my lack of experience, when it came time to edit files I couldn't figure out how to work the editor, so I went looking for the e3 man page. When commands suggested in the e3 man page didn't work I became confused and produced the first post in this thread. Helpful posts from helpful list members helped me to realize that e3 was emulating vi. Once I figured that out I was fine. I am now able to edit anything on the system that needs editing. Again, I don't have a personal preference when it comes to *nix text editors. As long as I can get an editor to save my changes I'm happy. If you as the developer are curious as to why e3 in my copy of Oxygen defaults to vi emulation when e3 is specified in the initial boot sequence I'd be glad to report on the various settings in various configuration files, but otherwise I'm happy with it as it is. I'm not writing the Great American Novel here, just editing a few scripts :) with the ultimate goal of establishing an Oxygen- based FTP server. Thanks for your help and for a great product. Brent Gardner [EMAIL PROTECTED] wrote: > "Brent P. Gardner" wrote: > > > Thanks Steve, Charles, and Patrick for your suggestions. It turns > > out that e3 was in vi mode as suggested below. This confuses me > > because both e3 and vi are in the list of options displayed when > > Oxygen asks which editor you would like to use. Since I specified > > e3 I didn't think to try vi commands. > > Sounded like you wanted WordStar commands - if you use e3ws, or > change E3EM to the appropriate value in .profile, then it should > work. > > Did you do that? Is it working for you now? > > ___ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf- user > > ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Simple, per client, machine access rules?
Mark Plowman wrote: > I know that the simplicity of setup and maintenance will be a > significant factor in the decisions about this project, together with > the fact that client would prefer it all to cost *nothing* - the > reason my boss quickly queried what LEAF could do ;-) Well, I'm not sure how simple this would be, but you could use arping to find out the IP address of a given MAC address and then let the scripts configure based on this computed IP address. This would require several things: 1. the RIGHT arping binary :-) 2. programming the system so the firewall rules self-check over time - or just reconfigure periodically to generate the appropriate rules if an IP changes. Perhaps just a wrapper script would be enough, in a cron job - checking IP addresses and creating a new firewall configuration The first is easy. If you grabbed arping off of your nearest Linux box, it's almost certainly wrong :-) If you get output like: # arping -h arping: invalid option -- h Usage: arping [-fDUAV] [-c count] [-w timeout] [-I device] [-s source] destination -f : quit on first reply -D : duplicate address detection mode -U : Unsolicited ARP mode, update your neighbours -A : ARP answer mode, update your neighbours -V : print version and exit -c count : how many packets to send -w timeout : how long to wait for a reply -I device : which ethernet device to use (eth0) -s source : source ip address destination : ask for what ip address ...that's the wrong one. If you get output like: # arping -h arping 1.01 [ -qvrRd0bp ] [ -S ] [ -T ] [ -t ] [ -c ] [ -i ] ...this is the right one. Given a MAC address, this program let's me "ping" it and gives me an IP besides: # arping 172.16.3.31 ARPING 172.16.3.31 60 bytes from 00:60:b0:4b:d3:c0 (172.16.3.31): index=0 60 bytes from 00:60:b0:4b:d3:c0 (172.16.3.31): index=1 60 bytes from 00:60:b0:4b:d3:c0 (172.16.3.31): index=2 60 bytes from 00:60:b0:4b:d3:c0 (172.16.3.31): index=3 --- 172.16.3.31 statistics --- 4 packets transmitted, 4 packets received, 0% unanswered # arping 00:60:b0:4b:d3:c0 ARPING 00:60:b0:4b:d3:c0 60 bytes from 172.16.3.31 (00:60:b0:4b:d3:c0): icmp_seq=0 60 bytes from 172.16.3.31 (00:60:b0:4b:d3:c0): icmp_seq=1 60 bytes from 172.16.3.31 (00:60:b0:4b:d3:c0): icmp_seq=2 60 bytes from 172.16.3.31 (00:60:b0:4b:d3:c0): icmp_seq=3 60 bytes from 172.16.3.31 (00:60:b0:4b:d3:c0): icmp_seq=4 --- 00:60:b0:4b:d3:c0 statistics --- 5 packets transmitted, 5 packets received, 0% unanswered # Will this help you? Or perhaps someone else? There IS an arping.lrp available at http://leaf.sourceforge.net/pub/oxygen/packages/arping.lrp I believe. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein-CD RC4: loading modules
Hi I use the rtl8139 module also for my nics. It requires pci-scan to load first. Also you can check to see if your cd-rom is being recognized in all of that text that scrolls by as you start up. Use page-up to see what just went by. My modules.conf looks like this: # PCI ethernet cards pci-scan rtl8139 Hope this helps, Robert Williams # PCI ethernet cards >I think I missed something in the module loading process. I get everything >loading in the boot process and its missing loading the modules for the >network cards. I am sure its in the module file in \etc but I don't know if >I am doing this correctly. > >I am booting from the floppy to load the CD. I have no HDD so the CD player >is ' /hda '. I am sure this is pretty obvious but I am only used to doing >dual floppies. All my Nics are PCI or integrated and I have been using the >dual floppy version for almost a year. > >anyone got a clue train ticket to sell me? Why its not loading the modules? > > >thanks >Alec > >### > ! mount iso9660 /dev/hda > ># You can directly reference modules, like this: >#/scsi/aic7xxx >#/fs/ext2 > ># Or change the default directory, like this: >! dir /lib/modules/net > ># PCI ethernet cards >#3c59x >rtl8139 >3c509 > >.. > >!umount > > > >___ >Leaf-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein-CD RC4: loading modules
I think I missed something in the module loading process. I get everything loading in the boot process and its missing loading the modules for the network cards. I am sure its in the module file in \etc but I don't know if I am doing this correctly. I am booting from the floppy to load the CD. I have no HDD so the CD player is ' /hda '. I am sure this is pretty obvious but I am only used to doing dual floppies. All my Nics are PCI or integrated and I have been using the dual floppy version for almost a year. anyone got a clue train ticket to sell me? Why its not loading the modules? thanks Alec ### ! mount iso9660 /dev/hda # You can directly reference modules, like this: #/scsi/aic7xxx #/fs/ext2 # Or change the default directory, like this: ! dir /lib/modules/net # PCI ethernet cards #3c59x rtl8139 3c509 .. !umount ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] host ignores redirect ???
Michael D. Schleif wrote: > I've found references to this issue in the archives; but, have not found > adequate explanation nor resolution. > > host 0a02a8c0/if8 ignores redirects for 0a02a8c0 to 0a02a8c0. > > Yes, the ip address is 192.168.2.10; but, *what* is it trying to > redirect? *Why* is it trying to redirect _whatever_ to itself? > > What does this really mean? I believe I know what this is - some one can straighten me out if not. This would be an ICMP REDIRECT packet coming from your router telling the LEAF system to use THIS machine instead of THAT one as the gateway - and the LEAF system is telling you it isn't listening to that other router. However, this seems rather unusual, in that this messages I would think normally would contain three IP addresses, not the one you show here. This should be: host /if8 ignores redirects for to or something like that. If I read this right, the system is sending a packet to itself telling itself to redirect its own default gateway to itself. That sounds almost like a routing problem... ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] using the e3 editor in Oxygen
"Brent P. Gardner" wrote: > Thanks Steve, Charles, and Patrick for your suggestions. It turns out > that e3 was in vi mode as suggested below. This confuses me because > both e3 and vi are in the list of options displayed when Oxygen asks > which editor you would like to use. Since I specified e3 I didn't think > to try vi commands. Sounded like you wanted WordStar commands - if you use e3ws, or change E3EM to the appropriate value in .profile, then it should work. Did you do that? Is it working for you now? ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] VPN 2.2.19 Kernal patch
I am running Dachstien. I would like to know where I can get the 2.2.19-2-LRP-VPNMasq-Floppy-zImage. I got VPN masq working on eigerstienbeta2 by simply renaming the file 2.2.16-1-LRP-VPNMasq-Floppy-zImage to LINUX and copying it over the Linux file on my floppy. Is there a Floppy-zImage file out there for dachstien? I do not have access to a Linux box so I can’t patch the kernel. Also, Is there a kernel for Dachstien with both vpn and multicasting? I am aware that my questions are rather simple. I hope someone out there can e-mail me and help me out. Thanks in advance. Troy.
Re: [Leaf-user] using the e3 editor in Oxygen
"Brent P. Gardner" wrote: > It turns out > that e3 was in vi mode as suggested below. This confuses me because > both e3 and vi are in the list of options displayed when Oxygen asks > which editor you would like to use. Since I specified e3 I didn't think > to try vi commands. The reason for this is that I wanted Oxygen to provide a UNIX-like environment, and virtually every UNIX system ever made comes with vi. Also, in the selection process, if you load all of the added add-on packages, one can choose from emacs (zile), vi (elvis-tiny), pico (nano), and perhaps even THE (a VMS VDT clone). Also, I wanted to allow a user to specify they wanted vi or emacs or whatever and e3 should be set up to act that way. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] compiling for LRP.
Jeff Newmiller wrote: > There are compatibility development packages for RedHat that allow you to > compile for glibc2.0, but in many cases it is not quite so simple. One > reason is that the makefiles or configure scripts provided to prepare the > makefiles require some amount hand-editing to get them to work in a > compatibility mode. Depending on your familiarity with the dependencies > in the source you are compiling, this may be possible but can be far from > trivial in the general case. Unless the source is particularly simple, > the easiest solution is to use a Debian Slink installation for > development, as long as your source code doesn't depend on glibc features > added after glibc2.0. You can also use Red Hat 5.2 or Mandrake 5.3 to do the same thing. However, using the compatability packages for Red Hat requires Red Hat 6.x or equivalent, since they weren't released for Red Hat 7.x - I don't know how they'd be under Red Hat 7. Compiling is usually not so bad unless the program makes extensive use of networking or a few other functions. Many things will compile just fine, including networking applications. Using the glibc compatability libraries is the only way I've done most of my package development, since Red Hat 5 is hopelessly out of date (as is everything which uses glibc 2.0). If you use a shell wrapper script, you can override the C compiler used by the Makefiles (and by autoconfigure) which allows you to compile for glibc 2.0. In fact, many programs will compile without any editing if they don't use any glibc 2.1 specific features, and if you set the CC variable to make and use the -e option - or set CC and run autoconfigure. More extensive details can be found in the LRP Developer's Guide on the LEAF site at http://leaf.sourceforge.net/ ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein-CD RC4: POSIXness.mail caution
Charles Steinkuehler wrote:
>
> > One caution: I found several places where lines could be compressed
> > using redirects instead of pipes for the mail body:
> >
> > {
> > cool stuff
> > } | mail -s "$subject" $mailto
> >
> > Beware -- this no longer works !!!
>
> What breaks? This should work...if it doesn't, it's a bug.
Yesterday was a tough day all around for me ;<
First, there was the client from h*ll and his neverending problems that
couldn't wait for a weekday.
Then, I struggled with sshd in RC4.
And, last evening, when I cam home, I had ~300 mail processes *stuck* in
the process table, including that many /proc//fd's.
When I tried manually running:
/usr/local/bin/mailonerr moe.config
I got my ubiquitous ``broken pipe'' error -- not once; but, three times
in a row.
Once I changed this, in mailonerr:
} | mail -s "$subject" $mailto # my edit
to this:
} > $prefix.msg
mail -s "$subject" $mailto < $prefix.msg
Everything started working again, after mass-killing those hung
processes.
Therefore, I concluded that the pipe was the source to my problems.
Today, I test the pipe (|) and it works -- go figure ;>
OK, Charles, again, I am wrong and stand corrected . . .
--
Best Regards,
mds
mds resource
888.250.3987
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . .
___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [leaf-user] Floppy 2 HD
Hi, Thanks Patrick & Jeff for your replies, but after doing some fiddling with a different floppy drive and a different cable I got the floppy working again. Don't have to the hazzling with the HD :) Thanks anyway. Regards, Joris ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein-CD RC4: POSIXness.mail caution
> One caution: I found several places where lines could be compressed
> using redirects instead of pipes for the mail body:
>
> {
> cool stuff
> } | mail -s "$subject" $mailto
>
> Beware -- this no longer works !!!
What breaks? This should work...if it doesn't, it's a bug.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
___
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [leaf-user] Floppy 2 HD
On Mon, 12 Nov 2001, Mart Kempen wrote: > Hi, > > I have a working floppy image by now :) > > But the computer where I want to run Dachstein on has a broken floppy > controller, and can't fix this. I find this hard to believe. A FDC is not more expensive than a NIC, and you need two of those. > But I still have a 1 gb HD laying around with W95 installed on it. > > I assume that ny router can also be run from a HD. > > How do I get my floppy on the HD. > > How to format it, under Linux or under W95. How to copy the files on it. So many options, each with assumptions... I think the new floppy drive will be much easier on your brain. IF the HD was native to that box, and included two network cards, OR you have a CD drive and the W95 cd and can configure the NICs to play nice, OR you have a bootable CD drive and a bootable Linux cd, THEN you MIGHT be able to install LOADLIN and transfer the diskette files over the network onto the HD and configure LOADLIN to start from the AUTOEXEC.BAT file. The Linux cd approach would require more than minimal Linux knowledge. I think having Win95 know about and be happy with the two NICs may not be needed, but having to remove one of them from your machine every time you try to bypass LOADLIN may be a hassle. I think your HD would need to be formatted with FAT16 (almost certainly the case... you would need W95OSR2 otherwise, and for that size HD it would make little sense to use FAT32). You don't say if the box uses ISA or PCI NICs. Each has quirks... the former usually need configuration programs that are usually available on the net, the latter sometimes need you to go into the BIOS and tweak settings or have the NICs placed in specific slots. You may need to replace the "linux" file from your floppy with a version that supports IDE... if so, you will need to replace the modules in your modules.lrp file also. (SYSLINUX.DPY, LDLINUX.SYS and SYSLINUX.CFG are not needed if you use LOADLIN, but it won't hurt if you forget to remove them.) See http://www.linuxdoc.org/HOWTO/mini/Loadlin+Win95-98-ME.html and http://c0wz.steinkuehler.net/dox/loadlin_howto.txt. http://leaf.sourceforge.net/devel/cstein/Documentation/LRPHardDiskHOWTO.txt has a lot of useful information, but it assumes you have a working FDC, so I don't think you can use syslinux. > Any help would be appreciated. > > Please keep in mind that my Linux knowledge is absolutely minimal LRP is a good tool for correcting that... it is a small system, so it has relatively few configuration points, yet you can still use Windows to get it up and going. However, getting things onto hard disks is easiest with a floppy drive. --- Jeff NewmillerThe . . Go Live... DCN:<[EMAIL PROTECTED]>Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [leaf-user] Floppy 2 HD
Mart Kempen wrote: > > Hi, > > I have a working floppy image by now :) > > But the computer where I want to run Dachstein on has a broken floppy > controller, and can't fix this. > > But I still have a 1 gb HD laying around with W95 installed on it. > > I assume that ny router can also be run from a HD. > > How do I get my floppy on the HD. > > How to format it, under Linux or under W95. How to copy the files on it. > > Any help would be appreciated. > > Please keep in mind that my Linux knowledge is absolutely minimal > > Thanks and regards, > > Joris Please keep in mind that your Linux knowledge will certainly increase dramatically after reading this!. :-) http://leaf.sourceforge.net/devel/cstein/Documentation/LRPHardDiskHOWTO.txt Keep an eye on the WARNING message about installing it on a hard disk.. -- Patrick Benson Stockholm, Sweden ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[leaf-user] Floppy 2 HD
Hi, I have a working floppy image by now :) But the computer where I want to run Dachstein on has a broken floppy controller, and can't fix this. But I still have a 1 gb HD laying around with W95 installed on it. I assume that ny router can also be run from a HD. How do I get my floppy on the HD. How to format it, under Linux or under W95. How to copy the files on it. Any help would be appreciated. Please keep in mind that my Linux knowledge is absolutely minimal Thanks and regards, Joris ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Cipe Vpn for eiger
> That could be the problem I guess I am running a 2.16 kernel from > harddisk well basicly a Disk On Chip that doesn't need an extra > driver and is > recognized as /dev/hda It seems that you're running an IDE enabled Kernel. We had the same problem after I realeased a CIPE LRP package for 2.2.19 Kernels. A lot of people are running IDE Kernels and some of them asked the list why these segfaults happened. We have two possiblities now: 1. You migrate to a 2.2.19 Kernel and use my IDE CIPE for 2.2.19 2. I download a 2.2.16 kernel tree and compile it for your current kernel Please let me know which one you prefer (I would prefer the first one ;), but don't be shy to ask for the second) Sandro > Kim > ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] LEAF shell scripting novice resources
Julian Church wrote: > Thanks for that - it does look useful. They've got a book there about bash > - is that the one I want? I haven't read it but most of their books are highly recommended, since they usually are useful for beginners -> experts as well as excellent reference material at the same time. If you look at the symlinks in /bin you will notice something, though: # ls -l -rwxr-xr-x 1 root root93340 Nov 1 17:13 ash lrwxrwxrwx 1 root root3 Nov 12 09:29 bash -> ash lrwxrwxrwx 1 root root3 Nov 12 09:29 sh -> ash They point to the ash shell. Ash is usually used for simplicity and it doesn't need that much space. It's used on the installation disks with Slackware, for example, whereas bash is usually used with the common distributions after a complete installation, since it has more advanced options and won't complain about space on a hard disk. http://leaf.sourceforge.net/devel/cstein/Documentation/ash.html It's good to read up on both, ash and bash, and since you mention it I think I will, too. I'm, by no means, a shell expert! :-) -- Patrick Benson Stockholm, Sweden ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] LEAF shell scripting novice resources
At 22:43 09/11/01 +0100, Patrick Benson wrote: >Julian Church wrote: > > > 1. What is the LEAF (I generally use Eigerstein) shell script language > > called - is it just "sh"? > > 2. Can anyone recommend resources to get me started? Online resources are > > good, textbooks are better, and I find I tend to get on with O'Reilly books > > quite well. > >http://linux.oreilly.com/ > >Lots of resources there. Thanks for that - it does look useful. They've got a book there about bash - is that the one I want? >-- >Patrick Benson >Stockholm, Sweden > >___ >Leaf-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/leaf-user -- [EMAIL PROTECTED] www.ljchurch.co.uk ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
