This should mean that I can now put in my Port Forward rule (Screenshot attached) into Untangle for my redirection of this traffic destined on the desired port to an internal IP. I have also tried to generalize the rule (removed the source interface) and it still did not work. Oddly enough I checked the port from my ISPs external address with the simplified port forward rule it showed open. Something to note: I did follow the port forward troubleshooting guide as well. I went into Reports-Network-Port Forwarded Sessions and I see the traffic being forwarded correctly. I then went into Troubleshooting within the Network Configuration menu in Untangle and did a connectivity test from the Untangle router to the local machine where the port is needed. This would mean Untangle can access the local machine through this port. I have also tried turning off all the Apps and checked the “blocked” reports for both non-web and web to ensure nothing was being blocked. The only thing that seemed to be doing anything is the Threat Prevention app. It seemed to be blocking certain IP’s that were on its list. and it isn’t the Port Forward rule or the Apps stopping traffic – what could it be? I went ahead and added a rule for this troubleshooting to Pass all traffic destined for port 37842. Somethings I may have forgotten to mention. I have Tunnel setup and working correctly – I have a rule set for a tag to route through it. I have tagged this internal machine on my network and have confirmed the traffic is routing through it. I also went ahead and made a Ubuntu VM and tried this same process on it – and it also exhibits the same issue. I only have 12 days left in my trial to decide! So far, Untangle is performing MUCH better then PFSense was on my Proxmox machine. Great product! This is the only thing remaining to complete my transition over to Untangle.I published this guide several years ago to expose my thinking and configuration to the scrutiny of networking experts and benefit less experienced users with an easy to follow but comprehensive guide. ![]() I would like to thank all those who contacted me with questions or provided feedback that contributed to making this guide what it is today. I continue to appreciate feedback on any errors, configuration or areas you think would benefit from additional clarification so please don’t hesitate to contact me by email. Verification of functionality and performance.pfSense baseline guide with VPN, Guest and VLAN support Last revised 27 February 2021. #RETURNED ERROR CODE 1 AIRVPN VERIFICATION# #RETURNED ERROR CODE 1 AIRVPN VERIFICATION#.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |