I have updated my ipfire core 202 to core 203. But My wireguard is not working anymore.
I can connect to the vpn but I have no traffic on it. I am using it with my phone to secure my wifi access. But It is now impossible to connect to my DMZ at home or to navigate on internet.I don’t understand why. Do you have any idea?
I have also a trouble with the DHCP on the green network, but after disable and enable it it is working fine like I read in another topic.
I have also a problem with Wireguard and update core 203. After update, DNS Resolution do not work. Allowed Subnet in the wireguard Settings was 0.0.0.0/0 → no resolution 4 internal or external network. I changed this setting do my Green Interface → external Nameresolution is now ok , internal nameresoluton do not work. On IPfire version 202 everything is working fine. nslookup server… shows:
NS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: “IP of DNS-Server”
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Zeitüberschreitung bei Anforderung an UnKnown.
thank you for this answer.
I have also the settings 0.0.0.0/0 and the DNS on the green interface.
So, if I have well understood, if I modify the settings 0.0.0.0/0 to the green interface. External name resolution will work but not the internal name resolution. Why not, I can do with this.
My question is can I have traffic between the wireguard interface on the red one to navigate on internet?
Because for me, 0.0.0.0/0 was useful to be able to access to all interfaces (green, orange and red) from the wireguard one. But If you set the green interface instead of 0.0.0.0/0 you can only link wireguard interface to the green interface. Other traffic are forbidden.
the link to the documentation. www.ipfire.org - WireGuard
You can also decide which networks the peer is able to reach. By default, this is 0.0.0.0/0 to have the client route everything through the tunnel, but you can change it to your GREEN network to only route traffic to the local net over the VPN connection.
I have the same problem. I worked around it by creating DNAT rules for WireGuard traffic (udp 53) from the WG side to the red IP. I also have Kubernetes, and it’s experiencing the same issue, so I created DNAT rules for the 10.0.0.0/8 network as well.
in knot doc Configuration — Knot Resolver 6.4.1 documentation there is warning for using 0.0.0.0, so i have also tried to list all the interfaces and now it is working fine.
network:
listen:
# - interface: 0.0.0.0@53
- interface: lo # 127.0.0.1
- interface: green0
- interface: blue0
- interface: orange0
- interface: red0
You should create a bug report. Someone already created an issue with similar content:
Unfortunately I could not find the account registration page…
Aahh, I am able to login with my community account…
Somewhere in the documentation there is a link to an not existing page…
Where, which link? I just tried all the links on that page and all of them worked for me.
The “account” link points to https://people.ipfire.org/register and will re redirected to IPFire HP.
Interesting!
Brave/Chrome points to correct site, Firefox lands on homepage - wired…
I am using Firefox and for me it went to the right place.
Okay, I confirm that. However if you are logged in then you don’t need to register a new IPFire People account because you are already registered.
If you aren’t logged in then you get the Join page but if you then enter your existing username it will say that you can’t use it as it is already used.
So the link is for users who are not registered already with IPFire and therefore cannot log in to Community, People or Bugzilla.
I found out yesterday that I also have wireguard connection issues as described above. I have looked but can not find the actual “official” solution. I of course may have missed it. Does one exist?
Unfortunately, this does not work after reboot. Knot-resolver does not start automatically.
green0, blue0, red0… interfaces are initialized after DNS. DNS waits some time, than fails to start.
If you start knot resolver manually after reboot everything is ok.