Re: ipv6_newaddr: Invalid argument
Roy Marples
Fri Jan 17 13:29:48 2020
Hi Mike
On 15/01/2020 20:27, Mike Goodman wrote:
This could be related to the IPv6 configuration problems for which you went to
all the trouble of supplying a patch. As you mooted very early on (Arch forum)
it may be network rather than dhcpcd related after all.
Well, I'm not sure how a /128 is supposed to work over RA.
RA is broadcast to the whole network, so this can ONLY work if the whole network
is just one host like say a router conneced to the ISP.
Still, I've finally been able to test it on my network and my patch I posted
earlier works fine.
I've comitted the patch to both dhcpcd-8 and master branches.
It is now a matter of great urgency that I get a mail server configured and
running, so leaving the IPv6 for a while. In doing so, Apache wouldn't work on
IP4 and the server wouldn't resolve to its fqdn. Digging for reasons and finding
some, with outcomes shown below, hopefully enough for you to see what's going on.
~]# lspci -v
(leaving out all the unnecessary)
01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network {lots more
blah blah}
Kernel driver in use: igb <<** no kernel module present **>>
~]# dmesg | grep igb <<** no response, straight back to command prompt **>>
There's a driver, igb-dkms, in the AUR repo so I'm going to try and compile it
then see which problems it may solve.
Good luck with that!
Apologies for sending you on what now looks like a red herring chase and with
sincere thanks for your help and patience to date. I'll let you know how I get on.
Don't appologise! I'm not sure it's entirely a red herring.
Roy
Archive administrator: postmaster@marples.name