Hi Tom,
Thanks! you were right all this time, we had a router in a back room which was
the culprit. It was the bridge between the 10.1.50.0 and the 74.2.235.0. Shut
it off, and scenario is fix, thanks for your time and patience.
Thanks again
________________________________
From: Tom Eastep <[email protected]>
To: Shorewall Users <[email protected]>
Sent: Wednesday, September 2, 2009 11:45:28 AM
Subject: Re: [Shorewall-users] LOC traffic shows up as NET traffic
Surge wrote:
> Hi,
> I agree with you. But it's odd because I can't find where on the
> network I would have this.... here's the run down of what I have.
>
> I have 2 locations where I have routers in my building. Room 1 has a
> router for the 192.168.2.0, same room another router for the 10.1.50.0.
> and another router for the 74.2.235.0. They all have a link to my
> warehouse - Room 2, which has a router for the 74.2.235.0, same room
> another route with 24 ports, 12 ports are configured for the
> 192.168.2.0, and the other 10.1.50.0.
>
> Now just for grins I also disabled some policies in the policy file, now
> I should be able to ping between 192.168.2.0 and 10.1.50.0. Even though
> I understand that we a re looking for the culprit which is creating a
> bridge between the 74.2.235.0 and 10.1.50.0, right?
If you want to test without the bridging getting in the way, set
arp_filter=1 on your interfaces (/etc/shorewall/interfaces).
-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 \________________________________________________
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users