[Firehol-support] Routing between virtual interfaces

M. O. mofog at hotmail.com
Wed Jan 28 16:07:20 GMT 2009

Sorry it took me so long to get back to you.

IP forwarding is already enabled and the pinging "feels" to work better when firehol was turned off by calling /etc/init.d/firehol stop.
Still, how could the routing possibly work though the firewall, and therefore the routing, has been shut down?
I'm really clueless here. If you have any more suggestions, I'd appreciate your help. But if it gets too complicated to determine the problem I'd just merge the networks. Could this also be caused by a malfunctioning switch?



> Date: Sun, 25 Jan 2009 20:38:19 +0000
> Subject: Re: [Firehol-support] Routing between virtual interfaces
> From: cefrodrigues at gmail.com
> To: mofog at hotmail.com
> CC: firehol-support at lists.sourceforge.net
> On Sun, Jan 25, 2009 at 11:59 AM, M. O. <mofog at hotmail.com> wrote:
> > Again: it works "sometimes". For example alpha can ping delta, but beta
> > can't. Wait a few minutes and the behaviour may be vice versa. Even more
> > interesting is that delta happens to be a network printer with a web
> > interface. Even when I'm able to reach the printer by ping, I may not be
> > able to access it's web interface (things are getting spooky here, don't
> > they?).
> You should check if that also happens with forwarding enabled ("echo 1
> > /proc/sys/net/ipv4/ip_forward") but without any kind of firewall. It
> may be a problem with something firewall-related (like connection
> tracking) or it may be something else entirely.
> -- 
> Carlos Rodrigues

UNO - Online gegen andere spielen! Spiel mit!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.firehol.org/pipermail/firehol-support/attachments/20090128/76accaf9/attachment-0003.html>

More information about the Firehol-support mailing list