关于创建指向本机特定端口的局域网虚拟网络地址的技术咨询

Hey Lance, this is a super practical use case—luckily, it’s totally achievable with a few network configuration tweaks depending on your operating system. Let me walk you through the step-by-step methods for Linux, Windows, and macOS:

Linux Method #

1. Add a dummy virtual IP to your network interface
   Pick an unused IP on your LAN subnet (e.g., 192.168.1.100 if your LAN uses 192.168.1.x). Run this command (replace eth0 with your actual interface name, like wlan0 for Wi-Fi):

   sudo ip addr add 192.168.1.100/24 dev eth0
   

   To make this persistent across reboots, add the command to your /etc/rc.local file or use your distro-specific network manager.

2. Set up port forwarding with iptables
   Use DNAT to route traffic aimed at the virtual IP to your host’s local port. For example, to forward TCP traffic on port 80 of the virtual IP to port 8080 on 127.0.0.1:

   sudo iptables -t nat -A PREROUTING -d 192.168.1.100 -p tcp --dport 80 -j DNAT --to-destination 127.0.0.1:8080
   

   You’ll also need a SNAT rule to ensure return traffic routes correctly:

   sudo iptables -t nat -A POSTROUTING -d 127.0.0.1 -p tcp --dport 8080 -j SNAT --to-source 192.168.1.100
   

   Save your iptables rules with sudo iptables-save > /etc/iptables/rules.v4 (or your distro’s equivalent) to keep them after a reboot.

Windows Method #

1. Add a secondary IP address
   Open Command Prompt as Administrator and run (replace "Ethernet" with your network adapter name, found via netsh interface ipv4 show interfaces):

   netsh interface ipv4 add address "Ethernet" 192.168.1.100 255.255.255.0
   

2. Configure port proxying
   Set up the forwarding rule to map the virtual IP’s port to your local port:

   netsh interface portproxy add v4tov4 listenaddress=192.168.1.100 listenport=80 connectaddress=127.0.0.1 connectport=8080
   

   Verify the rule exists with netsh interface portproxy show all. To make this persistent, create a batch file with these commands and add it to your Startup folder, or use Task Scheduler to run it on boot.

macOS Method #

1. Add an alias IP to your interface
   Open Terminal and run (replace en0 with your interface name, found via ifconfig):

   sudo ifconfig en0 alias 192.168.1.100/24
   

   To persist this, add the command to /etc/rc.local (create the file if it doesn’t exist) or use a Launch Daemon.

2. Set up port forwarding with pfctl
   Create an anchor file for your rules, e.g., /etc/pf.anchors/com.virtualport, with:

   rdr pass on en0 inet proto tcp from any to 192.168.1.100 port 80 -> 127.0.0.1 port 8080
   

   Edit /etc/pf.conf to include the anchor (add this line at the bottom):

   load anchor "com.virtualport" from "/etc/pf.anchors/com.virtualport"
   

   Enable the rules with:

   sudo pfctl -ef /etc/pf.conf
   

   To make pfctl start automatically on boot, enable it with sudo sysctl net.inet.ip.forwarding=1 and add the pfctl command to your startup scripts.

Quick Notes #

• Make sure the virtual IP you choose isn’t already in use on your LAN (check with ping 192.168.1.100 before setting it up).
• Ensure your host’s firewall allows incoming traffic on both the virtual IP’s port and the local target port.
• Test from another machine on the LAN by connecting to 192.168.1.100:80—it should route to your host’s 127.0.0.1:8080.

备注：内容来源于stack exchange，提问作者Lance Collins