[Leaf-user] Bering Firewall without NAT
Hi, I was wondering if anyone had any idea about using Bering/Shorewall without using Masqurading or NAT. We are at a University so we already have all the machines on our network assigned to "real" addresses. I dont really want to change all of them to private addresses but I am having problems in configuring Bering Shorewall to do this. Currently we have a gateway 134.36.22.1 and our main switch connects to that and its all very straight forward. Our plan was to add the firewall between the gateway and the switch i.e. Gateway Firewall ExtFirewall IntSwitch Hosts 134.36.22.1 134.36.22.2 134.36.22.5 * 134.36.22.??? gw=134.36.22.1gw=134.36.22.5 We also need to enable access to our webserver for ssh, www and ftp access. I was planning on doing this either via a separate zone/hosts or via rule exceptions in Shorewall. I have a pair of machines that I have connected to the firewall so I can try things but the only way I have go anything to work was adding static routes on the firewall and even then I couldnt get very far as I was still running NAT. My test setup worked well with NAT using private addresses. Bering was straightforward to setup in this case. (Kudos to the authors) Unfortunately I suspect my knowledge of TCP/IP has sort of run its course at this point and I am a bit stuck for what to try next. I was considering trying to chuck out the NAT kernel modules and set it up as a bridge but the example configuration also used NAT Cheers, Jonathan -- Dr Jonathan Monk, Dundee Satellite Receiving Station University of Dundee, Dundee, DD1 4HN tel: 44 (0)1382 344409 fax: 44 (0)1382 345415 e-mail [EMAIL PROTECTED] http://www.sat.dundee.ac.uk ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card
Hi, I've successfully managed to configure a bering floppy to use my pppoe connection ( chapeau les mecs ! ! ) Now, I'm trying to configure the wireless adapter but I'm "lost" My firewall machine IS NOT a laptop. The Intel PRO/Wireless is in a PCI adapter. tcic.o, yenta_socket, i82092, i82365 modules with no success Should I realy use the PCMCIA stuff or is there other modules to use ??? Regards, Etienne - Original Message - From: "Jacques Nilo" <[EMAIL PROTECTED]> To: "Lee" <[EMAIL PROTECTED]>; "Etienne Charlier" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, March 21, 2002 10:21 PM Subject: Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card > > > I have a dachstein cd-based router running very well. ( P133 desktop PC) > > > I'm connected to the Internet through ADSL/PPPOE > > > I just got a pair of Pcmcia Intel PRO/Wireless2021 cards and a PCI > > adapter. > > > > > > I would like to put the PCMCIA card with adapter in the Dachstein box to > > be > > > able to surf from my laptop. > > > > > > is there some howto somewhere. I only found doc about true laptop/pcmcia > > > stuff but nothing concerning the PCI adapter. > > > > Etienne: > There is pcmcia documentation available for Bering in our new user's guide. It > might help to setup pcmcia/wireless in Dachstein > http://leaf.sourceforge.net/devel/jnilo/busers02.html > Wireless is working too with the wireless tools available as a separate > package. Documentation not ready yet. > > Jacques > > > ___ > 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] Help on initrd patch to autoload minix
> I've tried rebuilding my DS kernel in an attempt to add some more > features. My problem is that the standard 2.2.19 source trees .config > listing does not include the following lines: > > CONFIG_BLOCK_DEV_INITRD_ARCHIVE=y > CONFIG_BLOCK_DEV_INITRD_ARCHIVE_AUTOFS_MINIX=y > > I tried scouring the net for the initrd source patches created by Dave > Cinege way back but wasn't able to find one. Can anyone show me links on > where to get, and how to apply these patches on a 2.2.19 source tree? I > already checked out Dave's ftp psychosis site, but there isn't much you > can do when logged as anonymous. Everything you need is at the link below, including kernel patches, a script to apply them, kernel configuration files, &c: http://lrp.steinkuehler.net/files/kernels/Dachstein-source/ See the README file for details: http://lrp.steinkuehler.net/files/kernels/Dachstein-source/README 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] libz on Dach-CD
> I certainly have to defer to Charles and Michael - but if you want an > example, here's how I did it, based on Charles instructions in the > Dachstein CD notes. Feedback or suggestions for improvement of my setup > are welcome! > > I have an ancient 486DX with a mere 16Mb of ram for my firewall, boot off a > floppy, then read the CDROM for modules. > > I added the floppy drive to the PKGPATH in "syslinux.cfg" on the boot > floppy, and libz.lrp to "lrpkg.cfg" as well, with the search order R > (reverse search of PKGPATH, stop on first match). > > Here's the content of the files: > > # mount -t msdos /dev/fd0u1680 /mnt > mount: /dev/fd0u1680 is write-protected, mounting read-only > > firewall: -root- > # cat /mnt/syslinux.cfg > display syslinux.dpy > timeout 0 > default linux append=load_ramdisk=1 initrd=root.lrp initrd_archive=minix > ramdisk_size=12288 root=/dev/ram0 boot=/dev/fd0u1680,msdos > PKGPATH=/dev/cdrom:iso9660,/dev/fd0u1680:msdos > LRP=etc,ramlog,local,modules,dhclient,dhcpd,dnscache,weblet > > firewall: -root- > # cat /mnt/lrpkg.cfg > etc,ramlog,local,modules,dhclient,dhcpd,dnscache,weblet,ifconfig,mawk,ipsec, sshd,libz:R,tcpdump > > On boot, only the libz.lrp from the floppy is loaded. Now, if I can just > figure out what kind of memory to put in this ancient box, I'll get enough > to load bash... Looks good, except for the floppy disk in PKGPATH, which should be unnecessary. I think if you trim PKGPATH to simply "PKGPATH=/dev/cdrom:iso9660", everything will continue to work properly. As it stands now, you're probably loading the floppy contents twice... Using the :R switch for libz is a good idea. As long as you've got the *ENTIRE* package (and not just configuration data) on the floppy, this is probably the best way to implement an upgrade. If you simply have two libz packages (one on the CD, and one on the floppy), and don't use the :R option, the CD-ROM libz is loaded first, then the floppy libz is loaded on top of that. While this shouldn't normally cause any problems (things would only get wierd if the CD-ROM package contained files not present in the floppy version, which wouldn't be deleted, and would likely wind up "orphened", becomming part of the root package), it's cleaner to use the :R switch, and avoid loading the CD-ROM version of the package entirely. 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] Help on initrd patch to autoload minix
Hi, I wondered if there are available any patches for the 2.4 kernel ? Charles Steinkuehler wrote: >>I've tried rebuilding my DS kernel in an attempt to add some more >>features. My problem is that the standard 2.2.19 source trees .config >>listing does not include the following lines: >> >>CONFIG_BLOCK_DEV_INITRD_ARCHIVE=y >>CONFIG_BLOCK_DEV_INITRD_ARCHIVE_AUTOFS_MINIX=y >> >>I tried scouring the net for the initrd source patches created by Dave >>Cinege way back but wasn't able to find one. Can anyone show me links on >>where to get, and how to apply these patches on a 2.2.19 source tree? I >>already checked out Dave's ftp psychosis site, but there isn't much you >>can do when logged as anonymous. >> > > Everything you need is at the link below, including kernel patches, a script > to apply them, kernel configuration files, &c: > http://lrp.steinkuehler.net/files/kernels/Dachstein-source/ > > See the README file for details: > http://lrp.steinkuehler.net/files/kernels/Dachstein-source/README > > 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 > > ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Eigerstein with 2 internal Networks.
Hello I'm using Eigerstein for my internet access, VPN and Port forwarding. I am masquerading my current network. I now have a need to masquerade another internal subnet. Here is the setup. Internet | Eigerstein | 192.168.0 network | Multihomed NT server Routing between networks | 172.16 network I would like to masquerade the 172.16 network. (give them internet access) Is this possible with Eigerstein? Thanks, Joe ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Help on initrd patch to autoload minix
> I wondered if there are available any patches for the 2.4 kernel ? There are some patches for early versions of the 2.4 kernel, but most current work is aimed at eliminating the need for the kernel patches in the first place. 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] Bering Firewall without NAT
- Original Message - From: "Jonathan Monk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 1:43 AM Subject: [Leaf-user] Bering Firewall without NAT > Hi, > > I was wondering if anyone had any idea about using Bering/Shorewall without > using Masqurading or NAT. We are at a University so we already have all the > machines on our network assigned to "real" addresses. I dont really want to > change all of them to private addresses but I am having problems in > configuring Bering Shorewall to do this. Install the Shorewall.lrp from the Shorewall site (URL below) -- the one in Bering comes with training wheels attached and hides all of the power and flexibility of Shorewall. You'll have to learn how to configure Shorewall without the training wheels but the Shorewall documentation (again available at the URL below) should be more than enough to let you do that. -Tom -- Tom Eastep\ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ [EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Eigerstein with 2 internal Networks.
> I'm using Eigerstein for my internet access, VPN and Port forwarding. I am > masquerading my current network. I now have a need to masquerade another > internal subnet. > > Here is the setup. > >Internet >| > Eigerstein >| > 192.168.0 network >| > Multihomed NT server >Routing between networks >| > 172.16 network > > I would like to masquerade the 172.16 network. (give them internet access) > Is this possible with Eigerstein? Yes. You need to make two changes to /etc/network.conf (both assume Dachstein network scripts...I don't recall off-hand if these features were implemented in Eiger): 1) Add a static route to the 172 network so your firewall can talk to it. Assuming your internal network interface on the Eiger box is eth1: eth1_ROUTES="172.16.0.0/24_via_192.168.0.111" Obviously, modify the network specification (172.16.0.0/24) and IP of your multi-homed NT system (192.168.0.111) as required for your network (you didn't provide specifics, so I made some up :) 2) Add the new network to INTERN_NET: INTERN_NET="192.168.0.0/24 172.16.0.0/24" Again, change the 172 network specification as required for your setup. I doubt both of these parameters are supported by EigerStein. You could upgrade your network scripts, but I'd suggest upgrading to Dachstein. 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] Bering Firewall without NAT
I had to do something similar recently, and I'm still amazed at how uncommon it seems to be -- there are not many examples around. I can't speak to Bering-specific configurations, as I have only used Shorewall on Red Hat and SuSE "minimal" installations, but I assume it is Shorewall that will take the lead in your scenario. The secret for Shorewall is the proxyarp file, since Proxy-arp must be used to do what you are looking to do. Getting the proxyarp file configured can be a bit time-consuming, as it must explicitly list each IP address for which it will proxy, plus a few other configuration parameters. To assist with this task, I created a short Perl script, that you can find here: http://www.optimumnetworks.com/PAconfig . A few other tips: 1. Assign an RFC1918 address to your internal interface, like 192.168.0.1 2. Create a host route to your default gateway, specifying the external NIC by device name, i.e.: route add -host DefGWIP dev ethX. Create the "init" file per Shorewall docs, and put your route command there. 3. Create host routes for any host NOT behind your firewall, but in the same network space as the external interface -- via the external interface. Since you are using legal addresses, your configs need to expressly indicate "these hosts are on THAT side of eth1, those hosts are on THAT side of eth0." 4. Control arp caches --- the single most blindingly frustrating hair-pulling make-you-think-you've-gone-insane part of Proxy-arp. If you can flush a device with a command, do it; if not power cycle any arp-caching devices (bridges/swithes/routers) within your control --- or be prepared to wait an undefined amount of time before all entries expire in the arp caches you can't control. ISP's upstream router on bridged DSL comes to mind... This is the part that really complicates troubleshooting, since you ALWAYS want your system up NOW, when you've rolled the dice by taking an entire subnet down. If you have a smaller piece of the network you can isolate as a test "zone," it will give you more breathing room to get comfortable with your configs, and the behavior of Proxy-arp. Resist the temptation to go back and make guesses in your configs --- since you are more likely to move from the right answer to the wrong one, due to a stuck arp entry "somewhere." 5. See http://www.optimumnetworks.com/proxyarp.txt for an example of a real Shorewall proxyarp config file. Notice I generated the entire /25 subnet, then commented out special-purpose addresses near the bottom. 6. All other Shorewall configs are standard. Good luck! Dan Optimum Networks, Inc. www.optimumnetworks.com - Original Message - From: "Jonathan Monk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 3:43 AM Subject: [Leaf-user] Bering Firewall without NAT > Hi, > > I was wondering if anyone had any idea about using Bering/Shorewall without > using Masqurading or NAT. We are at a University so we already have all the > machines on our network assigned to "real" addresses. I dont really want to > change all of them to private addresses but I am having problems in > configuring Bering Shorewall to do this. > > Currently we have a gateway 134.36.22.1 and our main switch connects to that > and its all very straight forward. Our plan was to add the firewall between > the gateway and the switch i.e. > > Gateway Firewall Ext Firewall Int Switch Hosts > 134.36.22.1 134.36.22.2 134.36.22.5 * 134.36.22.??? > gw=134.36.22.1 gw=134.36.22.5 > > We also need to enable access to our webserver for ssh, www and ftp access. I > was planning on doing this either via a separate zone/hosts or via rule > exceptions in Shorewall. > > I have a pair of machines that I have connected to the firewall so I can try > things but the only way I have go anything to work was adding static routes > on the firewall and even then I couldnt get very far as I was still running > NAT. > > My test setup worked well with NAT using private addresses. Bering was > straightforward to setup in this case. (Kudos to the authors) > Unfortunately I suspect my knowledge of TCP/IP has sort of run its course at > this point and I am a bit stuck for what to try next. I was considering > trying to chuck out the NAT kernel modules and set it up as a bridge but the > example configuration also used NAT > > Cheers, > > Jonathan > > -- > Dr Jonathan Monk, Dundee Satellite Receiving Station > University of Dundee, Dundee, DD1 4HN > tel: 44 (0)1382 344409 fax: 44 (0)1382 345415 > e-mail [EMAIL PROTECTED] http://www.sat.dundee.ac.uk > > > ___ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > - Original Message - From: "Jonathan Monk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 3:43 AM Subject: [Leaf-user] Bering Firewall without NAT > Hi, > > I was wondering if anyone had any idea abo
Re: [Leaf-user] Bering Firewall without NAT
- Original Message - From: "dgilleece" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 6:34 AM Subject: Re: [Leaf-user] Bering Firewall without NAT > I had to do something similar recently, and I'm still amazed at how uncommon > it seems to be -- there are not many examples around. > > I can't speak to Bering-specific configurations, as I have only used > Shorewall on Red Hat and SuSE "minimal" installations, but I assume it is > Shorewall that will take the lead in your scenario. > > The secret for Shorewall is the proxyarp file, since Proxy-arp must be used > to do what you are looking to do. Getting the proxyarp file configured can > be a bit time-consuming, as it must explicitly list each IP address for > which it will proxy, plus a few other configuration parameters. To assist > with this task, I created a short Perl script, that you can find here: > http://www.optimumnetworks.com/PAconfig . Sounds like Jonathan could also use the bridge patches together with Shorewall thus avoiding Proxy ARP. I know that Jacque has been working with someone to test bridging with Bering but I haven't heard about any results recently. Even if Proxy ARP is used, with only two firewall interfaces and the requirement to Proxy ARP the entire subnet behind the firewall, I wouldn't use the /etc/shorewall/proxyarp file at all. I would instead: echo 1 > /proc/sys/net/ipv4/config/all/proxy_arp That way, the firewall will Proxy ARP in both directions using the firewall's routing table. -Tom -- Tom Eastep\ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ [EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Bering programs
Hi, Just a quik question. Is Bering based on Debian 2.2 r5?? If so, can I freely use Debian programs on Bering, provided the necessary libraries ar available? How do I detect program libraries dependencies?? Thanks Sergio D. Morilla Sistemas Tipoiti SATIC San Martín 647 Piso 2 Tel. : +54 11 4314-4482 C1004AAM - Buenos Aires Fax : +54 11 4508-6425 Argentina e-mail [EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Re: Leaf-user digest, Vol 1 #746 - 4 msgs
On Fri, 22 Mar 2002, Erich Titl wrote: --> Date: Fri, 22 Mar 2002 08:31:37 +0100 --> From: Erich Titl <[EMAIL PROTECTED]> --> To: [EMAIL PROTECTED] --> Subject: [Leaf-user] Re: Leaf-user digest, Vol 1 #746 - 4 msgs --> --> At 12:15 21.03.2002 -0800, you wrote: --> --> >Message: 3 --> >Date: Thu, 21 Mar 2002 13:35:57 -0600 (CST) --> >From: w <[EMAIL PROTECTED]> --> >To: [EMAIL PROTECTED] --> >Subject: [Leaf-user] dnscache/tinydns for dhcp aquired dns servers --> > --> >Hi, --> > --> >I have a question I hope someone can help me with. Here goes: --> > --> >I'm running dachstein on a 1722K floppy, with dhclient.lrp, --> >dhcpd.lrp, daemontl.lrp, tinydns.lrp and dnscache.lrp. Currently --> >I'm in the testing phase, but I hope to use this setup in a --> >couple of situations soon. --> > --> >Question: --> > --> >DMACHINE, (Better know as my dachstein 233MHZ machine), uses --> >the dhclient to obtain an IP for it's eth0 interface. Also in --> >the lease information, is the external DNS server IP(s). --> >Normally, the dhclient would update /etc/resolv.conf with this --> >DNS information, but I've turned this functionality off, and --> >instead have an resolv.conf entry point to my eth1 interface, --> >on which dnscache is running. dnscache uses tinydns, (running --> >on the loopback interface), for my internal network DNS resolution. --> > --> >I would like dnscache to use the DNS server IP(s) in the lease --> >information for external resolution, (without manually updating --> >the configuration). One way to do this is to update --> >/etc/dnscache/env/DNS0 (or /etc/dnscache/env/DNS1) after --> >the dhcplient lease has been aquired, and start/restart the --> >dnscache server. --> > --> >Is "something" like this functionality already implemented? --> > --> > --> >Much thanks guys and gddals --> > --> >Will --> --> Add something like --> --> echo $new_ip_address > /etc/dnscache/env/DNS0 --> --> to your /etc/dhclient-exit-hooks file and restart dnscache --> --> HTH --> --> Erich --> I'm thinking, (but not sure), the following occurs: "/etc/init.d/dhclient" calls "/usr/sbin/dhclient" which reads the dhclient.conf file and also parses the ISP lease info. Because I'm using the "supersede domain-name-servers" directive in the dhclient.conf file, I'm thinking the variable that should hold the nameserver(s) from the ISP lease info, instead contain the nameserver(s) from the dhclient.conf file "BEFORE" control is passed to the "/etc/dhclient-script". I believe only "/etc/dhclient-script" calls/sources "dhclient-exit-hooks" but at this point, only the nameservers I've explicitly specified in the "dhclient.conf" file have are avaliable to "/etc/dhclient-script". So effectively the ISP nameserver(s) in the lease info have been "lost" unless I change and recompile "/usr/sbin/dhclient", (which "I" have NO plans of doing). So it may be possible to "reaquire" this info directly from the "dhclient.leases" file, but I don't know if its a good idea to do this, and I also don't know at what point during the above process would I do this. Does this only make sence in my twisted twisted brain? Please help. Will ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] Eigerstein with 2 internal Networks.
Thanks Charles, INTERN_NET="192.168.0.0/24 172.16.0.0/24" This worked. I had to manually add the routes in Eigerstein. Best, Joe -Original Message- From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] Sent: Friday, March 22, 2002 9:26 AM To: Kroboth, Joe; [EMAIL PROTECTED] Subject: Re: [Leaf-user] Eigerstein with 2 internal Networks. > I'm using Eigerstein for my internet access, VPN and Port forwarding. I am > masquerading my current network. I now have a need to masquerade another > internal subnet. > > Here is the setup. > >Internet >| > Eigerstein >| > 192.168.0 network >| > Multihomed NT server >Routing between networks >| > 172.16 network > > I would like to masquerade the 172.16 network. (give them internet access) > Is this possible with Eigerstein? Yes. You need to make two changes to /etc/network.conf (both assume Dachstein network scripts...I don't recall off-hand if these features were implemented in Eiger): 1) Add a static route to the 172 network so your firewall can talk to it. Assuming your internal network interface on the Eiger box is eth1: eth1_ROUTES="172.16.0.0/24_via_192.168.0.111" Obviously, modify the network specification (172.16.0.0/24) and IP of your multi-homed NT system (192.168.0.111) as required for your network (you didn't provide specifics, so I made some up :) 2) Add the new network to INTERN_NET: INTERN_NET="192.168.0.0/24 172.16.0.0/24" Again, change the 172 network specification as required for your setup. I doubt both of these parameters are supported by EigerStein. You could upgrade your network scripts, but I'd suggest upgrading to Dachstein. 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 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Static routes in Bering
Hi paul > Hi all, > Just a quick question, > how can I set routes in Bering? I cant seem to find it in the documentation > anywhere. > I know how to set them using iproute2 but don't know how to save them so > they are there on a reboot. > In Dachstein, its by adding the ROUTE= command to each interface in "Network > conf" is there a similar way in Bering? The routes to the devices you have declared are set automatically by shorewall, for extra routes you can add after each interface up followed by the iproute command . I give an example to add route 192.168.3.0/24 and an extra adress 192.168.3.245 to eth2 edit interfaces () auto eth2 iface eth2 inet static address 192.168.2.254 masklen 24 broadcast 192.168.2.255 # untill hear "normal setup the following commands are executed # as device comes up up ip addr add 192.168.3.245 dev eth2 up ip route add 192.168.3.0/24 dev eth2 () backup etc . Greetings Eric Wolzak (the bering crew) http://leaf.sf.net/devel/ericw http://leaf.sf.net/devel/jnilo > Thanks in advance, > > Paul > > > ___ > 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] A jpg diagram of my working LEAF
Reginald R. Richardson wrote: > Looks...almost like mines.. > > Job will done.. > > cheers > > -Original Message- > From: junkmail [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, March 20, 2002 23:29 > To: [EMAIL PROTECTED] > Subject: [Leaf-user] A jpg diagram of my working LEAF > > > this is how I share our company 1meg dsl with > other clients in our building, it works terrific > > Thanks to all your help, > espically Matthew and CS for ironing out my mistakes. > > http://home.attbi.com/~crackerjack31/LEAFslfc.jpg > > > thanks > Gary. > > my next LEAF application will require Gigabit nic's if anyone finds > a brand that works, please post it... I just saw the picture, and it looks nice. I'd be curious to know what breaks most often on that collection of systems. Good Luck, Matt ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering programs
Hello Sergio Bering is Based on Debian Slink (2.1 ? ) like the other "leaf flavours" too You can use almost all lrp packages that are made for the Dachstein and Oxygen. As long as they are not kernel dependent. (now 2.4.19) We have also removed some libs. > > Just a quik question. > > Is Bering based on Debian 2.2 r5?? > If so, can I freely use Debian programs on Bering, provided > the necessary libraries ar available? Slink programs yes. > How do I detect program libraries dependencies?? The programm doesn't function ;) to see what externals are used you can use programms like objdump and ldd see the manpages. But there are a large amount of programms packaged for leave so you can best use the appropriate lrp package. look in the leaf.sf.net for packages. > Thanks > > Sergio D. Morilla > Sistemas > > Tipoiti SATIC > San Martín 647 Piso 2 Tel. : +54 11 4314-4482 > C1004AAM - Buenos Aires Fax : +54 11 4508-6425 > Argentina e-mail [EMAIL PROTECTED] Eric Wolzak > > ___ > 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 and Intel 2021 wireless card
Bonsoir Etienne > I've successfully managed to configure a bering floppy to use my pppoe > connection ( chapeau les mecs ! ! ) Good > Now, I'm trying to configure the wireless adapter but I'm "lost" > My firewall machine IS NOT a laptop. > > The Intel PRO/Wireless is in a PCI adapter. > tcic.o, yenta_socket, i82092, i82365 modules with no success > Should I realy use the PCMCIA stuff or is there other modules to use ??? Most probably Yes But what is really your card ? I do not know any Intel 2021. There is an Intel 2011 and an Intel 2011B I have no experience with those cards but Intel 2011 is supposed to worked with the orinoco drivers (check /etc/pcmcia/hermes.conf) But the Intel site also says that the Intel 2011 requires spectrum24 http://sourceforge.net/projects/spectrum24/ http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.htm l#Spectrum24t The problem with this last one is that it is not provided as a pcmcia kernel driver . It is not part of the pcmcia-cs package either. You might send a post to the spectrum list: http://sourceforge.net/forum/forum.php?forum_id=34783 It seems that the spectrum stuff does not work with the pcmcia kernel mode. Only with the pcmcia_cs approach. I am considering switching back to this approach for pcmcia support. Seems more robust than pcmcia kernel route. >From the spectrum README: Symbol Spectrum24 Linux driver Beta 5 In order to get this driver up and running you must have the pcmcia package installed. This driver was compiled against and tested with version 3.1.24 of David Hinds' pcmcia package. This driver also requires version 2.2.x or 2.4.x of the Linux kernel. I may get around to porting it backwards at some point, but with all the advantages to driver writers that the newer kernel offers, it made sense to start there. NOTE: in the 2.4.x kernel, it was tested with the kernel support for PCMCIA *off*, I'm not sure why, but there are some compatibility issues that can arise when the native kernel level support is turned on. Hope that will help. Let me know. Jacques ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] http
hello- This might seem like a silly question but, here it goes anyway. Is it possible to tunnel http through ssh on port 22 and access a website from outside the local network? Thanks! Brian ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] http
> This might seem like a silly question but, here it goes anyway. Is it > possible to tunnel http through ssh on port 22 and access a website from > outside the local network? Absolutely! Run something like the following on your local system (use cygwin on a windows box) ssh -L 80::80 -l This will connect your local port 80 to port 80 on via an ssh connection to . To access the remote website, just go to http://localhost , or http://127.0.0.1 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] Dachstein CD and Intel 2021 wireless card
Hi, Jacques Sorry for not giving enough details about my problem - The card is an Intel Pro/Wireless 2011 (PCMCIA) - I tried to put it in the Intel carrier sold for it (the card is in the PC now) - I added (and renamed) the pcmcia_orinoco.lrp package - When I boot with bering rc1. I get the following error message (retyped) in pcmcia package config ( file 1 /etc/default/pcmcia) I changed PCIC=i82365 same behaviour Starting PCMCIA services: modules Using /lib/modules/pcmcia/pcmcia_core.o Using /lib/modules/pcmcia/i82365.o insmod: init_module: i82365: Operation not supported by device Using /lib/modules/pcmcia/ds.o ds: no socket drivers loaded insmod: init_module: ds: Operation not permitted cardmgr. cardmgr[828]: no pcmcia driver in /proc/devices I don't see any chip number on the PCI carrier to It's difficult to guest which socket driver would work. I tried to put the card with the carrier in a Windows 2000 pc and when the drivers are correctly installed, I just see an Intel Pro/Wireless 2011 LAN PCI Card. but no PCMCIA Adapter branch in the "device manager" I check my laptop, It has a Rico R/RL/5C476 cardbus controller. in the pcmcia howto, it seems to be supported but I don't kown which socket driver to use Thanks in advance for your help and once more congratulations on the work done on the leaf project - Original Message - From: "Jacques Nilo" <[EMAIL PROTECTED]> To: "Etienne Charlier" <[EMAIL PROTECTED]>; "Lee" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 10:14 PM Subject: Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card > Bonsoir Etienne > > I've successfully managed to configure a bering floppy to use my pppoe > > connection ( chapeau les mecs ! ! ) > Good > > Now, I'm trying to configure the wireless adapter but I'm "lost" > > My firewall machine IS NOT a laptop. > > > > The Intel PRO/Wireless is in a PCI adapter. > > tcic.o, yenta_socket, i82092, i82365 modules with no success > > Should I realy use the PCMCIA stuff or is there other modules to use ??? > Most probably Yes > > But what is really your card ? > I do not know any Intel 2021. There is an Intel 2011 and an Intel 2011B > I have no experience with those cards but > Intel 2011 is supposed to worked with the orinoco drivers (check > /etc/pcmcia/hermes.conf) > But the Intel site also says that the Intel 2011 requires spectrum24 > http://sourceforge.net/projects/spectrum24/ > http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers. htm > l#Spectrum24t > The problem with this last one is that it is not provided as a pcmcia kernel > driver . It is not part of the pcmcia-cs package either. > You might send a post to the spectrum list: > http://sourceforge.net/forum/forum.php?forum_id=34783 > It seems that the spectrum stuff does not work with the pcmcia kernel mode. > Only with the pcmcia_cs approach. I am considering switching back to this > approach for pcmcia support. Seems more robust than pcmcia kernel route. > > >From the spectrum README: > > > Symbol Spectrum24 Linux driver Beta 5 > > In order to get this driver up and running you must have the pcmcia package > installed. This driver was compiled against and tested with version 3.1.24 > of David Hinds' pcmcia package. > > This driver also requires version 2.2.x or 2.4.x of the Linux kernel. I may > get around to porting it backwards at some point, but with all the > advantages to driver writers that the newer kernel offers, it made sense to > start there. > > NOTE: in the 2.4.x kernel, it was tested with the kernel support for PCMCIA > *off*, I'm not sure why, but there are some compatibility issues that can > arise when the native kernel level support is turned on. > > > Hope that will help. Let me know. > > Jacques > > > > > > ___ > 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
[Leaf-user] Traffic Shaping using TC
Well I Couldn't get cbq.init to work - possibly because of the busybox find command, or because I'm not "getting" something. Either way I decided to give up that dream and look at trying to create a script that would just use tc. What I'd like my end result to be is to limit the outgoing bandwidth that is used by my ftp server to 16 K/s. From what I read I should be able to use tc, assuming all proper modules are loaded, without having to change anything else. I realize that this would probably be easier if implemented using network.conf but as I use seawall thats not really an option. Here is what I've got - but I could be (and quite likely am) hopelessly confused. #!/bin/sh tc qdisc del dev eth0 root tc qdisc add dev eth0 root handle 10: cbq bandwidth 10mbit avpkt 1000 tc class add dev eth0 parent 10: classid 10:1 cbq bandwidth 10mbit / rate 128kbit allot 1514 maxburst 20 avpkt 1000 bounded prio 3 tc filter add dev eth0 parent 10: protocol ip prio 100 u32 match / ip dport 21 0x flowid 10:10 #end script I have no idea whether this will work - and before I throw it on my box I figured I might as well ask - can't be any harm in asking first. Any help would be greatly appreciated. S _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card
http://leaf.sourceforge.net/devel/jnilo - Original Message - From: "Etienne Charlier" <[EMAIL PROTECTED]> To: "Jacques Nilo" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, March 22, 2002 11:53 PM Subject: Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card > Hi, Jacques > > Sorry for not giving enough details about my problem > > - The card is an Intel Pro/Wireless 2011 (PCMCIA) > - I tried to put it in the Intel carrier sold for it (the card is in the PC > now) > - I added (and renamed) the pcmcia_orinoco.lrp package > - When I boot with bering rc1. I get the following error message > (retyped) > in pcmcia package config ( file 1 /etc/default/pcmcia) > I changed > PCIC=i82365 > > same behaviour > Starting PCMCIA services: > modules > Using /lib/modules/pcmcia/pcmcia_core.o > Using /lib/modules/pcmcia/i82365.o > insmod: init_module: i82365: Operation not supported by device > Using /lib/modules/pcmcia/ds.o > ds: no socket drivers loaded > insmod: init_module: ds: Operation not permitted > cardmgr. > cardmgr[828]: no pcmcia driver in /proc/devices > > I don't see any chip number on the PCI carrier to It's difficult to guest > which socket driver would work. > > I tried to put the card with the carrier in a Windows 2000 pc and when the > drivers are correctly installed, I just see an Intel Pro/Wireless 2011 LAN > PCI Card. but no PCMCIA Adapter branch in the "device manager" > > I check my laptop, It has a Rico R/RL/5C476 cardbus controller. in the > pcmcia howto, it seems to be supported but I don't kown which socket driver > to use > > Thanks in advance for your help and once more congratulations on the work > done on the leaf project > > - Original Message - > From: "Jacques Nilo" <[EMAIL PROTECTED]> > To: "Etienne Charlier" <[EMAIL PROTECTED]>; "Lee" > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Friday, March 22, 2002 10:14 PM > Subject: Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card > > > > Bonsoir Etienne > > > I've successfully managed to configure a bering floppy to use my pppoe > > > connection ( chapeau les mecs ! ! ) > > Good > > > Now, I'm trying to configure the wireless adapter but I'm "lost" > > > My firewall machine IS NOT a laptop. > > > > > > The Intel PRO/Wireless is in a PCI adapter. > > > tcic.o, yenta_socket, i82092, i82365 modules with no success > > > Should I realy use the PCMCIA stuff or is there other modules to use ??? > > Most probably Yes > > > > But what is really your card ? > > I do not know any Intel 2021. There is an Intel 2011 and an Intel 2011B > > I have no experience with those cards but > > Intel 2011 is supposed to worked with the orinoco drivers (check > > /etc/pcmcia/hermes.conf) > > But the Intel site also says that the Intel 2011 requires spectrum24 > > http://sourceforge.net/projects/spectrum24/ > > > http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers. > htm > > l#Spectrum24t > > The problem with this last one is that it is not provided as a pcmcia > kernel > > driver . It is not part of the pcmcia-cs package either. > > You might send a post to the spectrum list: > > http://sourceforge.net/forum/forum.php?forum_id=34783 > > It seems that the spectrum stuff does not work with the pcmcia kernel > mode. > > Only with the pcmcia_cs approach. I am considering switching back to this > > approach for pcmcia support. Seems more robust than pcmcia kernel route. > > > > >From the spectrum README: > > > > > > Symbol Spectrum24 Linux driver Beta 5 > > > > In order to get this driver up and running you must have the pcmcia > package > > installed. This driver was compiled against and tested with version 3.1.24 > > of David Hinds' pcmcia package. > > > > This driver also requires version 2.2.x or 2.4.x of the Linux kernel. I > may > > get around to porting it backwards at some point, but with all the > > advantages to driver writers that the newer kernel offers, it made sense > to > > start there. > > > > NOTE: in the 2.4.x kernel, it was tested with the kernel support for > PCMCIA > > *off*, I'm not sure why, but there are some compatibility issues that can > > arise when the native kernel level support is turned on. > > > > > > Hope that will help. Let me know. > > > > Jacques > > > > > > > > > > > > ___ > > 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 and Intel 2021 wireless card
> - The card is an Intel Pro/Wireless 2011 (PCMCIA) > - I tried to put it in the Intel carrier sold for it (the card is in the PC > now) > - I added (and renamed) the pcmcia_orinoco.lrp package > - When I boot with bering rc1. I get the following error message > (retyped) > in pcmcia package config ( file 1 /etc/default/pcmcia) > I changed > PCIC=i82365 > > same behaviour > Starting PCMCIA services: > modules > Using /lib/modules/pcmcia/pcmcia_core.o > Using /lib/modules/pcmcia/i82365.o > insmod: init_module: i82365: Operation not supported by device > Using /lib/modules/pcmcia/ds.o > ds: no socket drivers loaded > insmod: init_module: ds: Operation not permitted > cardmgr. > cardmgr[828]: no pcmcia driver in /proc/devices > > I don't see any chip number on the PCI carrier to It's difficult to guest > which socket driver would work. > > I tried to put the card with the carrier in a Windows 2000 pc and when the > drivers are correctly installed, I just see an Intel Pro/Wireless 2011 LAN > PCI Card. but no PCMCIA Adapter branch in the "device manager" > > I check my laptop, It has a Rico R/RL/5C476 cardbus controller. in the > pcmcia howto, it seems to be supported but I don't kown which socket driver > to use > > Thanks in advance for your help and once more congratulations on the work > done on the leaf project > > - Original Message - > From: "Jacques Nilo" <[EMAIL PROTECTED]> > To: "Etienne Charlier" <[EMAIL PROTECTED]>; "Lee" > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Friday, March 22, 2002 10:14 PM > Subject: Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card > > > > Bonsoir Etienne > > > I've successfully managed to configure a bering floppy to use my pppoe > > > connection ( chapeau les mecs ! ! ) > > Good > > > Now, I'm trying to configure the wireless adapter but I'm "lost" > > > My firewall machine IS NOT a laptop. > > > > > > The Intel PRO/Wireless is in a PCI adapter. > > > tcic.o, yenta_socket, i82092, i82365 modules with no success > > > Should I realy use the PCMCIA stuff or is there other modules to use ??? > > Most probably Yes > > > > But what is really your card ? > > I do not know any Intel 2021. There is an Intel 2011 and an Intel 2011B > > I have no experience with those cards but > > Intel 2011 is supposed to worked with the orinoco drivers (check > > /etc/pcmcia/hermes.conf) > > But the Intel site also says that the Intel 2011 requires spectrum24 > > http://sourceforge.net/projects/spectrum24/ > > > http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers. > htm > > l#Spectrum24t > > The problem with this last one is that it is not provided as a pcmcia > kernel > > driver . It is not part of the pcmcia-cs package either. > > You might send a post to the spectrum list: > > http://sourceforge.net/forum/forum.php?forum_id=34783 > > It seems that the spectrum stuff does not work with the pcmcia kernel > mode. > > Only with the pcmcia_cs approach. I am considering switching back to this > > approach for pcmcia support. Seems more robust than pcmcia kernel route. > > > > >From the spectrum README: > > > > > > Symbol Spectrum24 Linux driver Beta 5 > > > > In order to get this driver up and running you must have the pcmcia > package > > installed. This driver was compiled against and tested with version 3.1.24 > > of David Hinds' pcmcia package. > > > > This driver also requires version 2.2.x or 2.4.x of the Linux kernel. I > may > > get around to porting it backwards at some point, but with all the > > advantages to driver writers that the newer kernel offers, it made sense > to > > start there. > > > > NOTE: in the 2.4.x kernel, it was tested with the kernel support for > PCMCIA > > *off*, I'm not sure why, but there are some compatibility issues that can > > arise when the native kernel level support is turned on. > > > > > > Hope that will help. Let me know. > > > > Jacques > > > > > > > > > > > > ___ > > 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 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Dachstein CD and Intel 2021 wireless card
Sorry for previous answer which were sent empty by mistake :-) > - The card is an Intel Pro/Wireless 2011 (PCMCIA) > - I tried to put it in the Intel carrier sold for it (the card is in the PC > now) > - I added (and renamed) the pcmcia_orinoco.lrp package > - When I boot with bering rc1. I get the following error message > (retyped) > in pcmcia package config ( file 1 /etc/default/pcmcia) > I changed > PCIC=i82365 > > same behaviour > Starting PCMCIA services: > modules > Using /lib/modules/pcmcia/pcmcia_core.o > Using /lib/modules/pcmcia/i82365.o > insmod: init_module: i82365: Operation not supported by device > Using /lib/modules/pcmcia/ds.o > ds: no socket drivers loaded > insmod: init_module: ds: Operation not permitted > cardmgr. > cardmgr[828]: no pcmcia driver in /proc/devices > > I don't see any chip number on the PCI carrier to It's difficult to guest > which socket driver would work. It could be a PCMCIA kernel related problem. I will send you off list a new kernel without PCMCIA support and the corresponding pcmcia.lrp package. If it works like that it will be a good indication to remove pcmcia support from kernel and get it through pcmcia_cs. Jacques ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
