I'm half tempted to return back to 380.66 to get consistent upnp.ĭns filtering works with your loop back, only on an external dns server ip address, not on internal ip address I checked it with an internal ip, it failed to work is there a possibility of a fix I'm willing to let you team viewer my system if you need to might help if you can see the behaviour first hand or I possibly could use my capture card and make a recording if it helps. I've also noticed that qos priority changes cause upnp to reboot and so does changing the upnp port range, both of which temporarily fix it even a loop back change does with out cleaning existing upnp forwards, which fixes the behaviour revert of upnp. Just a quick question how long does it take before a loop back change takes effect, or do I have to reboot in order for it to kick in. I've also been trying to test and see if you loop back would help with the strange nat error messagees that I received for gta v rockstar social club and mw3 spec ops mode even though the ports appear in the upnp log, I still get nat errors, Oddly my steam link connects to my pc but net work test results in an error about not being able to connect via its required port. The reason I'm trying get see if I can set up you loop back, is I'm trying to work out why upnp seems to have reverted in behaviour it appears to stop forwarding ports after an hour or so and I need to trigger a uPnP reboot in order to get it working this has been persistent behaviour since 380.67 alpa 1 but mainly it's bugging out on my pcs, I haven't left it on long enough to see if it's a bug with upnp or asus loop back. ![]() ![]() That's why I offer both options rather than just one or the other. You will have to resolve the conflict by either adding another exception rule, or by switching loopback mode.Įach NAT loopback method has its strengths and limitations. If it is, then it's simply a functionality conflict between the NAT loopback and DNSFilter in your particular scenario, and not a bug. You could try adding another exception for the router's IP to see if that's actually the case. It's possible for instance that the loopback causes the Pi's resolution connections to appear as coming from the router's own IP rather than from the Pi, causing it to get looped over and over. All I can think is that since you are probably ending up going through the loopback with your setup (as the router will attempt to redirect the outbound connection back to a LAN IP), and this somehow interferes with the Pi's ability to achieve recursive lookups. Unfortunately, I still cant access to my domains and sub-domains using this method.ĭNSMASQ_CONF=/jffs/configs/Įcho "address=//192.168.0.2" > $DNSMASQ_CONFĮcho "address=//192.168.0.2" > $DNSMASQ_CONFĮcho "address=//192.168.0.I still can't reproduce it here, however I don't have anything within my LAN to act as a recursive nameserver. So, as I own a nice RT-AC68U, with the latest Asuswrt-Merlin firmware 380.57, I tried to make some manipulation to have these local DNS entries working for all my connected devices: From previous searches, I understood NAT loopback function is precisely what you described. On Windows, Ubuntu, no problem, I just modify the host file as follow:īut on portable devices (android, apple) this modification is not possible (and I don't want to root). Your ISP router has the public address and when your local clients try to reach home assistant via external pubic ip address, it should handle this internally using NAT loopback, not your wifi router. Without NAT loopback you must use the internal IP address of the device when on the LAN. ![]() I own a server with some website locally homed. where a machine on the LAN is able to access another machine on the LAN via the external IP address of the LAN/router (with port forwarding set up on the router to direct requests to the appropriate machine on the LAN).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |