On 6/28/05, S. Klapprott <sascha dot klapprott at freenet dot de> wrote:
> Hi,
> 
> yes - thats wat i want :)
> 
> I've done the outbound nat like the tut said:
> 
> http://home.arcor.de/sashxp/etc/m0n0.GIF
> 
> I've also add an alias ( 192.168.178.2 ) - but if I try to ping
> 192.168.178.1 from my m0n0 it says "no route to host" what route should I
> create ?
> 
> 
> 
> On 6/27/05, Jeroen Visser <monowall at forty dash two dot nl> wrote:
> > Sascha,
> >
> > Same problem here.
> > Adding routes to the exec.php page of m0n0wall does not help.
> 
> is this what you're attempting?
> http://wiki.m0n0.ch/wikka.php?wakka=AccessingModemOutsideFirewall
> 
> -Chris
> 

I've just tried the steps in the above link and it works for me at
least - ping doesn't work from m0n0 (I too get no route to host), but
I can still browse to the GUI of my ADSL modem and ping it from a PC
connected to the LAN.

I will just say in summary that it has to do with PPPoE using a
virtual interface and your modem being accessible only via the
physical interface.

My logs show denied pings out via sis0:
Block   18:03:45.320859  	sis0  	192.168.178.2  	192.168.178.1  	ICMP
Block	18:03:44.320016 	sis0 	192.168.178.2 	192.168.178.1 	ICMP
Block	18:03:43.319184 	sis0 	192.168.178.2 	192.168.178.1 	ICMP

whereas if I enable logging on the pass rule for the LAN interface, I
get the following (no auto default LAN -> any, I create outbound rules
as required):
Pass	18:20:58.633988 	sis0 	192.168.178.1, port 80 	10.1.1.10, port 2782 	TCP
Pass	18:20:58.632624 	LAN 	10.1.1.10, port 2782 	192.168.178.1, port 80 	TCP

Note how ipfilter is returning the physical interface for sis0 (which
is where the virtual pppoe WAN interface lives), rather than WAN.

So, try the ping from an internal machine, rather than m0n0 itself and
failing that try to browse to the modem anyway.

--g'luck
gm