Re: Routing with 4 NICs breaks

[Marco Feenstra <mfeenstra@suqata.net>]

Rob Foster wrote:

>Hi,
>
>I'm having a problem. I have 3 subnets connected to an openbsd 3.6 router.
>internet_if     = "dc0"
>office_if       = "ste3"
>dmz_if          = "ste2"
>warroom_if      = "ste0"
>
>
>2 things break in the warroom:
>
>192.168.3.10# ping 192.168.0.3
>Request timed out.
>192.168.3.10# ping 192.168.1.74
>Reply from 192.168.1.74: bytes=32 time=6ms TTL=127
>192.168.3.10# ping google.com
>Reply from 216.239.57.99: bytes=32 time=111ms TTL=237
>  
>
I only see one failure which is the ping 192.168.0.3 am I misreading 
something ?

>1 thing breaks in the dmz (yes, not quite a dmz right now):
>192.168.0.3# ping 192.168.3.10
>Request timed out.
>192.168.0.3# ping 192.168.1.74
>Reply from 192.168.1.74: bytes=32 time=6ms TTL=127
>192.168.0.30# ping google.com
>Reply from 216.239.57.99: bytes=32 time=111ms TTL=237
>
>Why is this happening. Why can't the warroom talk to the dmz or the
>internet while the office can?
>
>everyone should talk to everyone, until I change the pf ruleset!
>  
>
I assume you have disable pf.conf and and (personal) firewall's on the 
source and target systems.
What happens if you where to ping these systems from the firewall / 
router itself, sometimes on windows to really disable a personal 
firewall is to completly uninstall a personal firewall :)
And what happens when you ping from the:
    192.168.3.10->192.168.3.1
    192.168.3.10->192.168.0.1
    192.168.0.3->192.168.0.1
    192.168.0.3->192.168.3.1
An last but not least
192.168.3.10#traceroute -n 192.168.0.3
192.168.0.3#traceroute -n 192.168.3.10

See if that helps you any further

Cheers,
Marco Feenstra