On Mon, Dec 28, 2020 at 10:39:56AM +0100, Otto Moerbeek wrote:
> On Mon, Dec 28, 2020 at 10:25:08AM +0100, Bastien Durel wrote:
>
> > Le lundi 28 d?cembre 2020 ? 09:17 +, Stuart Henderson a ?crit?:
> > > > So hardware failure confirmed :/ Do you think I can change the RAM
> > > > or
> > > >
On 12/28/20 12:18 PM, rgc wrote:
> On Mon, Dec 28, 2020 at 10:39:56AM +0100, Otto Moerbeek wrote:
>> On Mon, Dec 28, 2020 at 10:25:08AM +0100, Bastien Durel wrote:
>>
>>> Le lundi 28 d?cembre 2020 ? 09:17 +, Stuart Henderson a ?crit?:
> So hardware failure confirmed :/ Do you think I
This is my first attempt to set up wireguard, and of course I can't get it to
work.
The wg man page shows "ifconfig wgN debug" as an option to help debugging.
The man page for ifconfig does document the option.
Nor does the man page tell how to turn the option off.
I hoped it might show me my
Hi,
I am not sure where my issue is...
As I understand, WireGuard is strictly UDP.
I am working on a road warrior setup, where one end of the tunnel is my
OpenBSD server with a static public IP address and the other end will be
Windows 7/10 laptops with random public IP addresses.
My
Kernel is OpenBSD 6.8-current (GENERIC) #561: Sun Dec 27 18:29:43 MST 2020
Machine is a Wyse C90 - orignially sold as a "thin client" - tiny machine, no
serial port (ps and trace typed in).
HW Info at https://www.parkytowers.me.uk/thin/wyse/cx0/
Was planning to use it as a wifi bridge, so tiny
On Mon, 28 Dec 2020 21:17:42 +, Peter Fraser
wrote:
> This is my first attempt to set up wireguard, and of course I can't
> get it to work.
>
> The wg man page shows "ifconfig wgN debug" as an option to help
> debugging. The man page for ifconfig does document the option.
> Nor does the man
Hi Steve,
On 20/12/28 04:14PM, Steve Williams wrote:
> ...
>
> I am not sure where my issue is...
I am going to cut to the chase here since I am no wireguard or OpenBSD
expert; however, I happen to come across this blog today that may help
you clarify some of your questions:
Hi,
wgport 53
Unbound is configured to only listen on the loopback interface, so that
shouldn't be interfering...
But it does
https://www.mail-archive.com/misc@openbsd.org/msg175837.html
Le lundi 28 décembre 2020 à 09:23 +1000, Stuart Longland a écrit :
> On 28/12/20 3:56 am, Bastien Durel wrote:
> > After that I got a (maybe) endless loop of panics inducing panics
> > (I did
> > not got the output, it was cycling fast), and after that the /bsd
> > file
> > was left empty :
> >
On 2020-12-28, Bastien Durel wrote:
> Le lundi 28 décembre 2020 à 09:23 +1000, Stuart Longland a écrit :
>> On 28/12/20 3:56 am, Bastien Durel wrote:
>> > After that I got a (maybe) endless loop of panics inducing panics
>> > (I did
>> > not got the output, it was cycling fast), and after that
Le lundi 28 décembre 2020 à 09:17 +, Stuart Henderson a écrit :
> > So hardware failure confirmed :/ Do you think I can change the RAM
> > or
> > it's more likely a CPU/Chipset failure ?
> >
> > Thanks,
> >
>
> If you have multiple sticks of RAM, try removing some.
I have only one
--
On Mon, Dec 28, 2020 at 10:25:08AM +0100, Bastien Durel wrote:
> Le lundi 28 décembre 2020 à 09:17 +, Stuart Henderson a écrit :
> > > So hardware failure confirmed :/ Do you think I can change the RAM
> > > or
> > > it's more likely a CPU/Chipset failure ?
> > >
> > > Thanks,
> > >
> >
>
12 matches
Mail list logo
