[ previous ] [ next ] [ threads ]
 From:  Manuel Kasper <mk at neon1 dot net>
 To:  Martin Holst <mail at martinh dot dk>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: Small bug: NAT rules with optional interfaces
 Date:  Mon, 10 May 2004 21:32:51 +0200
On 10.05.2004 21:01 +0200, Martin Holst wrote:

> Latest betas include the possibility to use OPT-interfaces as extra
> WAN-interfaces (under "Advanced outbound NAT").
> You can choose OPT interfaces when creating NAT-rules - however the
> drop-down menu "External address" only lets you choose WAN-address
> or predefined addresses from "Server NAT".
> Shouldn't the menu include OPTx-address?

Yeah, why not - the option "WAN address" for inbound NAT is
translated to 0/0 in the ipnat ruleset anyway (because the WAN IP
address may be dynamic), so all it would take is renaming to
"Interface address" or something (and some adjustments to the

> And a suggestion as well: Since OPT-interfaces can be used as
> WAN-interfaces, how about including WAN connectivity options on OPT
> configuration pages? (PPPoE, DHCP etc.)
> You could use have a check box named "Use as WAN" enabling all the
> extra connectivity options.

That unfortunately would require the overhaul of just about every
single file in m0n0wall, as there are so many historic assumptions
about the special function of the WAN interface. Besides, it would
also raise questions like what happens if you have two default
gateways, and so on. So no, this is not going to happen.

- Manuel