I've got to get use to replying to list. On 2017-12-22 21:42, James Knott wrote:
On 12/22/2017 10:36 PM, Mark Petersen wrote:
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 50:e5:49:c6:1a:e0 brd ff:ff:ff:ff:ff:ff inet 192.168.0.50/24 brd 192.168.0.255 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::52e5:49ff:fec6:1ae0/64 scope link
valid_lft forever preferred_lft forever
I only have an fe80 address.
I assume this is for the LAN side? No, for the WAN interface.
192.168.0.50 on the WAN???
No, you must have read that wrong. enp5s6 is on the WAN side - currently has a 174.xxx address. enp3s0/br0 is on the LAN side with an address of 192.168.0.50.
If I plug the WAN into my Tumbleweed laptop, I do get an IPV6 address. So I know I can get an address. - Also in the journal, my isp is giving me and address.
As I suspected. So, start with a fresh install as a desktop, verify you get an IPv6 address and go from there. However, as I mentioned, I couldn't get DHCPv6-PD to work with openSUSE. You may have the same issue. This was over 1.5 years ago, so perhaps someone else has more current experience.
So this may be a wicked problem, or an issue with how opensuse tweaks the kernel? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org