--On Sunday, January 26, 2003 9:26 PM +0100 Eric Wolzak <[EMAIL PROTECTED]> wrote:
Shorewall can also block the reconnection attempt. Typically, the externel ethernet interface in a PPPoE setup isn't defined to Shorewall. This works fine so long as the PPPoE connection is established before Shorewall starts and doesn't disconnect. If it disconnects, you may need to "shorewall clear" before a new connection can be established.Hello Arcana, rayOn Sunday 26 January 2003 13:24, Ray Olszewski wrote:> Third, your immediate problem is that when the connection goes down, > your keepalive script does not restart it. Nor does your executing the > same command (/etc/init.d/networking restart) from the command line. > Since that is the command to stop, then restart, all interfaces, this > command should work ... or at least it should do *something*.Anyhow as soon as the connection goes down the pppd daemon will try to restart it immediately. The reconnecting might fail for several reasons for example. password server at provider out of order hardware problem problem with your modem ( this is probable because you had to powercycle the modem). Don't forget that the "lowest level" connection between your modem and the endpoint at your provider is not controlled by the pppd daemon ( this is at a "higher" level
One way to fix that would be to define a new Zone call 'void', assign the external ethernet interface to 'void' in /etc/shorewall/interfaces and include a policy of "fw void ACCEPT".
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
Shoreline, \ http://www.shorewall.net
Washington USA \ [EMAIL PROTECTED]
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
------------------------------------------------------------------------
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
