From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Feedback on WG Date: Wed, 21 Aug 2024 15:23:31 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4040239791288943709==" List-Id: --===============4040239791288943709== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, > On 19 Aug 2024, at 12:04, Adolf Belka wrote: >=20 > Hi Michael, >=20 > Sorry for the delay with feedback on the WG testing. I was a bit tied up wi= th DIY stuff in the house. No problem... > By manually importing the WG config file created I was able to successfully= connect from my laptop to my IPFire vm system. The WUI showed connected. The= config file had my allowed subnets set as 192.168.200.0/255.255.255.0 which= is the green subnet on my vm system. However trying ping over the WG tunnel = gave failures for the IP of the vm machine, green1, and also for the green in= terface of the vm IPFire. Okay, connecting should be nice and easy. However, you *should* be able to tr= ansfer some data... > Trying to ping with the FQDN for the green1 system resulted in no resolving= of green1's FQDN to a local IP but tried to send it to my main red interface= with my ISP. Can you try to ping from either side? The client the firewall and the firewal= l the client? That should work if the tunnel is up. > So something appears to be missing or incorrect with the routing but not su= re what. >=20 > Minor points on the WUI. I would like to have the thing working first before we spend any time on maki= ng the UI look nice, but you are raising very good points. > When disconnected the status section that is coloured red is huge and the s= pace for the remark is very small but when connected then the status space is= large enough to have the connected status word, giving much more room for th= e remark. That should not be. No idea why that is, but I am sure that is not too hard t= o fix. > When the WG config file is created and you have the page with the QR code, = there is also a message about the WG config file only being shown this one ti= me as it contains private key material. The message is fine but the heading f= or the message is "Oops, something went wrong...". It should really be someth= ing like "Information Note" or equivalent as it is not an actual error messag= e. I think I created a little widget which I used somewhere else too and then ad= ded the headline. It certainly does not fit here. -Michael >=20 > See the screenshots attached. >=20 > Regards, >=20 > Adolf. > --===============4040239791288943709==--