Routing brakes if IPv6 is activated on the WAN interface
-
@steveits said in Routing brakes if IPv6 is activated on the WAN interface:
@m0nkey Click the 3 dots in the lower right of your post and see if it lets you edit it.
This seems only possible in the first 3600 seconds after creation of a thread, but thank. I guess, I have to live with the shame.
I agree from your tests it looks like pinging IPv4 addresses works and DNS does not. Which seems odd. Is google.de not resolving over IPv4?
It seems so. An recommendation for additional tests here? Should I try to reach a webpage via IP instead of name?
What are your DNS Resolver settings?
Here are my settings:
-
Is there anyone, who is able to help me with my issue?
-
@m0nkey is there a reason you enabled forwarding mode?
-
@heper I'm not sure anymore. I guess I had activated it because I was experimenting with certificate offloading for my sub-services.
But basically, I don't know. Should I try to deactivate it?
-
@m0nkey i don't know. maybe the upstream dns servers you use for forwarding are causing issues somehow?
-
@heper Deactivated the option, but it issue still consists and nothing changes.
-
@m0nkey You might try unchecking:
Use SSL/TLS for outgoing DNS Queries to Forwarding Servers
DNSSEC data is required for trust-anchored zones. -
@steveits Thx, unchecked them, but it does not solve my problem.
-
@m0nkey Start a new thread in the German sub-forum and don't do anything s... special like:
"I wanted to start with configuring the WAN interface for IPv6 only at first".
Load the pfSense default setting first and maybe then someone is able to help you. If you have a full dual stack there shouldn't be a problem at all. -
@bob-dig Thank you, but why the German sub-forum?
In the end, I will have to try what you suggested. I was hoping to get to know, how to analyse such issues, to learn something and solve future problems by myself.
