Re: [leaf-user] Booting from a USB FDD. Help please.
- Original Message - From: "Jacques Nilo" <[EMAIL PROTECTED]> To: "Jeff Newmiller" <[EMAIL PROTECTED]>; "Bob Alexander" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 08, 2003 9:39 PM Subject: Re: [leaf-user] Booting from a USB FDD. Help please. > Le Mercredi 8 Octobre 2003 18:21, Jeff Newmiller a écrit : > > On Wed, 8 Oct 2003, Bob Alexander wrote: > > > Am trying to use Bering on my T40 Thinkpad. A great project on a great > > > laptop 8-> > > > > A look at the module.dep file gives you the answer: > usb-storage depends on usbcore & scsi_mod that need to be loaded first. > http://leaf.sf.net/devel/jnilo/bering/latest/modules/2.4.20/modules.dep > Jacques > Jacques (and others), thank you very very much. Will try out. Would it be possible that the MIME type associated with the modules.dep would be text ? I would like to write an Italian version of your installation guide. Not a full translation (afraid would not have time to do that) but a terse, quick HOWTO. If i do so would you be interested in adding it to the project doc ?? Ciao from Rome (caput mundi 8->). Bob Alexander --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Booting from a USB FDD. Help please
>> usb.c: new USB hub registered, assigned bus number 3 >> ... same as above >> Using /boot/lib/modules/usb-stor.o >> Insmod unresolved symbol scsi_unregister_module >> Insmod unresolved symbol scsi_register >> Insmod unresolved symbol scsi_register_module >> Linuxrc Could not mount the boot device. Can't install packages >> Kernel panic: attempted to kill init >> >> From what I understand (no guru here 8-<) could it be that >> the kernel does >> not support the scsi "emulation" that is usually >> used to mount a USB storage device ?? > You will need the scsi modules also. > Luis Correia Luis thank you very much (muito obrigado ?). How can I understand which of the many many modules present in the scsi directory own the missing symbols ??? (this is a general question). Take care Bob Alexander PS Sorry for replying not perfectly but I am receiving the digest !!! --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Booting from a USB FDD. Help please
[snip] > > > You will need the scsi modules also. > > Luis Correia > > Luis thank you very much (muito obrigado ?). Grazie! > > How can I understand which of the many many modules present > in the scsi > directory own the missing symbols ??? (this is a general question). you will probably need the scsi_mod. Check the modules.dep in the kernel source tree. > > Take care > > Bob Alexander > > PS Sorry for replying not perfectly but I am receiving the digest !!! > Your reply is perfect enough. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Re: [Bering] IDLE Problem (Michelle Konzack)
JD wrote: Regarding the following issue with ppp0 idle command failing ... Am 2003-10-07 21:50:29, schrieb Jeff Newmiller: On Wed, 8 Oct 2003, Michelle Konzack wrote: Hello all, if I set the idle to 30~80 seconds, all is working fine. But more give me no Timeout on ppp0. Why ? Your link is probably being keep active by inbound traffic from the internet. I had the same issue. I was "normally" able to get a proper disconnect with a short idle timeout [like 30-60 seconds]. But with my desired timeout of 600 seconds - inbound traffic from the internet would reset the pppd timer and keep the link active forever. [...] I like to have an 'IDLE 300' but this will never disconnect... I was trying two weeks the Bering with the 'active-filter' and it does not work. There is no incoming and no outgoing traffic, and Bering does not disconnect after 300 seconds. Are you sure that there is not inbound traffic??? What I found was inbound pings [ICMP] and other unwanted traffic from the net was resetting my timer. I found that using the following command 'pppstats -w 30' worked well to identify that infact traffic was coming from the net [note 30 is the number of seconds between stat updates]. While pppstats was updating my screen - I was able to see inbound bytes incrementing. Shorewall would drop the packet, but pppd saw it as valid traffic. I finally pulled the tcpdump.lrp to my FW to watch the traffic that was inbound. What I found was MS share requests, pings, and other traffic was keeping my ppp0 interface active. I pulled down the pppd with the filter enabled and replaced my default pppd file. I added the following to my /etc/ppp/options file ... active-filter 'not(icmp[0]=0 or icmp[0]=3 or icmp[0]=8 or port 135 or port 137 or port 139 or port 445)' which has solved my problem. The format is the same as the tcpdump expression. I did not find too much helpful information on the net about the syntax - but was able to filter icmp's - and test it with tcpdump. Later I added the port 135-139 & 445 because I continued to see M$ junk hitting my FW. I have setup a dial out Bering firewall in a small office. Recently I noticed that it often fails to hang up the modem even when all machines on the internal network have been turned off for long past the timeout value. Possibly this is because of the increased number of worms hammering on the outside. I replaced pppd with the active-filter version but had not researched how to implement it. I shall try your active-filter line in /etc/ppp/options. Thanks very much for your post and hope this solves the "no hang up" the modem problem. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] 2xNIC Bering won't route? Help!
Hi Everybody, This ones got my hair falling out. A very simple task, which I've done before. 1 Bering box, 2 NICs (3c905C and rtl8139) This box has no external connection (yet, still no ADSL), just needs to route between the two eth adaptors A D-Link WAP (192.168.51.2) is plugged straight into eth1 (192.168.51.1) A WinXP (192.168.50.30) box is crossed over into eth0 (192.168.50.1) Hosts.allow contains ALL: 192.168.50.0/255.255.255.0 ALL: 192.168.51.0/255.255.255.0 Two zones in shorewall, dave and alex (+fw). Dave is bound to eth1, alex to eth0. Policy is: DavealexACCEPT AlexdaveACCEPT Fw all ACCEPT All fw ACCEPT The routes are correctly set, all ping requests flash a light on a NIC somewhere. Fw can ping it's interfaces, the WAP and the XP box. The XP box can ping both interfaces of the FW box. A wireless client can ping the WAP and the FW box. But that's it. The XP box cannot see the WAP or any wireless clients. I could've sworn this worked on Sunday... I'm not doing any NAT, maybe I have to turn NAT off in shorewall config? Somebody please help, this is driving me nuts... Thanks again, James. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] 2xNIC Bering won't route? Help!
Does the D-Link have it's gateway set up to be 192.168.51.1? Cheers, Dave. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > James Neave > Sent: 09 October 2003 10:14 > To: [EMAIL PROTECTED] > Subject: [leaf-user] 2xNIC Bering won't route? Help! > > > Hi Everybody, > > This ones got my hair falling out. A very simple task, which > I've done before. > > 1 Bering box, 2 NICs (3c905C and rtl8139) > > This box has no external connection (yet, still no ADSL), > just needs to route between the two eth adaptors > > A D-Link WAP (192.168.51.2) is plugged straight into eth1 > (192.168.51.1) A WinXP (192.168.50.30) box is crossed over > into eth0 (192.168.50.1) > > Hosts.allow contains > ALL: 192.168.50.0/255.255.255.0 > ALL: 192.168.51.0/255.255.255.0 > > Two zones in shorewall, dave and alex (+fw). > Dave is bound to eth1, alex to eth0. > > Policy is: > > Dave alexACCEPT > Alex daveACCEPT > Fwall ACCEPT > All fw ACCEPT > > The routes are correctly set, all ping requests flash a light > on a NIC somewhere. > > Fw can ping it's interfaces, the WAP and the XP box. > The XP box can ping both interfaces of the FW box. > A wireless client can ping the WAP and the FW box. > > But that's it. The XP box cannot see the WAP or any wireless clients. > > I could've sworn this worked on Sunday... > I'm not doing any NAT, maybe I have to turn NAT off in > shorewall config? > > Somebody please help, this is driving me nuts... > > Thanks again, > > James. > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. See > the people who have HELPED US provide better services: Click > here: http://sourceforge.net/supporters.php > -- > -- > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/l> eaf-user > SR > FAQ: > http://leaf-project.org/pub/doc/docmanager/docid_1891.html > --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] 2xNIC Bering won't route? Help!
Hi, Yes, here are the settings for all the hosts. The WAP IP: 192.168.51.2 MASK: 255.255.255.0 GATE: 192.168.51.1 DNS:192.168.51.1 (redundant, no DNS yet) The XP Box IP: 192.168.50.30 MASK: 255.255.255.0 GATE: None DNS:None ON the XP Box: Route add 192.168.51.0 MASK 255.255.255.0 192.168.50.30 Interfaces file on the bering box: (may not be precise syntax, but the values are correct) Auto eth0 Eth0 static Address 192.168.50.1 Masklen 24 Broadcast 192.168.50.255 (no gateway tag) auto eth1 eth1 static address 192.168.51.1 masklen 24 broadcast 192.168.51.255 (no gateway tag) "ip route show" just has the two networks with their respective adaptors. Thanks, James. -Original Message- From: Dave Hunt [mailto:[EMAIL PROTECTED] Sent: 09 October 2003 10:37 To: James Neave; [EMAIL PROTECTED] Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! Does the D-Link have it's gateway set up to be 192.168.51.1? Cheers, Dave. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > James Neave > Sent: 09 October 2003 10:14 > To: [EMAIL PROTECTED] > Subject: [leaf-user] 2xNIC Bering won't route? Help! > > > Hi Everybody, > > This ones got my hair falling out. A very simple task, which > I've done before. > > 1 Bering box, 2 NICs (3c905C and rtl8139) > > This box has no external connection (yet, still no ADSL), > just needs to route between the two eth adaptors > > A D-Link WAP (192.168.51.2) is plugged straight into eth1 > (192.168.51.1) A WinXP (192.168.50.30) box is crossed over > into eth0 (192.168.50.1) > > Hosts.allow contains > ALL: 192.168.50.0/255.255.255.0 > ALL: 192.168.51.0/255.255.255.0 > > Two zones in shorewall, dave and alex (+fw). > Dave is bound to eth1, alex to eth0. > > Policy is: > > Dave alexACCEPT > Alex daveACCEPT > Fwall ACCEPT > All fw ACCEPT > > The routes are correctly set, all ping requests flash a light > on a NIC somewhere. > > Fw can ping it's interfaces, the WAP and the XP box. > The XP box can ping both interfaces of the FW box. > A wireless client can ping the WAP and the FW box. > > But that's it. The XP box cannot see the WAP or any wireless clients. > > I could've sworn this worked on Sunday... > I'm not doing any NAT, maybe I have to turn NAT off in > shorewall config? > > Somebody please help, this is driving me nuts... > > Thanks again, > > James. > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. See > the people who have HELPED US provide better services: Click > here: http://sourceforge.net/supporters.php > -- > -- > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/l> eaf-user > SR > FAQ: > http://leaf-project.org/pub/doc/docmanager/docid_1891.html > --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] 2xNIC Bering won't route? Help!
Route on the XP box should be Route add 192.168.51.0 MASK 255.255.255.0 192.168.50.1 Cheers, Dave. > -Original Message- > From: James Neave [mailto:[EMAIL PROTECTED] > Sent: 09 October 2003 10:51 > To: Dave Hunt; [EMAIL PROTECTED] > Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! > > > Hi, > > Yes, here are the settings for all the hosts. > > The WAP > > IP: 192.168.51.2 > MASK: 255.255.255.0 > GATE: 192.168.51.1 > DNS: 192.168.51.1 (redundant, no DNS yet) > > The XP Box > > IP: 192.168.50.30 > MASK: 255.255.255.0 > GATE: None > DNS: None > > ON the XP Box: > > Route add 192.168.51.0 MASK 255.255.255.0 192.168.50.30 > > Interfaces file on the bering box: (may not be precise > syntax, but the values are correct) > > Auto eth0 > Eth0 static > Address 192.168.50.1 > Masklen 24 > Broadcast 192.168.50.255 > (no gateway tag) > > auto eth1 > eth1 static > address 192.168.51.1 > masklen 24 > broadcast 192.168.51.255 > (no gateway tag) > > "ip route show" just has the two networks with their > respective adaptors. > > Thanks, > > James. > > -Original Message- > From: Dave Hunt [mailto:[EMAIL PROTECTED] > Sent: 09 October 2003 10:37 > To: James Neave; [EMAIL PROTECTED] > Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! > > > Does the D-Link have it's gateway set up to be 192.168.51.1? > > Cheers, > Dave. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > James Neave > > Sent: 09 October 2003 10:14 > > To: [EMAIL PROTECTED] > > Subject: [leaf-user] 2xNIC Bering won't route? Help! > > > > > > Hi Everybody, > > > > This ones got my hair falling out. A very simple task, which > > I've done before. > > > > 1 Bering box, 2 NICs (3c905C and rtl8139) > > > > This box has no external connection (yet, still no ADSL), > > just needs to route between the two eth adaptors > > > > A D-Link WAP (192.168.51.2) is plugged straight into eth1 > > (192.168.51.1) A WinXP (192.168.50.30) box is crossed over > > into eth0 (192.168.50.1) > > > > Hosts.allow contains > > ALL: 192.168.50.0/255.255.255.0 > > ALL: 192.168.51.0/255.255.255.0 > > > > Two zones in shorewall, dave and alex (+fw). > > Dave is bound to eth1, alex to eth0. > > > > Policy is: > > > > DavealexACCEPT > > AlexdaveACCEPT > > Fw all ACCEPT > > All fw ACCEPT > > > > The routes are correctly set, all ping requests flash a light > > on a NIC somewhere. > > > > Fw can ping it's interfaces, the WAP and the XP box. > > The XP box can ping both interfaces of the FW box. > > A wireless client can ping the WAP and the FW box. > > > > But that's it. The XP box cannot see the WAP or any > wireless clients. > > > > I could've sworn this worked on Sunday... > > I'm not doing any NAT, maybe I have to turn NAT off in > > shorewall config? > > > > Somebody please help, this is driving me nuts... > > > > Thanks again, > > > > James. > > > > > > --- > > This SF.net email is sponsored by: SF.net Giveback Program. > > SourceForge.net hosts over 70,000 Open Source Projects. See > > the people who have HELPED US provide better services: Click > > here: http://sourceforge.net/supporters.php > > -- > > -- > > leaf-user mailing list: [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/l> eaf-user > > SR > > FAQ: > > http://leaf-project.org/pub/doc/docmanager/docid_1891.html > > > > --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] 2xNIC Bering won't route? Help!
Hi, I'll give that a go. Somehow I got some wires crossed and thought you had to put the IP of the interface you were leaving through. Whoops... Thanks! James -Original Message- From: Dave Hunt [mailto:[EMAIL PROTECTED] Sent: 09 October 2003 11:00 To: James Neave; [EMAIL PROTECTED] Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! Route on the XP box should be Route add 192.168.51.0 MASK 255.255.255.0 192.168.50.1 Cheers, Dave. > -Original Message- > From: James Neave [mailto:[EMAIL PROTECTED] > Sent: 09 October 2003 10:51 > To: Dave Hunt; [EMAIL PROTECTED] > Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! > > > Hi, > > Yes, here are the settings for all the hosts. > > The WAP > > IP: 192.168.51.2 > MASK: 255.255.255.0 > GATE: 192.168.51.1 > DNS: 192.168.51.1 (redundant, no DNS yet) > > The XP Box > > IP: 192.168.50.30 > MASK: 255.255.255.0 > GATE: None > DNS: None > > ON the XP Box: > > Route add 192.168.51.0 MASK 255.255.255.0 192.168.50.30 > > Interfaces file on the bering box: (may not be precise > syntax, but the values are correct) > > Auto eth0 > Eth0 static > Address 192.168.50.1 > Masklen 24 > Broadcast 192.168.50.255 > (no gateway tag) > > auto eth1 > eth1 static > address 192.168.51.1 > masklen 24 > broadcast 192.168.51.255 > (no gateway tag) > > "ip route show" just has the two networks with their > respective adaptors. > > Thanks, > > James. > > -Original Message- > From: Dave Hunt [mailto:[EMAIL PROTECTED] > Sent: 09 October 2003 10:37 > To: James Neave; [EMAIL PROTECTED] > Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! > > > Does the D-Link have it's gateway set up to be 192.168.51.1? > > Cheers, > Dave. > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > James Neave > > Sent: 09 October 2003 10:14 > > To: [EMAIL PROTECTED] > > Subject: [leaf-user] 2xNIC Bering won't route? Help! > > > > > > Hi Everybody, > > > > This ones got my hair falling out. A very simple task, which > > I've done before. > > > > 1 Bering box, 2 NICs (3c905C and rtl8139) > > > > This box has no external connection (yet, still no ADSL), > > just needs to route between the two eth adaptors > > > > A D-Link WAP (192.168.51.2) is plugged straight into eth1 > > (192.168.51.1) A WinXP (192.168.50.30) box is crossed over > > into eth0 (192.168.50.1) > > > > Hosts.allow contains > > ALL: 192.168.50.0/255.255.255.0 > > ALL: 192.168.51.0/255.255.255.0 > > > > Two zones in shorewall, dave and alex (+fw). > > Dave is bound to eth1, alex to eth0. > > > > Policy is: > > > > DavealexACCEPT > > AlexdaveACCEPT > > Fw all ACCEPT > > All fw ACCEPT > > > > The routes are correctly set, all ping requests flash a light > > on a NIC somewhere. > > > > Fw can ping it's interfaces, the WAP and the XP box. > > The XP box can ping both interfaces of the FW box. > > A wireless client can ping the WAP and the FW box. > > > > But that's it. The XP box cannot see the WAP or any > wireless clients. > > > > I could've sworn this worked on Sunday... > > I'm not doing any NAT, maybe I have to turn NAT off in > > shorewall config? > > > > Somebody please help, this is driving me nuts... > > > > Thanks again, > > > > James. > > > > > > --- > > This SF.net email is sponsored by: SF.net Giveback Program. > > SourceForge.net hosts over 70,000 Open Source Projects. See > > the people who have HELPED US provide better services: Click > > here: http://sourceforge.net/supporters.php > > -- > > -- > > leaf-user mailing list: [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/l> eaf-user > > SR > > FAQ: > > http://leaf-project.org/pub/doc/docmanager/docid_1891.html > > > > --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] 2xNIC Bering won't route? Help!
On the XP Box you should add Route add -p 192.168.51.0 MASK 255.255.255.0 192.168.50.1 the -p make the route permanent. and the next hop to 192.168.51.0 should be the eth0 on the bering box Huy - Original Message - From: "James Neave" <[EMAIL PROTECTED]> To: "Dave Hunt" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, October 09, 2003 10:51 AM Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! Hi, Yes, here are the settings for all the hosts. The WAP IP: 192.168.51.2 MASK: 255.255.255.0 GATE: 192.168.51.1 DNS: 192.168.51.1 (redundant, no DNS yet) The XP Box IP: 192.168.50.30 MASK: 255.255.255.0 GATE: None DNS: None ON the XP Box: Route add 192.168.51.0 MASK 255.255.255.0 192.168.50.30 Interfaces file on the bering box: (may not be precise syntax, but the values are correct) Auto eth0 Eth0 static Address 192.168.50.1 Masklen 24 Broadcast 192.168.50.255 (no gateway tag) auto eth1 eth1 static address 192.168.51.1 masklen 24 broadcast 192.168.51.255 (no gateway tag) "ip route show" just has the two networks with their respective adaptors. Thanks, James. -Original Message- From: Dave Hunt [mailto:[EMAIL PROTECTED] Sent: 09 October 2003 10:37 To: James Neave; [EMAIL PROTECTED] Subject: RE: [leaf-user] 2xNIC Bering won't route? Help! Does the D-Link have it's gateway set up to be 192.168.51.1? Cheers, Dave. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > James Neave > Sent: 09 October 2003 10:14 > To: [EMAIL PROTECTED] > Subject: [leaf-user] 2xNIC Bering won't route? Help! > > > Hi Everybody, > > This ones got my hair falling out. A very simple task, which > I've done before. > > 1 Bering box, 2 NICs (3c905C and rtl8139) > > This box has no external connection (yet, still no ADSL), > just needs to route between the two eth adaptors > > A D-Link WAP (192.168.51.2) is plugged straight into eth1 > (192.168.51.1) A WinXP (192.168.50.30) box is crossed over > into eth0 (192.168.50.1) > > Hosts.allow contains > ALL: 192.168.50.0/255.255.255.0 > ALL: 192.168.51.0/255.255.255.0 > > Two zones in shorewall, dave and alex (+fw). > Dave is bound to eth1, alex to eth0. > > Policy is: > > Dave alex ACCEPT > Alex dave ACCEPT > Fw all ACCEPT > All fw ACCEPT > > The routes are correctly set, all ping requests flash a light > on a NIC somewhere. > > Fw can ping it's interfaces, the WAP and the XP box. > The XP box can ping both interfaces of the FW box. > A wireless client can ping the WAP and the FW box. > > But that's it. The XP box cannot see the WAP or any wireless clients. > > I could've sworn this worked on Sunday... > I'm not doing any NAT, maybe I have to turn NAT off in > shorewall config? > > Somebody please help, this is driving me nuts... > > Thanks again, > > James. > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. See > the people who have HELPED US provide better services: Click > here: http://sourceforge.net/supporters.php > -- > -- > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/l> eaf-user > SR > FAQ: > http://leaf-project.org/pub/doc/docmanager/docid_1891.html > --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Again the neverending "boot from USB FDD saga" 8-
Dear Friends, I really regret having to flood this list with this probably stupid problem but when something does not work for me I tend to become quite monomaniac 8-> Ok, as per previous help added the following modules: scsi-mod sd-mod usbcore usb-uhci usb-storage When I boot linux on the same machine I see that the external USB attached FDD is known as /dev/sda I have therefore edited the syslinux.cfg on Bering saying that the packages are not on fd0u1680 but on sda1. I also have added a 3 second delay after the modules loading. When I powerup the PC the boot from bering begins and after quite a long time (on a PC with a traditional non USB flpppy the process is much faster) at the end I find the last lines that say (going by memory): Mounted /dev/sda as msdos PKGPATH /dev/sda1 mounting /dev/sda1 on /mnt1 usb_uhci.c: interrupt status 3 frame #964 I/O error then quite a few other I/O errors and then init gets killed I also tried changing boot to /dev/sda1:msdos but the boot quit even before. I am obviously blundering in the wrong direction !!! Thank you for any help. Bob --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Problems with 3c509.o module
Hi all, I am trying to replace 2 of my current Dachstein firewalls with a Bering version. Each of these use 3c509 NICs which have been working fine for a couple of years under Dachstein but as soon as I boot the machines in Bering I get the following Kernel Panic: skput: over: c2837d85:0 put:60 dev;eth0 kernel BUG at skbuff.c:92! invalid operand: CPU:0 EIP: 0010:[] Not tainted EFLAGS: 10286 eax:00026 ebx:c10e8490 ecx:c1996000 edx:c1fb2890 esi:c10f8d60 edi:063c ebp:0012 esp:c19a7b38 ds:0018 es:0018 ss:0018 Process iptables (pid:3092, stackpage ... .. . Kernel panic:Aiee, killing interupt handler! At this point the machine is locked up with the keyboard lights flashing and can only be accessed by rebooting. The module I am using was downloaded from the LEAF site under the Bering section. Unfortunately I have no facility to compile modules so any help would be appreciated. Andrew G. Gray MCSE Phone: (07) 4124 6303 Mobile:0418 734 078 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] TI ACX100 based wireless NIC problem.
Hello All, *sighs* Well, Alex has managed to buy hardware that seems to universally hate linux... We have a D-LINK 520+ pci wifi nic based on the TI ACX100 chipset. There is a very early open driver for it here http://sourceforge.net/projects/acx100/ Which is still alpha. And a guide to use the closed driver here http://www.hack.gr/users/panxer/wireless/ This sounds more useful. But there are some things in there that confuse me. (not hard) "I tried the driver and works with my Debian 3.r0, 2.4.18 system." Sounds promising. The second link lists this as a step: Build the 2.4.18 kernel with: CONFIG_EXPERIMENTAL=y CONFIG_MODULES=y CONFIG_KMOD=y CONFIG_NET_RADIO=y CONFIG_DEBUG_KERNEL=y CONFIG_DEBUG_BUGVERBOSE=y Means nothing to me, has the Bering kernel been compiled like this? "3. Get wireless-tools by Jean Tourrilhes and build them" Is this what wireless.lrp is? Thanks! James. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Again the neverending "boot from USB FDD saga" 8-
I think you have to use /dev/sda instead of /dev/sda1 Have you try with a 1.44 formated floppy instead of 1.68. I use to have a similar prblem with a IDE LS120 drive booting a floppy. Bering recognise it as /dev/hdc. It only work with 1.44 format since I did not know how to specify the size of the floppy. (i.e i can not use something like /dev/hdc1680) Hope this help. Huy - Original Message - From: "Bob Alexander" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 09, 2003 2:45 PM Subject: [leaf-user] Again the neverending "boot from USB FDD saga" 8-< > Dear Friends, > I really regret having to flood this list with this probably stupid problem > but when something does not work for me I tend to become quite monomaniac > 8-> > > Ok, as per previous help added the following modules: > scsi-mod > sd-mod > usbcore > usb-uhci > usb-storage > > When I boot linux on the same machine I see that the external USB attached > FDD is known as /dev/sda > > I have therefore edited the syslinux.cfg on Bering saying that the packages > are not on fd0u1680 but on sda1. > > I also have added a 3 second delay after the modules loading. > > When I powerup the PC the boot from bering begins and after quite a long > time (on a PC with a traditional non USB flpppy the process is much faster) > at the end I find the last lines that say (going by memory): > > Mounted /dev/sda as msdos > PKGPATH /dev/sda1 > mounting /dev/sda1 on /mnt1 > usb_uhci.c: interrupt status 3 frame #964 > I/O error > then quite a few other I/O errors and then init gets killed > > I also tried changing boot to /dev/sda1:msdos but the boot quit even before. > > I am obviously blundering in the wrong direction !!! > > Thank you for any help. Bob > > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. > See the people who have HELPED US provide better services: > Click here: http://sourceforge.net/supporters.php > > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Problems with 3c509.o module
Hi all, I am trying to replace 2 of my current Dachstein firewalls with a Bering version. Each of these use 3c509 NICs which have been working fine for a couple of years under Dachstein but as soon as I boot the machines in Bering I get the following Kernel Panic: skput: over: c2837d85:0 put:60 dev;eth0 kernel BUG at skbuff.c:92! invalid operand: CPU:0 EIP: 0010:[] Not tainted EFLAGS: 10286 eax:00026 ebx:c10e8490 ecx:c1996000 edx:c1fb2890 esi:c10f8d60 edi:063c ebp:0012 esp:c19a7b38 ds:0018 es:0018 ss:0018 Process iptables (pid:3092, stackpage ... .. . Kernel panic:Aiee, killing interupt handler! At this point the machine is locked up with the keyboard lights flashing and can only be accessed by rebooting. The module I am using was downloaded from the LEAF site under the Bering section. Unfortunately I have no facility to compile modules so any help would be appreciated. Andrew G. Gray MCSE Phone: (07) 4124 6303 Mobile: 0418 734 078 --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Problems with 3c509.o module
At 10:39 AM 10/9/2003 +1000, Andrew Gray wrote: Hi all, I am trying to replace 2 of my current Dachstein firewalls with a Bering version. Each of these use 3c509 NICs which have been working fine for a couple of years under Dachstein but as soon as I boot the machines in Bering I get the following Kernel Panic: skput: over: c2837d85:0 put:60 dev;eth0 kernel BUG at skbuff.c:92! invalid operand: CPU:0 EIP: 0010:[] Not tainted EFLAGS: 10286 eax:00026 ebx:c10e8490 ecx:c1996000 edx:c1fb2890 esi:c10f8d60 edi:063c ebp:0012 esp:c19a7b38 ds:0018 es:0018 ss:0018 Process iptables (pid:3092, stackpage ... .. . Kernel panic:Aiee, killing interupt handler! At this point the machine is locked up with the keyboard lights flashing and can only be accessed by rebooting. The module I am using was downloaded from the LEAF site under the Bering section. Unfortunately I have no facility to compile modules so any help would be appreciated. First, we probably need a bit more detail on what versions of things you are using. Am I right in surmising that you downloaded an image of Bering-1.2 and the associated modules file from the Bering download area, that is, these packages: Bering_1.2_img_bering-1680.bin [or .exe] Bering_1.2_modules_2.4.20.tar.gz If not, be specific about what you are using. The LEAF site is a bit like Zork, with "twisty little passages" that sometimes lead you to obsolete or incorrect files, and the first thing to check is that you are using current and matching versions of things. Second, these kernel panics can be the result of hardware problems, not only of module problems. In your case, this is less likely (since the system runs OK with Dachstein), but you do want to check two possibilities: 1. A bad floppy disk. If you have not tried several different floppies, please do. 2. A RAM problem. 2.4.x kernels do use a bit more RAM than 2.2.x kernels, typically, so you want to make sure there is enough RAM on the system to handle Bering. (The "invalid operand" part of the panic message makes this a particularly tempting guess, BTW.) Finally, I know that it is hard to transcribe panic messages exactly, but the fragmentary nature of yours leaves me wondering where in boot/init this panic happens. "As soon as I boot" isn't really an answer to this, since it surely does not happen before the 3c509 module is loaded, and a lot happens before that (like actual booting; module installation doesn't happen until later, after init is running). The closing reference to "iptables" makes me think it is well after the NIC module is installed, perhaps when Shorewall is setting up its rules. You might want to clarify that part (for example, does the module think it finds and configures the NICs, earlier in the boot/init process)? If none of these suggestions leads tyou to a solution, please post a follow-up with additional information about your setup and exactly what Bering files you downloaded. (Unless, of course, someone else regognizes the problem from the description you posted and gives you a succinct answer.) --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] VIA vt6105
Hi! I have a network card based on the VIA VT6105 chip. I couldn't make it work whith the via-rhine.o module (from http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/2.4.20/net /) neither compiling the driver sources that came with in the card's diskette driver. (rhinefet.o) Has anybody make this netcard work with Bering. I'm using Bering uClibc 2.0 rc1. Cheers, Mariano Drzazga --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] ncurses5.lrp in Bering 1.2
At 03:08 PM 10/8/2003 +0200, Felix Theodor wrote:
Hallo!
does someone know why I get this Error "Error opening
terminal: Linux." when I start to init the screen?
I'm not exactly sure what you mean by "start to init the screen", but that
sort of erro message usually means that you are trying to run a program on
a terminal type ("Linux", or maybe "linux", is a terminal type used on vts)
that it does not know how to work with. Provide a bit more detail and I (or
someone else here) may be able to say more.
---
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
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] DNS with Bering in a small LAN
Hey how is everybody doing? Let see if you can spot me here with my problem. I use to work with Bering 1.2 for VLAN issues but now I want to configure an old machine as a firewall using the software shorewall which is include in Berig 1.2. I have downloaded the quick start guide for a simple configuration, a local net conected to the firewall (eth1) by a hub (local PCs and the firewall by eth1 are conected to the same hub) and the firewall conected to a cisco router machine provided by my cable operator (eth0) of course eth1 has the subnet address of the local net and eh0 has the same subnet address of the router. Also I have configurated all the machines within the local net with their gateway set to the IP address of the local interafce of the firewall (eth1). I have the following policies: local net ACCEPT net all DROP all all REJCET Them in the rules I have PORT RULE Source DEST ProtoDEST ACCEPT fw net tcp 53 ACCEPT fw net udp 53 # For ssh conection ACCEPT locfwtcp 22 ACCEPT locfwicmp 8 ACCEPT netfwicmp 8 ACCEPT fw loc icmp 8 ACCEPT fw net icmp 8 ACCEPT locfwtcp 80 ACCEPT locfwudp 53 ACCEPT locfwtcp 4662 ACCEPT netfwtcp 4662 ACCEPT fw net tcp 4662 ACCEPT fw loc tcp 4662 ACCEPT netfwudp 4672 ACCEPT locfwudp 4672 ACCEPT fw net udp 4672 ACCEPT fw loc udp 4672 #SMTP mail ACCEPT locfwtcp 25 ACCEPT netfwtcp 25 ACCEPT fw net tcp 25 ACCEPT fw loc tcp 25 #POP mail ACCEPT locfwtcp 110 ACCEPT netfwtcp 110 ACCEPT fw net tcp 110 ACCEPT fw loc tcp 110 and in the Masq option of the Shorwall menu I have #Interface SubnetAddress eth0 eth1 192.168.10.106 Where 192.168.10.106 is teh ip address of eth0 the file host.allow has ALL:192.168.30.0/24 where 192.168.30.0 is the subnet address of the internal net conected to eth1 so that any PC from that net can access to the services of the firewall, and reach the internet, am I wrong?. I have, at this point two questions: 1º) I don´t have any DNS configured in my local net (neither at the firewall (LEAF Router), dnscache etc...). In the PCs of the local net I have the addresses of the DNS servers that my cable operator gave me. SO now I don´t know if I have to configure a DNS server in my firewall (Leaf Router) or what, and If so how???. As I have understood in the Quickstart guide for two interfaces, The resolv.conf will be written as soon as you conect to your ISP 2) so now here comes the problem. From any computer of the local net I can ping the internal IP address of the cisco router(which is conected to the fw) and from the firewall(LEAF router) I can ping either the internal address of the cisco router or any local PC. The question here is that I can´t ping the external IP address of the cisco router or do a traceroute and when I try to open my web broser in any of my local PCs it doesn´t work. It says that it can open the website, and the same for the mailing tool Outlook 3) with Bering 1.2 and its shorewall, do I have to start the firewall with any command? or does it get set up automaticly by it self after the sistem is booted? if so, how can I get it started? Did I do anything wrong in my configuration of the firewall or in the desing of the net? Thanks for yor time falks ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] DNS with Bering in a small LAN
Hello ! > The question here is that I can´t ping the external IP > address of the cisco router or do a traceroute and > when I try to open my web broser in any of my local > PCs it doesn´t work. It says that it can open the > website, and the same for the mailing tool Outlook > From the above i assume that the local pc's are windows clients . if this is the case don't forget that you need to set up their (default) gateway and DNS server if you are not using a DHCP server The default gateway should be the Bering firewall and DNS the one given by your provider Stelios --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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] Re: [Bering] IDLE Problem (Michelle Konzack) - Active filter settings
Greetings, > > I have setup a dial out Bering firewall in a small office. Recently I > noticed that it often fails to hang up the modem even when all machines > on the internal network have been turned off for long past the timeout > value. Possibly this is because of the increased number of worms > hammering on the outside. I replaced pppd with the active-filter > version but had not researched how to implement it. I shall try your > active-filter line in /etc/ppp/options. Thanks very much for your post > and hope this solves the "no hang up" the modem problem. > I had the same problem (modem not hanging up due to incoming traffic) but with with an isdn modem Goggling through the net i found a SUSE article that had a active-filter sentence which works very good (at least in my case) The sentence is active-filter 'outbound and not icmp[0] == 3 and not tcp[13] & 4 != 0' Although the article refers to ipppd and isdn ,i think it will work the same for pppd with active filter support, put i have not tested yet Here is the link for future reference http://sdb.suse.de/en/sdb/html/fhassel_ppp_filtering.html Stelios --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php 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
