Erik Nørgaard wrote:
.. snip ..
Well, my suggestion is not to exhaust your precious /28 address space
right away. And don't make your life unnecessary difficult, why choose
the addreses in the middle for bimap?
Rather than using all your external ip's right away I would save some
for
Juergen Heberling wrote:
Due to historical reasons I can not just take a /29 or /30 block out of
the middle of the cidr I will ultimately use -- this FreeBSD server will
implement a firewall on an existing connection replacing an old Cisco
router that only NAT'd. So I will see if things can
: Re: ipnat syntax error?
Juergen Heberling wrote:
Due to historical reasons I can not just take a /29 or /30 block out of
the middle of the cidr I will ultimately use -- this FreeBSD server will
implement a firewall on an existing connection replacing an old Cisco
router that only NAT'd
fbsd_user wrote:
You can use this format of the ipnat map command
map dc0 10.0.10.1/29 - 20.20.20.5-20.20.20.7
.. snip ..
The above version of the command also results in a syntax error at the -.
Juergen
___
freebsd-questions@freebsd.org mailing
Juergen Heberling wrote:
/etc/ipnat.rules contains:
map em0 192.168.1.0/24 - 204.134.75.1-10
.. snip ..
I tried your suggestion of using the cidr notation format and that work;
thank you!
However I am concerned about overlapping mappings in the cidr range with
host-to-host maps - my cidr
Juergen Heberling wrote:
Could someone please check me on this ...
fw1# ipnat -CFn -f /etc/ipnat.rules
0 entries flushed from NAT table
1 entries flushed from NAT list
syntax error error at -, line 1
/etc/ipnat.rules contains:
map em0 192.168.1.0/24 - 204.134.75.1-10
.. snip ..
line 1 in the
Erik Nørgaard wrote:
Juergen Heberling wrote:
Could someone please check me on this ...
fw1# ipnat -CFn -f /etc/ipnat.rules
0 entries flushed from NAT table
1 entries flushed from NAT list
syntax error error at -, line 1
/etc/ipnat.rules contains:
map em0 192.168.1.0/24 - 204.134.75.1-10
