[ previous ] [ next ] [ threads ]
 From:  Peter Allgeyer <allgeyer at web dot de>
 To:  "S. Klapprott" <sascha dot klapprott at freenet dot de>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: AW: [m0n0wall] Help to get this route to work ?
 Date:  Wed, 29 Jun 2005 12:24:01 +0200
Servus Sascha!

Am Mittwoch, den 29.06.2005, 11:32 +0200 schrieb Peter Allgeyer:
> The fact that the external interface is sis0 (and not ng0), as
> googl3meister stated, is interesting. Maybe there has to be an
> additional rule for sis0:
> pass out quick on sis0 from any to any keep state
> I can try this out, if you want.

OK, have tried it. googl3meister was right. Besides adding an IP address
to your sis0 interface, you'll have to type these two rulesets in

echo "@7 pass out quick on sis0 from any to any keep state" | ipf -f -
echo "map sis0 ->" | ipnat -f -

Since there isn't any NAT configured for interface sis0, you don't have
to change any NAT settings for the WAN interface (as described in
Beside this, adding a rule for the sis0 interface is mandatory!

If everything works fine, add these lines to the configfile:
<shellcmd>ifconfig sis0 inet alias</shellcmd>
<shellcmd>echo "@7 pass out quick on sis0 from any to any keep state" |
ipf -f -</shellcmd>
<shellcmd>echo "map sis0 ->" | ipnat -f

One problem will arise: <shellcmd>...</shellcmd> will only be executed
at system start, not when you change any settings of your firewall rules
(adding, deleting, changing rulesets). So you'll have to type the
ruleset lines every time after you've changed your ruleset.

If we would have the possibility to define alias interfaces (in this
special case, a normal interface configuration for sis0 would be
enough), this problem is going away. Maybe a nice feature for past 1.2.

Ciao ...
	... PIT ...

 copyleft(c) by |           There are no threads in a.b.p.erotica, so
 Peter Allgeyer |   _-_     there's no gain in using a threaded news
                | 0(o_o)0   reader. (Unknown source)