User Details
- User Since
- May 22 2017, 8:55 PM (361 w, 1 d)
Dec 3 2017
Can anyone test this little patch?
Nov 23 2017
I know the right place for arp_accept is in "_net_link_ether_inet", but I do not know how to achieve it.
Jul 23 2017
After small changes to the config file, everything works great.
Jul 22 2017
http://85.187.224.234:3000 <--- Expected content. (Black page for the outside world)
http://85.187.224.234:80 <--- ipfw fwd returns this content (TEST OK)
Apache 2.4.25 listens on ports 80,443,3000.
I try to access a random web site from a PC in LAN and the reply comes from Apache port 80, not from port 3000.
Before I used ipfw nat I did a lot of tests with ipfw fwd.
I upgrade kernel to 11-RC3 and made a new test with ipfw fwd.
Jul 21 2017
I have never tested ipfw fwd on a external interface, because:
- I redirect only traffic for expired users, destination port 80 to ISP warning page. After first check (internal interface) this traffic dropped and never have going to second ipfw check on external interface.
- I allow traffic on a external interface with first rule. I try to make minimal ipfw rules for high performance router.
I want to redirect all outgoing traffic from LAN to destination IP:any port 80 ---> localhost:3000
It seems simple. Example rule:
ipfw nat 3000 config redirect_port tcp localhost:3000 80
Jul 20 2017
Can anyone check this functionality and add it to the kernel?