Wont go inte networking, but assuming networking works between them you can manually specify an IP in the mobile app:
Add a device -> three dots in top right -> add devices by IP.
Bonus: This also works over tailscale and similar apps, making it so you can have an always on connection despite not being home.
Glad to hear it seems to be working! Hoping you find the issue in the backups, would be interesting to know what went wrong haha
Probably a good idea sadly... There can be a lot of different things wrong, so will probably be faster doing that either way.
When rebuilding, try to verify each that each step works so you find the problem eventually, Im guessing it will be easier to find that way
Have you tried setting the gateway to one of your LAN interfaces? And what happens if you ping 10.99.1.254 from the firewall?
Okay, I think I know (at least one of) the problem(s).
It is sending the ping from the WLAN interface because that is your default route, and you either don't have a route specified for your 10.2.x.x network or you're overwriting it with a different route (I'm guessing the first option).
E.g. you need to tell your firewall "if you want to reach an ip-address in 10.2.x.x you need to go through here", with "here" probably being either your managed switch if it works as a gateway (10.6.1.254?) or an interface on your router if it works as a switch (10.6.1.41?).
If the firewall cant reach the LAN, either because of a firewall rule or bad routing, it will not be able to access the DNS server even if it works well for the rest of the LAN. I'm assuming that the rest of the LAN talks to the DNS server directly and not through the firewall.
It sounds like you would benefit from reading a bit about how routing and gateways work, as it seems like you're mostly trying stuff without really knowing what it does. Please save yourself some sanity and make some proper planning on your different subnets, their vlans and how they should route their traffic, ideally in a diagram of some sort.
Without knowing your exact setup I'm getting a feeling that your current configuration is both overly permissive and overly restrictive, meaning you cant access the things you want but any potential attackers can probably get around just fine.
I would seriously consider tearing it down and starting over with a more cohesive plan, but I know that might not be possible for you time-wise. On the other hand, having a well planned network that you understand would almost certainly save you time in the long run, especially if you want to keep doing more advanced and unorthodox stuff to it.
First off, if your firewall can ping 8.8.8.8 it can access the WAN, as 8.8.8.8 (hopefully, or you have bigger issues) is on the WAN. It not being able to do updates etc is probably a DNS issue in that case, probably caused by your firewall not being able to access your DNS server due to improper configuration on either the firewall, the switches or the DNS server itself.
Is your DNS server allowing clients coming from subnets other than its own? Can your Wireguard clients also ping 8.8.8.8? If so, they probably share the DNS issue with your firewall.
I would recommend trying to debug this iteratively, as this sort of problem has a lot of potential error sources that is hard to know of no matter how many screenshots you provide, like the configuration of your switches and DNS server. Try this:
Computer A cant reach computer B. What is the IP of A? What is the subnet of A? If it is different from the subnet of B, what route should it take to reach B? What is the next step on that route? Can we successfully reach this next step? Does the next hop on the route know where to go to reach the subnet for B? If so, what is the next step? Repeat until we've reached B, ideally ensuring each step on the way is acting as it should either trough something like wireguard or the built in tools of your firewall/switch/gateway/etc.
Assuming the problem hasnt been found, repeat from B to A, as responses might not reach us resulting in a broken connection even if we can reach B.
If the routing makes sense, is there a firewall on the way that doesnt allow us to reach B from A? Can we instead reach A from B? If not, we've found the problem.
I would strongly reccomend drawing your network layout (or at least the route you are trying to debug) in a flowchart tool (diagrams.net being a good option), as it is extremely hard to keep track of everything otherwise.
This used to be me until I got diagnosed with ADD. Medication pretty much solved the issue completely.
Which model? Currently searching for one, and that sounds bearable
Have you tried tumbleweed? As someone who uses both Fedora (or more accurately Nobara) and tumbleweed, my laptop experience on tumbleweed has actually been slightly better on tumbleweed.
My only remaining issue is that wayland has slightly more input latency when playing games, enough that it's noticeable (or a very convincing placebo effect).
This makes it so that I have to use X11 and that I have to disable compositioning when playing games as my displays have different refresh rates. All in all, not a big problem but looking forward to be on wayland for good soon.
I'm split on this. Obviously bad, but not sure I can blame the developers for this fully as (if I understand it correctly, which I might not) they are sort of bound by CCP law? I imagine "stirring up controversy"/"making China look bad" might have some rather dire consequences for the developers.