I am moving to a single IP base, instead of multiple IPs on each computer e just to access the server.
but in a single IP, I’m having no luck connecting.
I was able to ping the server/client in the router by disabling the firewall of the client.
But on my Client end when I ping the IP it says request time out.
Got two networks
Net A = 172.16.0.0/23 for Employee
Net B= 192.168.0.0/24 - ServerIP=192.168.0.117
What I did in the config
Configured the forward chain to accept traffic src-add = 172.16.0.0/23 to dst-add=192.168.0.0/24 vice versa
I tried experimenting in the network like IP routes but saying can’t find the gateway ports
Port forwarding or Hairpin no luck no even hitting the ports or I’m missing something
configt.rsc (18.7 KB)
anyone can Guide me to set this up? I appreciate your help
Simplify firewall rules including getting rid of raw rules.
You spend too much of config in fear instead of simply allowing needing traffic and dropping rest.
I apologize for being a late and noob, but not an exception. The table rules I just copied your sample last year to segregate my LAN IP to route different ISPs since I don’t want failover due to my company’s low compensation just to annoy them. I just figured out that having a separate route table/rules led to not communicating my two networks even though I set my DNS in the router to point to the server. I currently moved to the main routing table which I will redesign later.
About mangling, I used it to prioritize common websites visited by employees. I have a list that I removed in the posted configuration -text messaging service, email services, POS hosted in the cloud, etc.
I’m open to your suggestions Im, currently, I don’t use VLan since I have a lot of ports but for the improvement of the performance of the network might look forward about simplification.
