@hspindel Search the forums https://forum.netgate.com/topic/38499/set-gateway-and-dns-in-shell

@xman111 said in Internet going down: I was hoping for an easier way Well, it's a way. Other might exist. pfSense uses, as a WAN, an ordinary NIC, the same as your LAN, and other interfaces. These stay 'up' as long as power is good. No reason an interface would be taken down. That said, pfSense can take it down for a moment, as there is a process called dpinger that constantly pings a remote host, normally your upstream gateway,n or, as many people do : they chose '8.8.8.8'. if the pings start to drop, pfSense detects a 'bad' connection, an can reset the WAN. The moden, as it sees (feels ?) his LAN going down, can re initiate the upstream connection.

Thanks For Sharing Information.

@Gertjan one PPPoE connection for both IPv4 and IPv6. This is the configuration page: [image: 1721666225067-38d93822-7c9c-4eec-868d-9508acf4566a-image.png]

@Gertjan thanks, really helpful. Still I don't know why Netgate have not fixed this. Enabling DoT should just be that and not affect anything else.

Try checking the NAT type in each game on your Xbox, like in DayZ or Fallout. Sometimes the game shows a different NAT type than the Xbox settings. If it's showing strict or moderate NAT, that could be the problem.

@sheprador said in Is there a rule to tell pfSense: Allow traffic to the Internet from this interface?: There is the possibility in pfSense to create a single rule in which I say: "everything that comes from the WiFiGuest Vlan can go to the Internet". (maybe a couple of rules if I have 2 WANs) Yes ! It's the default rule you've found on the LAN interface when you installed pfSense. Here are mine : [image: 1721650863262-345324ba-6d5c-40cd-bb67-3ce1021d496c-image.png] Forget about the first rule, it's a NAT NUT rule, useful if you have an UPS. The second and third rule could be combined into one, but I've split them in 2 so I can see direct "how much IPv4 and how much IPv4". As soon as the IPv4 counters stays at "0" for a while, I can remove and disable IPv4 everywhere ^^

@SteveITS Many thanks for helping. Best regards

@stephenw10 Thanks very much for that. I did the upgrade and have not had the issue since. I did try looking for instructions on how to do this, but Google was not very helpful with the terms that I used. Either way, thanks again for the help.

sorry, my mistake. i had another drive (empty but normally mounted) that was the real problem, not zfs. i removed it from fstab and the system boot completed. again sorry for the false alarm...

@stephenw10 got everything working fine thank you very much

@stephenw10 thanks for responding -- yup pfSense update solved this particular issue. Now I'm running into TLS/ cert issues on my dockerized graylog setup, which is probably outside the scope of this forum. Would be nice to have a standard way to securely manage logs in Pfsense -- one that does not encourage people to send logs in the clear. I know you can just run a local server and have some security with Rules, but would suggest to have a more formal secure integration with Graylog given how popular it seems to be with people here. Also for people that want to monitor more than one network with one Graylog instance

Yup it's that. It forces pfSense to rebuild the ruleset using the patched script so you get the additional rules.

@Gertjan thanks for the info, I got brave yesterday and ordered this one... APC Back-UPS 600VA, 120V, 1 USB charging port, 7 NEMA outlets (2 surge) BE600M1

Yes, I've never seen that cause a problem.

Mmm, it sure feels like something is choking on that address though. Different code path for a static IP.

@stephenw10 I set a session timeout of 10 minutes. I have never entered a value in that field before. Logged back in after it timed out, cleared the session timeout field. This morning the login page came up normally.