Re: IPFW on CURRENT: NAT forwarding exposes internal IP!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 29 Sep 2016 16:00:10 +0300 Daniel Kalchev schrieb: Yes, your are right :-) Yes, I'm wrong, it is not NAT :-( Thanks a lot, Oliver > It looks like your httpd server is doing a redirect to your internal IP > address,

Re: IPFW on CURRENT: NAT forwarding exposes internal IP!

It looks like your httpd server is doing a redirect to your internal IP address, which it thinks is it’s ServerName. Don’t think NAT has anything to do with it. Daniel > On 29.09.2016 г., at 15:47, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash:

IPFW on CURRENT: NAT forwarding exposes internal IP!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Despite other problems with IPFW and its documentation regarding NAT, I face a serious and disturbing problem. I run a NanoBSD based router/firewall project of my own, running CURRENT (FreeBSD 12.0-CURRENT #1 r306333: Mon Sep 26 08:36:02 CEST