On 8/27/10 11:46 AM, Carlos Siso wrote: > 1.- All the router/firewall hardware, including the network cards has > been replaced and the problem persists.
What about the cables?
> The weird part:
>
> 1.- Disabling one of the internal network interfaces ("ifdown eth1" or
> "ifdown eth2") fix the problem for the other one.
Are the two internal networks bridged outside of the gateway/router?
Are you sure?
> 2.- While pinging from inside the router/firewall to the Internet, the
> packet loss, when pinging from a PC in the "loc" or "cus" zones, are
> reduced considerably (at almost 1% packed loss on an 10 minute ping
> period). Actually, I keep a console session on the router/firewall
> pinging the default gateway at the Internet to have things working (more
> or less).
>
I think that you need to monitor the traffic with a packet stiffer and
see what is happening on the links. And be sure to look at the ethernet
headers and ARP traffic.
-Tom
--
Tom Eastep \ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all of the passengers in his car
http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
