[leaf-user] LVS on top of Leaf?
A quick search of the archives has brought up one or two references to people playing with Linux Virtual Server on top of LEAF/LRP but no definitive evidence of success. Anyone out there built a working LEAF based LVS redirector? Any chance of sharing knowledge/code? If not I guess I'll have to break out that compiler again thx/andy ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] 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
[leaf-user] Hosts allow, SSH and dynamic IP addresses.
I've been trying to ssh into my firewall (Dachstein) from the internet at large (instead of from the internal network like I generally do). Experimenting, I added a line to hosts.allow, and used ipchains to put in a rule to accept the packets that came from my IP address, destined for the relevant port etc, and found I was able to log in by ssh without any problems. The problem I have is when I'll be doing this for real, I'll be using my internet connection at home where I have a dynamic IP address (changes about once a day). I'm wary of opening up the firewall to a big range of IP addresses (or whatever) so I tried setting up a hostname with a dynamic DNS system (dynDNS) and using the hostname instead of IP's. I think I have half a grasp of why that didn't work (I'd basically given my IP address an extra hostname, so forward and reverse name lookups didn't necessarily match - or something like that), and get the feeling that was the wrong approach to take for this problem. Can anyone give any pointers? What's the best way to grant yourself access by ssh if you have a dynamic IP? Do I need to relax a bit and put something pretty broad in hosts.allow, or is there a way to make a dynamic DNS system work the way I want? Thanks Julian Church -- [EMAIL PROTECTED] www.ljchurch.co.uk 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
RE: [leaf-user] Bering v1.0-rc2 with diskonchip?
On Tue, 2002-05-07 at 09:24, Darren Martz wrote: Yes, when I load docprobe.o after docecc.o and doc2000.o it reports address 0xD, but not the nftla1 as the article indicates. The #cat output is: Dev:size erasesize name Mtd0: 0100 4000 DiskOnChip 2000 I couldn't find much on the nftla1 comment made in that article, there really wasn't much to go on. I have tried loading the mtdchar and mtdblock modules before as well. That same article indicates the mtdblock is for a caching mechanics in relation to the lifespan of the chip... I just changed my configuration and tried with the extra mtd modules loaded - sadly, no change. I just read over the dmesg logs again and found something: manufacturer id: EC chip id: 73 (Samsung KM29U128T) 1 flash chips found. Total DiskOnChip size: 16 MiB Partition check nftla: nftla1 This is a 64mb chip currently with Slackware7 on an ext2 filesystem (I have loaded the ext2 module). It does not appear to be correctly identifying the chipset (anyone please feel free to correct me on this one). Comparing to the slackware7 logs, it loads the custom M-System driver that states 2 copyright messages and DOC device(s) found: 1. Darren, From my limited knowledge, it looks like the autodetect isn't functioning properly. The other possibility is a compatibility problem with MTD and the M-system drivers. Are you able to mount nftla1? -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] 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
RE: [leaf-user] Bering v1.0-rc2 with diskonchip?
no such file or directory when mounting nftla1. Agreed, there seems to be a compatibility problem with MTD. I just asked the author of the The Linux MTD, JFFS HOWTO paper for assistance, hopefully he can shed some light on the subject. Darren -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Noyes Sent: May 7, 2002 9:43 AM To: [EMAIL PROTECTED] Subject: RE: [leaf-user] Bering v1.0-rc2 with diskonchip? This is a 64mb chip currently with Slackware7 on an ext2 filesystem (I have loaded the ext2 module). It does not appear to be correctly identifying the chipset (anyone please feel free to correct me on this one). Comparing to the slackware7 logs, it loads the custom M-System driver that states 2 copyright messages and DOC device(s) found: 1. Darren, From my limited knowledge, it looks like the autodetect isn't functioning properly. The other possibility is a compatibility problem with MTD and the M-system drivers. Are you able to mount nftla1? ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] 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
RE: [leaf-user] Bering v1.0-rc2 with diskonchip?
On Tue, 2002-05-07 at 09:56, Darren Martz wrote: no such file or directory when mounting nftla1. Agreed, there seems to be a compatibility problem with MTD. I just asked the author of the The Linux MTD, JFFS HOWTO paper for assistance, hopefully he can shed some light on the subject. Darren, You may want to ask for assistance on the MTD mailing list. http://lists.infradead.org/mailman/listinfo/linux-mtd/ Please keep us updated on your progress. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Noyes Sent: May 7, 2002 9:43 AM To: [EMAIL PROTECTED] Subject: RE: [leaf-user] Bering v1.0-rc2 with diskonchip? This is a 64mb chip currently with Slackware7 on an ext2 filesystem (I have loaded the ext2 module). It does not appear to be correctly identifying the chipset (anyone please feel free to correct me on this one). Comparing to the slackware7 logs, it loads the custom M-System driver that states 2 copyright messages and DOC device(s) found: 1. Darren, From my limited knowledge, it looks like the autodetect isn't functioning properly. The other possibility is a compatibility problem with MTD and the M-system drivers. Are you able to mount nftla1? -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] 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
[leaf-user] Linux 2.4.X broadcast wan
Hi list, The linux kernel config file showed me some interesting stuf Basicly it talks about a broadcast wan to basicly create a virtual lan ( don't misunderstand for VLAN) distributed accross the internet. I would like to try out something like that, but can't seem to find any documentation on what to do. Any pointers anyone? Below is the help info from the linux configure script. IP: broadcast GRE over IP CONFIG_NET_IPGRE_BROADCAST One application of GRE/IP is to construct a broadcast WAN (Wide Area Network), which looks like a normal Ethernet LAN (Local Area Network), but can be distributed all over the Internet. If you want to do that, say Y here and to IP: multicast routing below Kim Oppalfens Azlan Training ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] 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
