natd.conf problem (was: natd problem (but close!) )

The Bean beantaxi at
Fri Dec 26 15:19:10 PST 2003

> You're getting the idea. You're trying to set up a static nat configuration
> instead of a dynamic nat. Dynamic NAT uses one IP for all traffic from the
> internal systems. Perhaps I should've stated it this way first, my bad. For
> Static Nat setups, a gateway has to have the redirected IP associated with
> it's external nic. It's best if this is an aliased IP so that no traffic to
> the gateway is lost. Then redirect that address to the internal system.
> specifically,  section 19.13.5 Address Redirection describes this best.

Indeed, from 19.3.5 (which I just checked) . . .

"The external IP addresses on the natd machine must be active and aliased 
to the external interface."

I'm sure I read this section. Since that quote was right at the end, I'm 
also sure I got lost before I got to that part . . . but since I checked
that section off my list, I probably never reread it.

Anyway, I took a stab at this a while ago, and sure enough, it fixed the problem.

"Your bad"? I beg to differ -- you're the guy who fixed this!!! And it's been 
bugging me for weeks. Aaaaaaaaaaaaaaaahhhhhhhhhhhhhhhh!!!!!!!!!!!!!!!!!!!!!!!

Thanks so much Micheal.
- The Bean
> "Address redirection is useful if several IP addresses are available, yet
> they must be on one machine. With this, natd(8) can assign each LAN client
> its own external IP address. natd(8) then rewrites outgoing packets from the
> LAN clients with the proper external IP address and redirects all traffic
> incoming on that particular IP address back to the specific LAN client. This
> is also known as static NAT"
> --
> Micheal Patterson
> Network Administration
> TSG Incorporated
> 405-917-0600

Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.

More information about the freebsd-questions mailing list