> For Q2
> Pls try
> rdr em1 0/0 port 6881 -> 192.168.2.1 port 6881 tcp
> Instead

Works like a charm. Thanks!


regards,

Derkjan

> -----Original Message-----
> From: Derkjan de Haan [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 25, 2004 3:20 PM
> To: [EMAIL PROTECTED]
> Subject: ipfilter
>
> I recently installed FreeBSD 4.9 on my home firewall/server, and I'm
> using the bundled ipfilter as firewall package of choice. However, I
> came across a few oddities; maybe someone can shed some light on these ?
>
> 1) For active FTP to work, I noticed I have to specify the back-end
> network, as well as the address of the server itself. I mean this most
> elegant syntax
>
> map em1 0/0 -> 0/32 proxy port ftp ftp/tcp
>
> is supposed to work if I understood the FAQ correctly, but is does not.
> This only works for FTP traffic originating from the firewall itself,
> but not for hosts behind it. Instead I have to use this:
>
> map em1 <extip>/32 -> 0/32 proxy port ftp ftp/tcp
> map em1 192.168.2.0/24 -> 0/32 proxy port ftp ftp/tcp
>
> 2) The 0/32 syntax can apparently not be used in rdr rules. Is this
> intentionally ? My external IP address gets assigned by DHCP, so I sort
> of dislike the idea of hardcoding my current address in the firewall
> rules.
>
> This doesn't seem to work, although the syntax is accepted:
>
> rdr em1 0/32 port 6881 -> 192.168.2.1 port 6881 tcp
>
> This does:
>
> rdr em1 <extip>/32 port 6881 -> 192.168.2.1 port 6881 tcp
>
> 3) The same question applies to ipf syntax. Is there some shorthand for
> the current address of an interface, like 0/32 exists for ipnat ?

Reply via email to