leen...@yahoo.co.uk <
leen...@yahoo.co.uk> wrote:
> wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet6 fdaa:bbcc:ddee:0:ed6f:210e:bdef:4c37 prefixlen 64 scopeid 0x0<global>
> inet6 fe80::5bdc:3cee:8de2:2469 prefixlen 64 scopeid 0x20<link>
> inet6 fdaa:bbcc:ddee:0:351d:2ed9:ec6f:1527 prefixlen 64 scopeid 0x0<global>
> ether e8:b1:fc:60:6c:33 txqueuelen 1000 (Ethernet)
> RX packets 2153 bytes 1757300 (1.7 MB)
> RX errors 0 dropped 12 overruns 0 frame 0
> TX packets 1298 bytes 230487 (230.4 KB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> I assume inet6 is the IPv6 address so it is almost as if for some reason I
> am not being given an IPv4 address? I wondered if the router was
> intercepting the DHCP request and giving an IPv6 address (must say don't
> know much about IPv6)? The config to switch off DHCP server on the router
> is in the IPv4 tab.
Those IPv6 addresses are local and link-local only, ie you don't have IPv6
connectivity they're just generated locally. You haven't received a public
IPv6 address so you can't talk to the IPv6 internet (unless the router is
doing v6 NAT, which is unusual).
It sounds like your link is up (packets are going past) so your WPA key/etc
are ok, but you aren't getting DHCP traffic. I would try running wireshark or
similar on wlp3s0 and watching what happens - does your machine make a DHCP
v4 request? Is there an answer?
One thing I have had problems with the BT Smart Hub with is it doesn't like
a machine roaming from ethernet to wifi and back again: I put a second WAP
on one of the ethernet ports, but the router couldn't cope with a device
connecting to the internal wifi, and then dropping off and reconnecting to
what it saw as ethernet (via the WAP). I don't think you would run into
that problem because you're connecting with different interfaces (ethernet
and wifi of your machine have different MAC addresses so the smart hub sees
them as different machines).
ISTR another similar problem publicised for the smart hub, but by then I'd
stopped using it and don't remember the details. I think a firmware update
was released to fix whatever it was, so maybe worth checking that is up to
date (the BT forum has various threads on issues with different firmware).
Theo