Pfsense Jobs

2 were found based on your criteria {{ paging.total|number:0 }} were found based on your criteria

show all
  • Hourly ({{ jobTypeController.getFacetCount("0")|number:0}})
  • Fixed Price ({{ jobTypeController.getFacetCount("1")|number:0}})
Fixed-Price - Intermediate ($$) - Est. Budget: $50 - Posted
Hello, We are having difficulties narrowing down the problem we're having with some of the IP addresses configured on our pfsense firewall (pfSense 2.2.3-RELEASE). The following actions were taken: - Added a Virtual IP as IP Alias for each IP address (example: X.Y.Z.245/28) - Added a 1:1 NAT mapping rule on the WAN interface (example: External subnet IP X.Y.Z.245 -> Internal IP: 192.168.1.110) - Added a WAN rule to allow anything with destination 192.168.1.110, protocol any (which allows everything, including icmp and http) (After doing these steps we lost internet connectivity on our local server 192.168.1.110) - Added an Outbound NAT rule (example: to translate 192.168.1.110 to X.Y.Z.245) Experienced behavior: - Pinging the local server IP from the firewall works fine - Pinging the public IP (which is NATted to a local IP) from outside times out - IP addresses were configured on a laptop connected directly to Comcast and all of them worked properly List of IP addresses and whether they work on pfSense as 1:1 NAT configuration: xx.xx.xx.241/28 - WORKS as pfsense WAN IP xx.xx.xx.242/28 - WORKS xx.xx.xx.243/28 - DOESN'T WORK xx.xx.xx.244/28 - WORKS xx.xx.xx.245/28 - DOESN'T WORK xx.xx.xx.246/28 - DOESN'T WORK xx.xx.xx.247/28 - DOESN'T WORK xx.xx.xx.248/28 - DOESN'T WORK xx.xx.xx.249/28 - WORKS xx.xx.xx.250/28 - WORKS xx.xx.xx.251/28 - WORKS xx.xx.xx.252/28 - WORKS xx.xx.xx.253/28 - DOESN'T WORK xx.xx.xx.254/28 - Comcast Gateway We expect a knowledgeable person to find the cause of this issue and reconfigure pfsense so that all IP addresses can be configured as 1:1 NAT IP mapping. ... The following actions were taken: - Added a Virtual IP as IP Alias for each IP address (example: X.Y.Z.245/28) - Added a 1:1 NAT mapping rule on the WAN interface (example: External subnet IP X.Y.Z.245 -> Internal IP: 192.168.1.110) - Added a WAN rule to allow anything with destination 192.168.1.110, protocol any (which allows everything, including icmp and http) (After doing these steps we lost internet connectivity on our local server 192.168.1.110) - Added an Outbound NAT rule (example: to translate 192.168.1.110 to X.Y.Z.245) Experienced behavior: - Pinging the local server IP from the firewall works fine - Pinging the public IP (which is NATted to a local IP) from outside times out - IP addresses were configured on a laptop connected directly to Comcast and all of them worked properly List of IP addresses and whether they work on pfSense as 1:1 NAT configuration: xx.xx.xx.241/28 - WORKS as pfsense WAN IP xx.xx.xx.242/28 - WORKS xx.xx.xx.243/28 - DOESN'T WORK xx.xx.xx.244/28 - WORKS xx.xx.xx.245/28 - DOESN'T WORK xx.xx.xx.246/28 - DOESN'T WORK xx.xx.xx.247/28 - DOESN'T WORK xx.xx.xx.248/28 - DOESN'T WORK xx.xx.xx.249/28 - WORKS xx.xx.xx.250/28 - WORKS xx.xx.xx.251/28 - WORKS xx.xx.xx.252/28 - WORKS xx.xx.xx.253/28 - DOESN'T WORK xx.xx.xx.254/28 - Comcast Gateway We expect a knowledgeable person to find the cause of this issue and reconfigure pfsense so that all IP addresses can be configured as 1:1 NAT IP mapping. ... The following actions were taken: - Added a Virtual IP as IP Alias for each IP address (example: X.Y.Z.245/28) - Added a 1:1 NAT mapping rule on the WAN interface (example: External subnet IP X.Y.Z.245 -> Internal IP: 192.168.1.110) - Added a WAN rule to allow anything with destination 192.168.1.110, protocol any (which allows everything, including icmp and http) (After doing these steps we lost internet connectivity on our local server 192.168.1.110) - Added an Outbound NAT rule (example: to translate 192.168.1.110 to X.Y.Z.245) Experienced behavior: - Pinging the local server IP from the firewall works fine - Pinging the public IP (which is NATted to a local IP) from outside times out - IP addresses were configured on a laptop connected directly to Comcast and all of them worked properly List of IP addresses and whether they work on pfSense as 1:1 NAT configuration: xx.xx.xx.241/28 - WORKS as pfsense WAN IP xx.xx.xx.242/28 - WORKS xx.xx.xx.243/28 - DOESN'T WORK xx.xx.xx.244/28 - WORKS xx.xx.xx.245/28 - DOESN'T WORK xx.xx.xx.246/28 - DOESN'T WORK xx.xx.xx.247/28 - DOESN'T WORK xx.xx.xx.248/28 - DOESN'T WORK xx.xx.xx.249/28 - WORKS xx.xx.xx.250/28 - WORKS xx.xx.xx.251/28 - WORKS xx.xx.xx.252/28 - WORKS xx.xx.xx.253/28 - DOESN'T WORK xx.xx.xx.254/28 - Comcast Gateway We expect a knowledgeable person to find the cause of this issue and reconfigure pfsense so that all IP addresses can be configured as 1:1 NAT IP mapping.
Skills: PfSense Computer Networking