RE: [leaf-user] followup to interfaces / shorewall assist
Greg
Greg Playle wrote the following at 17:31 03.08.2003:
Erich:
The output was something like this:
Variables
eth
/proc/net/dev
60
NICS = 1
Count = 0
Count updated
1
Devs = 1
expr [ 1 -eq 60 -o 1 -eq 1 ]
OK, the loop breaks here because we expect exactly one eth device and we
found one. Now the question is why.
We get the variable $devs here
devs=`grep ${WHAT} ${WHERE} | wc -l`
and $NICS is
NICS=`grep ${WHAT} /etc/shorewall/interfaces | grep -v ^# | wc -l`
This looks to me like a correct behaviour.
The NICS are defined in the shorewall interfaces file, we are looking for a
line with 'eth' which is not a comment, I guess that is right in your case,
now the question stands why we are finding an eth interface in
/proc/net/dev which would not respect configuration.
This is where you can continue digging should you be so inclined.
Try the following
grep eth /etc/shorewall/interfaces | grep -v ^#
this will give you the line in the shorewall interfaces file whic assert
looks for. The next you could check is:
grep eth /proc/net/dev
This is the condition we check against. It looks like your set finds an eth
before it is ready...:-(
Thanks
Erich
THINK
Püntenstrasse 39
8143 Stallikon
mailto:[EMAIL PROTECTED]
PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01
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] followup to interfaces / shorewall assist
Greg At 19:32 30.07.2003 -0600, Greg Playle wrote: This is essentially what I ended up doing. As Mr. Sturdevant observed, card services do not come up in time. I added a script at the end of the boot sequence in rc2.d that restarts networking, dhcpd and shorewall, and suddenly Bob's your Uncle! Basically the raison d'etre for the assert script was exactly to prevent the interfaced not up situation. I would be interested on why it apparently failed. My own installation consists of 2 PCMCIA adapters, no ppp though, so the situation is a bit different. Would you mind to find out how long assert waits (if it does wait at all) and if not what happened exactly inside that tiny bit of code? Thanks Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
This is essentially what I ended up doing. As Mr. Sturdevant observed, card services do not come up in time. I added a script at the end of the boot sequence in rc2.d that restarts networking, dhcpd and shorewall, and suddenly Bob's your Uncle! I got the same clue from an article that appeared referenced at SlashDot, which discussed making a Linux-powered wireless access point from a single board computer that used CF cards for the main storage and PCMCIA cards for the wireless NIC and ethernet NIC. It acted primarily as a bridge. As I read the article, he had a sentence that mentioned card services not up yet, so eth0 not up yet, so restartand the blindingly obvious strikes. I said I'd pass on what I learned...maybe we could add this to the official howto, or some such? -Original Message- From: S Mohan [SMTP:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 03:30 To: Erich Titl; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject:RE: [leaf-user] followup to interfaces / shorewall assist If it is a question of interface not coming up, why not put the commands in if-up and in rmnologon in /etc/init.d, add the svi networking restart? Mohan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Erich Titl Sent: Monday, July 28, 2003 1:18 AM To: [EMAIL PROTECTED]; '[EMAIL PROTECTED]' Subject: Re: [leaf-user] followup to interfaces / shorewall assist Greg At 18:14 27.07.2003, Greg Playle wrote: Tom, Steve and George: Thank you; the information you gave was helpful. I checked a bit more; in short, eth0 does not come up on boot, but seems to take a while--perhaps longer than Erich Titl's script allows. I've got to check more on the script, as I'm not sure it delays as long as needed. Restarting networking, esp eth0, brings it up fine, and then I can manually launch dhcpd, after which all responds as it should. I'm able to ping the eth0 address (192.168.1.254) both from itself and from another machine (which obtained its IP from the dhcp server). What I'd like to accomplish is having this all come up without having to manually restart eth0 and dhcpd. What I think is going on is that the version of Erich's script I'm using doesn't wait 60 seconds, but runs to completion in about one second, so eth0 is still not up before the boot process continues. Since eth0 isn't yet up, networking, therefore dhcpd, don't work either. By the time boot completes, eth0 is up, and manual restart of networking on eth0 and on dhcpd work. I guess you must have modified the assert script as it is written for 2 interfaces and would run at a wrong init level. I believe it does not run in your case for some reason difficult to diagnose unless you tell us more about the way you implemented it. I am pretty certain your problems stem from the interface not being up and the assert script failing for some reason. It does not have a backup routine, so it would be saved by etc I guess. So here is the stupid question, did you back it up? regards Erich THINK Puntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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 sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
An earlyer message indicated that iot was a 3c589. This is a PCMCIA card. As I recall, card services do not usually start until after networking. This could be the out of order issue. JamesS At 02:59 PM 7/28/03 +0530, S Mohan wrote: If it is a question of interface not coming up, why not put the commands in if-up and in rmnologon in /etc/init.d, add the svi networking restart? Mohan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Erich Titl Sent: Monday, July 28, 2003 1:18 AM To: [EMAIL PROTECTED]; '[EMAIL PROTECTED]' Subject: Re: [leaf-user] followup to interfaces / shorewall assist Greg At 18:14 27.07.2003, Greg Playle wrote: Tom, Steve and George: Thank you; the information you gave was helpful. I checked a bit more; in short, eth0 does not come up on boot, but seems to take a while--perhaps longer than Erich Titl's script allows. I've got to check more on the script, as I'm not sure it delays as long as needed. Restarting networking, esp eth0, brings it up fine, and then I can manually launch dhcpd, after which all responds as it should. I'm able to ping the eth0 address (192.168.1.254) both from itself and from another machine (which obtained its IP from the dhcp server). What I'd like to accomplish is having this all come up without having to manually restart eth0 and dhcpd. What I think is going on is that the version of Erich's script I'm using doesn't wait 60 seconds, but runs to completion in about one second, so eth0 is still not up before the boot process continues. Since eth0 isn't yet up, networking, therefore dhcpd, don't work either. By the time boot completes, eth0 is up, and manual restart of networking on eth0 and on dhcpd work. I guess you must have modified the assert script as it is written for 2 interfaces and would run at a wrong init level. I believe it does not run in your case for some reason difficult to diagnose unless you tell us more about the way you implemented it. I am pretty certain your problems stem from the interface not being up and the assert script failing for some reason. It does not have a backup routine, so it would be saved by etc I guess. So here is the stupid question, did you back it up? regards Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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 sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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 sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
Seems that I'm jumping in late on this thread, but as I recall on laptops, especially those using PCMCIA cards, card services have to start before the networking drivers are loaded. Otherwise there is no card to bind the driver to. Onboard nics in laptops are handled differently at the bios level. However I could be mistaken in this. Try loading the modules in the reverse order and see if that helps. Just my two penny's worth. Danny Carter - Original Message - From: JamesSturdevant [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 29, 2003 8:41 AM Subject: RE: [leaf-user] followup to interfaces / shorewall assist An earlyer message indicated that iot was a 3c589. This is a PCMCIA card. As I recall, card services do not usually start until after networking. This could be the out of order issue. JamesS At 02:59 PM 7/28/03 +0530, S Mohan wrote: If it is a question of interface not coming up, why not put the commands in if-up and in rmnologon in /etc/init.d, add the svi networking restart? Mohan --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
If it is a question of interface not coming up, why not put the commands in if-up and in rmnologon in /etc/init.d, add the svi networking restart? Mohan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Erich Titl Sent: Monday, July 28, 2003 1:18 AM To: [EMAIL PROTECTED]; '[EMAIL PROTECTED]' Subject: Re: [leaf-user] followup to interfaces / shorewall assist Greg At 18:14 27.07.2003, Greg Playle wrote: Tom, Steve and George: Thank you; the information you gave was helpful. I checked a bit more; in short, eth0 does not come up on boot, but seems to take a while--perhaps longer than Erich Titl's script allows. I've got to check more on the script, as I'm not sure it delays as long as needed. Restarting networking, esp eth0, brings it up fine, and then I can manually launch dhcpd, after which all responds as it should. I'm able to ping the eth0 address (192.168.1.254) both from itself and from another machine (which obtained its IP from the dhcp server). What I'd like to accomplish is having this all come up without having to manually restart eth0 and dhcpd. What I think is going on is that the version of Erich's script I'm using doesn't wait 60 seconds, but runs to completion in about one second, so eth0 is still not up before the boot process continues. Since eth0 isn't yet up, networking, therefore dhcpd, don't work either. By the time boot completes, eth0 is up, and manual restart of networking on eth0 and on dhcpd work. I guess you must have modified the assert script as it is written for 2 interfaces and would run at a wrong init level. I believe it does not run in your case for some reason difficult to diagnose unless you tell us more about the way you implemented it. I am pretty certain your problems stem from the interface not being up and the assert script failing for some reason. It does not have a backup routine, so it would be saved by etc I guess. So here is the stupid question, did you back it up? regards Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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 sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
On Sun, 2003-07-27 at 09:14, Greg Playle wrote: 4: eth0: BROADCAST,MULTICAST mtu 1500 qdisc noop qlen 100 link/ether 00:60:08:b1:ea:f5 brd ff:ff:ff:ff:ff:ff Demonstrates that eth0 isn't configured yet. * /etc/init.d/networking restart should have been eth0 instead of restart Reconfiguring network interfaces: Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Stopping Shorewall...Processing /etc/shorewall/stop ... Processing /etc/shorewall/stopped .. And sincd eth0 hasn't come up yet, Shorewall won't start. The Bering configuration of Shorewall requires all interfaces to be started before Shorewall starts. -Tom -- Tom Eastep\ Shorewall - iptables made easy Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
Greg At 18:14 27.07.2003, Greg Playle wrote: Tom, Steve and George: Thank you; the information you gave was helpful. I checked a bit more; in short, eth0 does not come up on boot, but seems to take a while--perhaps longer than Erich Titl's script allows. I've got to check more on the script, as I'm not sure it delays as long as needed. Restarting networking, esp eth0, brings it up fine, and then I can manually launch dhcpd, after which all responds as it should. I'm able to ping the eth0 address (192.168.1.254) both from itself and from another machine (which obtained its IP from the dhcp server). What I'd like to accomplish is having this all come up without having to manually restart eth0 and dhcpd. What I think is going on is that the version of Erich's script I'm using doesn't wait 60 seconds, but runs to completion in about one second, so eth0 is still not up before the boot process continues. Since eth0 isn't yet up, networking, therefore dhcpd, don't work either. By the time boot completes, eth0 is up, and manual restart of networking on eth0 and on dhcpd work. I guess you must have modified the assert script as it is written for 2 interfaces and would run at a wrong init level. I believe it does not run in your case for some reason difficult to diagnose unless you tell us more about the way you implemented it. I am pretty certain your problems stem from the interface not being up and the assert script failing for some reason. It does not have a backup routine, so it would be saved by etc I guess. So here is the stupid question, did you back it up? regards Erich THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
Greg Playle wrote: Thank you; the information you gave was helpful. I checked a bit more; in short, eth0 does not come up on boot, but seems to take a while interfaces that take ages to come up are usually waiting for some dhcp server to answer.. 8-) Your eth0 should configure nearly instantly, or else something is amiss. Here is your problem to solve, IMO. Perhaps post a bit more diagnostics of this phase of the bootup. Restarting networking, esp eth0, brings it up fine, and then I can manually launch dhcpd, after which all responds as it should. I'm able to ping the eth0 address (192.168.1.254) both from itself and from another machine (which obtained its IP from the dhcp server). Bering Gurus are needed here. Good luck. /steve --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
I tried building in a simple wait 60 seconds script, which ran at S29. That didn't help. I've got something out of order, but I'm still not sure what. What diagnostics would be useful here? -Original Message- From: Steve Wright [SMTP:[EMAIL PROTECTED] Sent: Sunday, July 27, 2003 14:39 To: [EMAIL PROTECTED] Subject:Re: [leaf-user] followup to interfaces / shorewall assist Greg Playle wrote: Thank you; the information you gave was helpful. I checked a bit more; in short, eth0 does not come up on boot, but seems to take a while interfaces that take ages to come up are usually waiting for some dhcp server to answer.. 8-) Your eth0 should configure nearly instantly, or else something is amiss. Here is your problem to solve, IMO. Perhaps post a bit more diagnostics of this phase of the bootup. Restarting networking, esp eth0, brings it up fine, and then I can manually launch dhcpd, after which all responds as it should. I'm able to ping the eth0 address (192.168.1.254) both from itself and from another machine (which obtained its IP from the dhcp server). Bering Gurus are needed here. Good luck. /steve --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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 sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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] followup to interfaces / shorewall assist
Steve Wright wrote: I know Linux and WISP-DIST, but I am not familiar with Bering, per se. Try these things ; boot Bering, and see if pump is running on eth0. It should not be. Start from scratch, with a perfectly clean image and have another go. Write a little script that that restarts the network - basically what you are doing now, but automatically. For that matter, removing pump entirely from the list of packages to be loaded would be indicated. PPP has it's own method to assign an IP address to the connecting device, and with eth0 being the only Ethernet interface, and the internal at that, then Pump doesn't need to be on the disk. --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 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
