[ previous ] [ next ] [ threads ]
 
 From:  Steve Yates <steve at teamITS dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Bridging - can't ping
 Date:  Thu, 01 Sep 2005 20:14:03 -0500
My setup, with 1.2b9:

WAN - 10.0.0.0/24 (WAN has IP 10.0.0.3, gateway 10.0.0.1)
OPT1 - bridged to WAN (PCs have 10.0.0.0/24)
LAN - 192.168.1.0/24 (not connected to either WAN or OPT1)

WAN and OPT1 are bridged, with filtering of bridged packets enabled. 
From m0n0wall, if I...

ping 10.0.0.1 (located on WAN) - "no route to host"
ping 10.0.0.2 (located on OPT1) -  3 success plus ~10 random "duplicates"
ping any Internet IP (located on WAN) - "no route to host"

I assume the duplicate packets seen by m0n0wall is it being confused
over seeing the replies on both sides of the bridge.  But, how come I
cannot ping to the Internet?  Pinging from any PC on OPT1 works fine. 
The firewall is set to allow everything, and there are no entries in the
log.  If I add a static route to OPT1 for 10.0.0.1/32 using gateway
10.0.0.3, I can ping 10.0.0.1 successfully, with ~4 duplicate replies.

	One eventual goal is to get the NTP client working.  Currently
with the time zone set to CST6CDT or America/Chicago, m0n0wall logs show the
time 5 hours behind the PC clock setting.

Thanks,

 - Steve Yates
 - ITS, Inc.
 - Don't use a big word where a diminutive one will suffice.

~ Taglines by Taglinator 4 - www.srtware.com ~