Second IP Address - Everything works except for one program/PF
-
@lasergecko said in Second IP Address - Everything works except for one program/PF:
the Gateway is different than our previous IP
Not sure what to make of that. Are they routing that new IP to your WAN IP? If not since it has a different gateway I would think that would need its own interface...? Otherwise how will it be able to talk to the Internet...
BTW, I meant to comment earlier...2.4.4. is several versions old at this point. Not that it will make a difference in the routing but when you get it straightened out you should consider upgrading.
-
@steveits Yeah, I thought that was odd myself. Our regular contact was out of the office, so we had to call and get the info from some random tech support person. I'm going to verify the info I was given.
Maybe it's coming out the 2nd Ethernet port on the modem?
Our hardware is a WatchGuard Firebox something, so I wasn't sure if it could be upgraded without causing issues since pfSense was hacked onto it. It's one of the things that I've always meant to get around to investigating, but there aren't enough hours in the day...until something like this happens.
It's one of those things that you think ought to work just fine, but then again, I thought that by just following the tutorial, I'd be done with this in an hour, too. :)
-
@lasergecko said in Second IP Address - Everything works except for one program/PF:
It's one of those things that you think ought to work just fine, but then again, I thought that by just following the tutorial, I'd be done with this in an hour, too. :)
That shouldn't be a big deal at all, but it needs proper details what you get from the provider.
-
@viragomann Confirmed from a phone tech because it's not actually in the account info. (Thanks, Cox!) As suspected, it is not on the second port on the cable modem.
First IP xxx.xxx.xxx.134 Gateway xxx.xxx.xxx.129
Second IP xxx.xxx.xxx.171 Gateway xxx.xxx.xxx.161It turns out that the macOS Firewall was blocking that program even though it should not have been. I can now access the web interface, but the two machines cannot connect reliably.
They can both ping each other using the FQDN, local IP, and ZeroTier. Only the Production server can hit the secure Dev WebUI consistently. Dev is the target of the Second IP address.
Does that have anything to do with the second gateway?
Does it make sense to make a LAN based rule to force all clients to use the .129 gateway?
-
@lasergecko I am a bit confused because Virtual IP Addresses don't have a gateway setting. I would think to have that work you'd need to have a second WAN interface for that IP, and have traffic from the web server route out that IP. Basically, have two WANs but use them independently.
The more normal way is to allocate a block of 8 IPs (5 usable) and you can use Virtual IPs for the additional 4. However if they didn't allocate you that whole block (.128-.135) and some other client is using IPs in it then you'd have to change your WAN1 IP to a new IP/subnet they assign.
-
@lasergecko said in Second IP Address - Everything works except for one program/PF:
First IP xxx.xxx.xxx.134 Gateway xxx.xxx.xxx.129
Second IP xxx.xxx.xxx.171 Gateway xxx.xxx.xxx.161That seems strange. Usually when getting a second public IP from the same provider, it is routed to the primary IP from outside. And there is no need to state an additional gateway, all traffic is passed over a single gateway, even if the second IP is outside of the subnet of the first.
However, this depends on the configuration of the ISP devices.You can easily test the communication by using Diagnostic > Ping on pfSense. Select the second WAN IP from source drop-down and enter a public IP to ping like 8.8.8.8.
I can now access the web interface, but the two machines cannot connect reliably.
What does this mean?
From outside, from LAN?
Maybe you can give better details, what is working now and what is not. -
Well, it's good to know that something is different and odd with this setup and it's not just me. I will call back to see if they can change it to the same gateway to see if that makes any difference. The data is definitely coming in on that singular internet tube. :)
Here's a photo of the connection matrix that denotes what works and what fails. For that software to be able to work correctly, they need to be able to access the secure FQDN.
The Apple Firewall is disabled on each machine.
The Dev server is the one with the second static IP.
It's soooo close to working. :)
-
@lasergecko said in Second IP Address - Everything works except for one program/PF:
Here's a photo of the connection matrix that denotes what works and what fails.
This doesn't show, if it's working or not from LAN or from outside.
For that software to be able to work correctly, they need to be able to access the secure FQDN.
Seems also that it needs TLS encryption. So you need an SSL certificate matching the FQDNs on both servers. Did you add a specific to the dev server?
-
They're both working perfectly from outside the LAN. Both have their own SSL. (I didn't include that data because I created that spreadsheet to keep troubleshooting this issue straight, hoping to see a pattern.)
I've deployed this software many, many times since I used to work for the company that sold it. If the servers were at separate sites or AWS instances, everything would be just peachy. It works just fine using FQDN from my computer on the LAN, at home, tethered to my phone.
For some reason, it looks like pfSense is prohibiting just Dev from reaching the Prod FQDN, but just via that method.
Dev's hosts file is stock, btw. so that shouldn't be causing any issues.
-
@lasergecko said in Second IP Address - Everything works except for one program/PF:
For some reason, it looks like pfSense is prohibiting just Dev from reaching the Prod FQDN, but just via that method.
The only one part where pfSense can affect the FQDN is at DNS resolution, if you use the DNS resolver. But since you say it resolves correctly, I cannot think of any issue with pfSense.
As I got you, the only problem is to access the dev server from within the same LAN. However, this traffic doesn't doesn't pass pfSense, when the host name resolves the the servers internal IP address.
So I think, you should look for the reason on the server itself. Maybe its firewall is blocking access from LAN, maybe the server have set a wrong network mask so that he is sending responses to the gateway.
Possibly you can sniff the traffic to find out more about what's going on.