Displaying 6 results from an estimated 6 matches for "wlp4s0".
2020 Aug 11
3
ipv6 NAT; accept_ra errors and about network choice
...eef:55::' prefix='64'>
</ip>
</network>
The first problem I hit was trying to start that network:
error: internal error: Check the host setup: enabling IPv6 forwarding
with RA routes without accept_ra set to 2 is likely to cause routes
loss. Interfaces to look at: wlp4s0
wlp4s0 is my wifi card that is configured by NetworkManager in a
completely unremarkable fashion. By default it gets an ipv6 via SLAAC
from my router. This feels a bit like the unresolved bug [1] which
says that systemd-networkd is handling the RA's in userspace for
... reasons [2]. It'...
2016 Oct 22
29
[Bug 98386] New: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer to {TDMS, flat panel) table invalid
https://bugs.freedesktop.org/show_bug.cgi?id=98386
Bug ID: 98386
Summary: [NVE7] bus: MMIO write of FAULT at [ IBUS ], Pointer
to {TDMS,flat panel) table invalid
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: minor
Priority:
2020 Aug 12
0
Re: ipv6 NAT; accept_ra errors and about network choice
...</ip>
> </network>
>
> The first problem I hit was trying to start that network:
>
> error: internal error: Check the host setup: enabling IPv6 forwarding
> with RA routes without accept_ra set to 2 is likely to cause routes
> loss. Interfaces to look at: wlp4s0
>
> wlp4s0 is my wifi card that is configured by NetworkManager in a
> completely unremarkable fashion. By default it gets an ipv6 via SLAAC
> from my router. This feels a bit like the unresolved bug [1] which
> says that systemd-networkd is handling the RA's in userspace for...
2020 Aug 17
1
Re: ipv6 NAT; accept_ra errors and about network choice
...rk>
> >
> > The first problem I hit was trying to start that network:
> >
> > error: internal error: Check the host setup: enabling IPv6 forwarding
> > with RA routes without accept_ra set to 2 is likely to cause routes
> > loss. Interfaces to look at: wlp4s0
> >
> > wlp4s0 is my wifi card that is configured by NetworkManager in a
> > completely unremarkable fashion. By default it gets an ipv6 via SLAAC
> > from my router. This feels a bit like the unresolved bug [1] which
> > says that systemd-networkd is handling the R...
2019 Apr 04
0
Shared printing between Linux (client) and Windows (server): NT_STATUS_ACCESS_DENIED
...ing parameter usershare owner only = no
> doing parameter security = user
> doing parameter encrypt passwords = yes
> doing parameter guest ok = yes
> doing parameter guest account = kotee
> pm_process() returned Yes
> lp_servicenumber: couldn't find homes
> added interface wlp4s0 ip=192.168.0.102 bcast=192.168.0.255
> netmask=255.255.255.0
> Netbios name list:-
> my_netbios_names[0]="XXXXXXXXXX"
> Client started (version 4.7.6-Ubuntu).
> Connecting to 192.168.0.100 at port 445
> Socket options:
> SO_KEEPALIVE = 0
> SO_REUSEADDR =...
2019 Apr 03
2
Shared printing between Linux (client) and Windows (server): NT_STATUS_ACCESS_DENIED
...ter usershare allow guests = yes
doing parameter usershare owner only = no
doing parameter security = user
doing parameter encrypt passwords = yes
doing parameter guest ok = yes
doing parameter guest account = kotee
pm_process() returned Yes
lp_servicenumber: couldn't find homes
added interface wlp4s0 ip=192.168.0.102 bcast=192.168.0.255 netmask=255.255.255.0
Netbios name list:-
my_netbios_names[0]="XXXXXXXXXX"
Client started (version 4.7.6-Ubuntu).
Connecting to 192.168.0.100 at port 445
Socket options:
SO_KEEPALIVE = 0
SO_REUSEADDR = 0
SO_BROADCAST = 0
TCP_NODELAY...