![]() ![]() Only turning off the 'firewall' itself worked. I tested by myself turning on and allowing all options in the firewall setting but it failed. What I want to know is if it is possible to access localhost with iOS while activating some part of function of macOS's firewall. I found the culprit, that is firewall setting because it worked fine when I turn off firewall of macOS.( At that time, I can accessed to the website via (private IP):80, and can't connected it via (my Mac Name).local:80. Oh, of course I used (my Mac Name).local:80 syntax instead. None of the four address above did not work. Then I try to connect the local website with my iPad using internet sharing via wifi and it failed. I can access the local website via localhost, localhost:80,(private IP) and (private IP):80 where my privateIP is .x. Many thanks for any advise or help you can offer and I apologize for the rather long post - but figured it would be easier to answer my questions if you had all the data.įirewall setting to connect to the localhost on macOS with iOS device I have local server using MAMP. If the command is non-persistent can I create a pf.conf file to store the values and have that invoked automatically on start-up? Is this command persistent or will it need to be entered on each restart of the system? Question: What is the command line entry to reroute incoming port 80 on ip 123.45.678.xxx to port 8080 at the same IP address? In researching the MAN files it appears that the way to do this involves some combination of sysctl(8) variables and or set to "1" (which I assume allows port forwarding to be available/functional) followed by a pfctl command with various options. The solution would be to port forward incoming port 80 to port 8080. ![]() I don't want to reconfigure TOMCAT to port 80 as that is a possible security issue. The solution appears to be eliminate the pointer at my domain service and associate the correct (matching) IP address with the domain name and allow the traffic to come in on my system on port 80. That means when the traffic arrives at my system the digital certificate information does not match and the user has to accept the "insecure" connection. Works fine EXCEPT that in the process of translating the domain name at my Domain provider they have associated the domain name with one of their IP addresses then allow the pointer to redirect traffic. Presently I use a pointer from my Domain provider to translate the domain name and point it to the static IP associated with the TOMCAT server on 8080. I have a Mac mini running TOMCAT which expects traffic on Port 8080.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |