Why not let the traffic from myself also obey the rule. When I see traffic from other devices to my WAN IP (within a specified port), redirect to another IP. You're basically saying "when I see traffic from me to my WAN IP (which is correct, as you improperly noted) - DNAT to another IP"? As I know, It is possible to let traffic to 127.0.0.1:(a port) redirect to another IP. The traffic would only pass the firewall during OUTPUT. I don't think what you're asking is possible with a firewall rule. NAT Loopback unifies subscribe file for public and local access, but now a subscribe file with internal IP is still required for OpenWrt itself, and I have to maintain two versions of subscribe files. So, I have to prepare two versions of subscribe files, One for the OperWrt and another for the rest devices. Navigate to Manage Rules NAT Policies submenu. If a LAN-side client can make a connection attempt to the public IP address of your gateway, and it successfully gets a response back from the LAN-side server you had set up a port mapping for, then your gateway is doing NAT loopback. Loopback Policy using WAN Interfaces IP Address Login to the SonicWall management GUI. NAT Loopback is a convenient way to test port forwarding when there is only a single router, because using the Public IP address in a connection will look exactly like someone connecting from the internet. But there are also sub links in the content, I have to change all of them. It MUST be done locally in your NAT gateway. Yes, If I change the address to internal IP, it works. Wait.why don't you change the address in the script? If it's reasonable, please handle it to the developers. Just like "NAT Loopback" option, thanks to which I don't have to set up it manually. "lo loopback", to let OpenWrt itself to follow. When setting the port forwarding rules, there could be an option called, e.g. It's really a good point to start to learn the routing knowledge.īy the way, is it a reasonable recommendation that adding an option for this to the luci's UI. I want to figure this out first before I try other menthods. So could you please give me example of how to write a customer rule for OpenWrt itself? (i.e. No, I guess luci's UI just don't let beginners to do this easily. Check if NAT loopback is enabled and click OK (allows users connected to any interface to use the NAT rule too) 1.2 Add a Firewall rule to allow the NAT (Port Forwarding) 1.2. Am I right? ( resolves to the public IP of OpenWrt)ĭid you actually create/apply a rule for the OpenWrt itself? NAT loopback is used inside the network to reach the internal server using the public IP. However, I am certain now that traffic from OpenWrt itself will not go through rules of wan (port forwarding) or lan (NAT loopback) on firewall, right? If OpenWrt try to access :1111, it will access 127.0.0.1:1111. As a beginner, I feel hard to achieve a full understanding about the information you provided.
0 Comments
Leave a Reply. |