Other hosts on the network are.
v4 stack works just fine.
This laptop does get properly addressed when booted to Windows 10
I do get an fe80 address:
Code:
joliver@blinky:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether ec:f4:bb:15:41:6b brd ff:ff:ff:ff:ff:ff
inet 192.168.0.22/24 brd 192.168.0.255 scope global dynamic noprefixroute eno1
valid_lft 85576sec preferred_lft 85576sec
inet6 fe80::8be3:2840:4718:3a80/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether ac:7b:a1:2d:5a:af brd ff:ff:ff:ff:ff:ff
ufw is disabled, but there are ip6tables rules:
Code:
joliver@blinky:~$ sudo ip6tables -L -n --line-numbers
Chain INPUT (policy DROP)
num target prot opt source destination
1 ACCEPT all ::/0 ::/0
2 ACCEPT all ::/0 ::/0 state RELATED,ESTABLISHED
3 LOGGING all ::/0 ::/0
Chain FORWARD (policy DROP)
num target prot opt source destination
Chain OUTPUT (policy ACCEPT)
num target prot opt source destination
Chain LOGGING (1 references)
num target prot opt source destination
1 LOG all ::/0 ::/0 LOG flags 0 level 4 prefix "iptables-fw "
2 DROP all ::/0 ::/0
Not sure whet else might be relevant.