(SOLVED) Problem with client connect through static IP cable internet
-
Thanks for your answers again!
@maverickws said in Problem with client connect through static IP cable internet:
When you say "HTTP, SSH all do not work from the client" in the example (diagram) you provided you have:
curl google.de not working - still requires DNS to resolve google.de - sorry I didn't get from your previous posts that you were lacking connectivity when using IP addresses.
Yes,
nslookup google.deis working (eg. returns 172.217.21.227) on the client - so doingcurl google.deor doingcurl 172.217.21.227results in the same behavior.
Doingnslookup google.de 1.1.1.1(ie. using Cloudflare 1.1.1.1 as the DNS server) on the client does not work. Same behaviour as with HTTP, SSH, ...I'm not about nslookup so I'll skip that one in particular.
Anyway cause I gtg I'll leave my DNS Resolver config so you can compare to yours:
Also, if you do a
curl 216.58.211.35what is the output?Time-out on the client. Same with SSH. Works fine on pfSense (
Diagnostics -> Command Prompt).Do you have the default allow LAN to any rule on your firewall?
Firewall > Rules > LAN
- Action: Pass
- Interface: LAN
- Address Family: IPv4
- Protocol: Any
- Source: LAN Net
- Destination: any
I will have to look later - but the config is the default and I think it is there.
I am really unsure what pfSense is doing with client traffic! Normally, I would assume it does outbound NAT (= gives traffic outside some temporary ports and writes its own (external) IP address in the SRC field) and does the translation backwards when the requests come back. But somehow in this chain, the packets get dropped... Is there a possibility to track all traffic (= testing NAT)?
-
I found the solution: I had to add a firewall rule to allow OUT traffic from LAN -> WAN. Floating Rule...
I am not entirely sure why this was necessary but I wanted to rule out any firewall involvement. All the traffic from the LAN net to the WAN net was silently blocked by pfSense.As I am not that familiar with firewall rules: is this a potential security risk?
-
Post a screencap of your LAN rules so we're not guessing what you've got going on. You should NOT need floating rules unless you're doing traffic shaping or a complex config. By default, LAN allows all traffic to anywhere.
-
I currently do not have access to pfSense - I will post the screenshots tomorrow morning!
Apart from that: thousand thanks for your help and time :)
-
This post is deleted! -
This is my working config: config-pfSense.SCRUBBED.xml
-
Nobody wants to parse through an XML file. Screencaps are much better, a picture worth a thousand words etc.
-
@KOM said in Problem with client connect through static IP cable internet:
Nobody wants to parse through an XML file. Screencaps are much better, a picture worth a thousand words etc.
I am sorry but I am not on-premise. I only have the config here. But I'll try to create a VM, import the config and make screencaptures.
-
-
Get rid of that floating rule. You don't need it and it may be part of the problem. If you lose connectivity after deleting that rule then there is a deeper problem to be discovered and fixed because, like I said earlier, floating rules are used for QoS and special custom configs. You don't need any floating rules to get basic connectivity working.
Your LAN rules look good but there is no traffic logged (0/0 B for each rule) which means pfSense isn't seeing anything from LAN that is hitting those rules. The floating rule may be taking precedence.
What specific errors are the clients getting when trying to connect using various things like ssh or http/s? The exact error text can be very helpful.
-
This post is deleted! -
@KOM said in Problem with client connect through static IP cable internet:
Get rid of that floating rule. You don't need it and it may be part of the problem. If you lose connectivity after deleting that rule then there is a deeper problem to be discovered and fixed because, like I said earlier, floating rules are used for QoS and special custom configs. You don't need any floating rules to get basic connectivity working.
Your LAN rules look good but there is no traffic logged (0/0 B for each rule) which means pfSense isn't seeing anything from LAN that is hitting those rules. The floating rule may be taking precedence.
What specific errors are the clients getting when trying to connect using various things like ssh or http/s? The exact error text can be very helpful.
Just to be 100% clear on that: without the floating rule the clients are not able to access the internet. Even IP-based traffic (like ssh to an IP) is not possible without the floating rule. Pinging specific IPs works, everything else does not work.
With the floating rule, the internet and everything else works just perfectly.It is 99% a firewall issue.
My setup is a fresh install of pfSense with only the static IP for the WAN interface and the floating rule added.
When the floating rule is NOT enabled: curl/ssh and everything like that simply times out. There are no specific error messages (only "Connecting to ....... Connection timed-out"). The error text is very non-descriptive.
I will provide the exact error messages after I have pfSense installed freshly (without the floating rule).
-
The default LAN IPv4 allow to any rule does not belong on the floating, so something is wrong there.
Do you have other Floating rules? -
@maverickws said in Problem with client connect through static IP cable internet:
The default LAN IPv4 allow to any rule does not belong on the floating, so something is wrong there.
Do you have other Floating rules?The default "LAN IPv4 allow" rule is unchanged from a fresh install (and also works when using my DSL internet through PPPoE on the WAN interface). But when using the static IP configuration for WAN this rule (for some reason) does not work (0/0B)...
This here is a screenshot of my DSL internet firewall rule (NOT the cable static-IP internet connection where the problem persists):
In this configuration for DSL with PPPoE, I do NOT have a floating rule - everything works fine. -
@paprikawuerzung said in Problem with client connect through static IP cable internet:
Just to be 100% clear on that: without the floating rule the clients are not able to access the internet. Even IP-based traffic (like ssh to an IP) is not possible without the floating rule. Pinging specific IPs works, everything else does not work.
And to be clear on our side: a floating rule is NOT needed for proper functionality. IF things work only then, you have - as already said - a deeper problem or serious configuration flaw that you didn't see/show. As outbound rules are created automatically in the background, something definetly doesn't add up. Period.
As debugging is simply voodoo and guessing at the moment, you should gather information when you are back on site and post them. Even screens in the VM are void, as it's not the same constellation as on site with the WAN and a LAN client behind it to test.
I'd also double check DHCP settings and the client on premise: does it have the right IP address and does it match the LAN configuration? Not the first time there was a simple small problem in numbers that got switched around and as the default LAN rules are matched against "LAN net" instead of "any" a DHCP problem can go unnoticed as "firewall access works".
Traceroute from the Client helps checking if the packet goes the right way and if and where it hits the firewall to trigger routes and rules. -
@JeGr said in Problem with client connect through static IP cable internet:
@paprikawuerzung said in Problem with client connect through static IP cable internet:
Just to be 100% clear on that: without the floating rule the clients are not able to access the internet. Even IP-based traffic (like ssh to an IP) is not possible without the floating rule. Pinging specific IPs works, everything else does not work.
And to be clear on our side: a floating rule is NOT needed for proper functionality. IF things work only then, you have - as already said - a deeper problem or serious configuration flaw that you didn't see/show. As outbound rules are created automatically in the background, something definetly doesn't add up. Period.
Yes, sorry for my tone in the previous posts. I am a little frustrated that at first every post was about DNS and DHCP when I already ruled that out 10 posts ago (for that matter I was sure that its not a problem before I even posted this thread) and I wanted it to be clear that it really, really is not the problem at all.
I know that you help me with your time and I am very grateful for that!
To the topic:
This is a complete fresh install with only the static IP and gateway for the WAN interface added. If it is a configuration problem it is part of pfSense as it (appearently) does NOT "create the outbound rules automatically in the background".
Since there are no definitive guides on how to configure static WAN IP setups (with UnityMedia/KabelBW) it is highly unclear whether this calls for floating rules or not. I read the sections in the pfSense regarding floating rules and understand that they are only used as a last resort - and that internet normally works out of the box with everything handled perfectly by pfSense - but this is obviously not the case.As debugging is simply voodoo and guessing at the moment, you should gather information when you are back on site and post them. Even screens in the VM are void, as it's not the same constellation as on site with the WAN and a LAN client behind it to test.
The configuration (down to the IP addresses) is exactly the same so it is not completely void.
I'd also double check DHCP settings and the client on premise: does it have the right IP address and does it match the LAN configuration? Not the first time there was a simple small problem in numbers that got switched around and as the default LAN rules are matched against "LAN net" instead of "any" a DHCP problem can go unnoticed as "firewall access works".
DHCP on client side works and the IPs, Gateway, Domain etc. are set correctly. I am very sure about that. It is not a configuration error in the DHCP area. Which also shows that when I add the floating rule (without re-requesting a DHCP lease) -> the internet works instantly - without any further configuration of the client or pfSense.
Traceroute from the Client helps checking if the packet goes the right way and if and where it hits the firewall to trigger routes and rules.
I will provide screenshots and outputs after I am at the premise again.
A thousand thanks again for your answers/guidance!
-
@paprikawuerzung said in Problem with client connect through static IP cable internet:
as it (appearently) does NOT "create the outbound rules automatically in the background".
Yes it is. In default configuration. Otherwise check /tmp/rules.debug for yourself and compare it with your DSL configuration.
@paprikawuerzung said in Problem with client connect through static IP cable internet:
Since there are no definitive guides on how to configure static WAN IP setups (with UnityMedia/KabelBW) it is highly unclear whether this calls for floating rules or not.
Why should there? It's completely transparent. If you configure DHCP IP, static IP or PPPoE for exmaple don't matter at all what pfSense creates for automatic rules like automatic outbound rules, default LAN rules etc. It's essentially the same if you don't configure some highly experimental or advanced options on the Interfaces/WAN setup screen.
and that internet normally works out of the box with everything handled perfectly by pfSense - but this is obviously not the case.
Yes in your case. In hundreds of others we configured/installed it does. Be it PPPoE, DHCP, static IP4. No matter what :)
The configuration (down to the IP addresses) is exactly the same so it is not completely void.
Void for me as in "I can't help or debug with you when this is not the same environment the error happens and the virtual setup isn't configured exactly the same (as in: has some sort of uplink, a test VM as client behind it etc. etc.)". So for debugging the problem it's not really well suited :)
-
@JeGr said in Problem with client connect through static IP cable internet:
@paprikawuerzung said in Problem with client connect through static IP cable internet:
as it (appearently) does NOT "create the outbound rules automatically in the background".
Yes it is. In default configuration. Otherwise check /tmp/rules.debug for yourself and compare it with your DSL configuration.
It is a complete fresh install with no firewalls added and no additional configuration made apart from adding the static IP. Whether this rule is created or not (I believe you if you say it is) does not make any difference as it does not work.
@paprikawuerzung said in Problem with client connect through static IP cable internet:
Since there are no definitive guides on how to configure static WAN IP setups (with UnityMedia/KabelBW) it is highly unclear whether this calls for floating rules or not.
Why should there? It's completely transparent. If you configure DHCP IP, static IP or PPPoE for exmaple don't matter at all what pfSense creates for automatic rules like automatic outbound rules, default LAN rules etc. It's essentially the same if you don't configure some highly experimental or advanced options on the Interfaces/WAN setup screen.
and that internet normally works out of the box with everything handled perfectly by pfSense - but this is obviously not the case.
Yes in your case. In hundreds of others we configured/installed it does. Be it PPPoE, DHCP, static IP4. No matter what :)
I also configured the PPPoE configuration without any problems at all. The only difference here is that I add a static IP (provided by UM) and a gateway (also provided by UM). Why this should create problems with the firewall is beyond my knowledge...
The configuration (down to the IP addresses) is exactly the same so it is not completely void.
Void for me as in "I can't help or debug with you when this is not the same environment the error happens and the virtual setup isn't configured exactly the same (as in: has some sort of uplink, a test VM as client behind it etc. etc.)". So for debugging the problem it's not really well suited :)
Ok. I will provide screenshots from the running system.
-
https://docs.netgate.com/pfsense/en/latest/routing/connectivity-troubleshooting.html
It's always something from this list. I would do a packet capture on LAN to see if client packets are hitting the interface at all, and another on WAN to see if they're being forwarded out.
-
I fixed the error by adding a WAN firewall rule. In the default installation, this rule was missing:
I found the rule in another pfSense installation (= DSL internet) which I compared to the (now working) cable internet installation. After adding it, everything works just fine. The floating rule was overkill but essentially did the same thing.
I am still a little confused why this rule was not created automatically (as it was in the PPPoE DSL installation). Also, there were strange issues when booting the Fritz!Box BEFORE booting pfSense - even with reboots. In the last installation, everything worked out just fine and with no hassle - strange, strange... But now everything seems to be working just as I want it to
Thousand thanks for your time and suggestions, @JeGr, @kiokoman, @KOM and @maverickws !
