Re: [DNG] Configuring ethernet port for IPv6
Curtis Maurand wrote: > I think this is all great right up until you need a fixed address for > something like a mail server or a web server. That is no more of a problem with IPv6 as it is with IPv4 - if you have a “poor quality” ISP that doesn’t do fixed addresses then you have a problem with anything that needs a fixed(dish) IP. > So far, I've found IPV6 to be unreliable. In what way ? I’m not currently running IPv6 at home as I’ve not got round to reconfiguring the network to use my own (pre-systemd Debian, Linux VM) router, and the ISP supplied router doesn’t have the option to forward (IIRC) GRE needed to make my HE tunnel work. But in the past when I have had IPv6 running, it’s worked fine. I didn’t run my email over IPv6 for the simple reason that at the time, there was one element of my software stack that didn’t fully cope with it. Again, not found time to update everything - I believe that one issue was fixed a while ago. Going back probably around 10 years, I enabled IPv6 on our office network and waited to see if anyone noticed - no-one did, and we didn’t start experiencing new problems. Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On Mon, Sep 05, 2022 at 11:47:33AM -0400, Curtis Maurand wrote: > I think this is all great right up until you need a fixed address for > something like a mail server or a web server. So far, I've found IPV6 to be > unreliable. I would argue it's easier to get a fixed address with IPv6 than it is with IPv4. If a provider is using mobile IPv6 to hand out addresses, or is doing something else preventing users from having a fixed static IPv6 subnet this is the fault of that provider, and not a deficiency of the IPv6 protocol. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On 1/30/22 14:01, o1bigtenor via Dng wrote: On Sun, Jan 30, 2022 at 8:14 AM Simon wrote: Joel Roth via Dng wrote: My problem is connecting via dhcp over ethernet. On IRC I was advised to try ping ff02::1%eth1 which fails to get a response, indicating IPv6 is not enabled in my client. I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, then "ifup eth1". This fails with no link-local IPv6 address for eth1 References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" will trigger the kernel to assign an IPv6 address. Since this is not happening, I'm asking the wisdom of the list VUAs how to enable IPv6 for this port. You don’t actually need DHCP to configure IPv6. snip As an aside, and not specifically in response to either of the above emails, I recommend the certification scheme run by HE at https://ipv6.he.net/certification/, and if your ISP doesn’t yet offer IPv6, then their tunnel service will provide you with good IPv6 connectivity. It’s true that there is some learning you need to do for IPv6, but this course will take you through things in steps - start with the basics and work up to the more complicated stuff. The only bit I thought was a p.i.t.a. is a stage where you have to provide ping and traceroute results to 100 different IPv6 destinations over 100 days. The hardest part if finding 100 different destinations - at the time I did it, I did some grepping of DNS server logs at work to find them ;-) Not only do I want to echo mr Joel but for mr Simon. This gives great information - - - all together AND in a fashion that I think I may even be understanding this. Please would you fashion perhaps 2 or three more messages for intermediate and maybe even extend this into more of the 'advanced' networking country. I am not needing ipv6 at present but likely this spring fiber optics are happening (finally some decent speed options) and they are in the process of moving to ipv6 likely within a year or so. I would prefer to know at least some more before I 'need' it. I think this is all great right up until you need a fixed address for something like a mail server or a web server. So far, I've found IPV6 to be unreliable. -- Curtis https://curtis.maurand.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On Sun, Jan 30, 2022 at 8:14 AM Simon wrote: > > Joel Roth via Dng wrote: > > > My problem is connecting via dhcp over ethernet. On IRC > > I was advised to try > > > > ping ff02::1%eth1 > > > > which fails to get a response, indicating IPv6 is not enabled in my client. > > > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > > then "ifup eth1". This fails with > > > > no link-local IPv6 address for eth1 > > > > References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" > > will trigger the kernel to assign an IPv6 address. Since > > this is not happening, I'm asking the wisdom of the list VUAs > > how to enable IPv6 for this port. > > You don’t actually need DHCP to configure IPv6. snip > As an aside, and not specifically in response to either of the above emails, > I recommend the certification scheme run by HE at > https://ipv6.he.net/certification/, and if your ISP doesn’t yet offer IPv6, > then their tunnel service will provide you with good IPv6 connectivity. It’s > true that there is some learning you need to do for IPv6, but this course > will take you through things in steps - start with the basics and work up to > the more complicated stuff. The only bit I thought was a p.i.t.a. is a stage > where you have to provide ping and traceroute results to 100 different IPv6 > destinations over 100 days. The hardest part if finding 100 different > destinations - at the time I did it, I did some grepping of DNS server logs > at work to find them ;-) > > Not only do I want to echo mr Joel but for mr Simon. This gives great information - - - all together AND in a fashion that I think I may even be understanding this. Please would you fashion perhaps 2 or three more messages for intermediate and maybe even extend this into more of the 'advanced' networking country. I am not needing ipv6 at present but likely this spring fiber optics are happening (finally some decent speed options) and they are in the process of moving to ipv6 likely within a year or so. I would prefer to know at least some more before I 'need' it. TIA ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
Thank you for this introduction. On Sun, Jan 30, 2022 at 02:14:37PM +, Simon wrote: > Joel Roth via Dng wrote: > > > My problem is connecting via dhcp over ethernet. On IRC > > I was advised to try > > > > ping ff02::1%eth1 > > > > which fails to get a response, indicating IPv6 is not enabled in my client. > > > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > > then "ifup eth1". This fails with > > > > no link-local IPv6 address for eth1 > > > > References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" > > will trigger the kernel to assign an IPv6 address. Since > > this is not happening, I'm asking the wisdom of the list VUAs > > how to enable IPv6 for this port. > > You don’t actually need DHCP to configure IPv6. > By default, I think every major OS these days enables IPv6. When an interface > connects (link comes up), the device will solicit for routers on the network > - both actively by sending RS (Router Solicit) packets to trigger routers to > send RA packets, and passively by looking for RA (Router Advertisement) > packets that are sent periodically anyway. > Each RA lists all the network prefixes (IPv6 prefix is roughly analogous to > subnet number in IPv4) the router supports on that interface. Note that an > arbitrary number of prefixes are supported, and devices can have "many" IPv6 > addresses. Each prefix is accompanied by a number of flags - the key ones > here being whether autoconfig is supported (A flag) and whether the prefix is > managed (M flag), defaults normally being A set and M clear. > > With A set and M clear, devices will use SLAAC (StateLess Address Auto > Configuration) to create at least one address for itself in that prefix - > these days by randomly generating an address in a 64 bit range. For partly > historical, and partly philosophical reasons, SLAAC only works with 64 bit > prefix lengths, leaving 64 bits for the host address part. The device can > create multiple addresses, and change then as often as it likes. > This roughly analogous to the address autoconfig feature in IPv4 using the > 169.254/16 address ranges - except that with IPv6 the addresses are useful > for more than just the local network. > > NOTE: You will often see comments along the lines of “but the address is just > an extension of the MAC address meaning ...”. This was an early idea, but for > privacy reasons was dropped a long time ago and AFAIK no modern OS uses > it by default - whether they can be configured to use it I don’t know, but it > was deprecated a long time ago and it is strongly recommended not to use it. > > So that’s the most common network setup : each router (more than one can be > present) will advertise prefixes to be used on the network, and devices will > automatically configure their own addresses. This will generally work out of > the box once there is a router with the right IPv6 support connected to an > ISP that provides IPv6 support in their network. > > Note that none of this involves DHCPv6 - and in fact, adding a DHCPv6 service > to the network won’t have any effect. For this to work, the (IIRC) M flag > needs to be set in at least one RA. This signals to the clients that this ia > a managed network and they should use DHCPv6 to obtain some information. DHCP > doesn’t inform of IPv6 prefixes - these are still the preserve of RAs. > Setting the M flag for a prefix will involve configuration on the router. > > For completeness, another new concept in IPv6 is whether a prefix is “on > link”. In simple terms, if the prefix is on-link then a device can talk > directly to another device using addresses in that prefix - as is normally > the case with ethernet networks. However, there are some networks (wireless > networks with client isolation, some “locked down” secure networks, ...) > where this is not the case - where an intermediary (router) is needed to get > packets from one device to another - having the prefix flagged as no on-link > will trigger devices to send packets via the router even for addresses that > are in the same prefix. > > > Given the number of major ISPs (e.g. Sky and BT in the UK) who have turned on > IPv6, this autoconfig makes a huge proportion of users IPv6 enabled - and > mostly they’ve never noticed ! > > > And a note about Android. For mobile use, prefixes can change frequently as > the phone moves about. DHCP isn’t good at handling this, whereas it’s easy to > send out an RA with a new prefix and deprecating the old one by setting the > lifetime to a very short value. > Apart from the mobile use case, they also seem to think that no network > operator should be able to control the devices on the network - with DHCP > being seen as a tool for oppression and monitoring of devices. Never mind > that in some sectors, such control and monitoring is a legal requirement, or > needed to enforce security policies. > As a result, it
Re: [DNG] Configuring ethernet port for IPv6
Joel Roth via Dng wrote: > My problem is connecting via dhcp over ethernet. On IRC > I was advised to try > > ping ff02::1%eth1 > > which fails to get a response, indicating IPv6 is not enabled in my client. > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > then "ifup eth1". This fails with > > no link-local IPv6 address for eth1 > > References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" > will trigger the kernel to assign an IPv6 address. Since > this is not happening, I'm asking the wisdom of the list VUAs > how to enable IPv6 for this port. You don’t actually need DHCP to configure IPv6. By default, I think every major OS these days enables IPv6. When an interface connects (link comes up), the device will solicit for routers on the network - both actively by sending RS (Router Solicit) packets to trigger routers to send RA packets, and passively by looking for RA (Router Advertisement) packets that are sent periodically anyway. Each RA lists all the network prefixes (IPv6 prefix is roughly analogous to subnet number in IPv4) the router supports on that interface. Note that an arbitrary number of prefixes are supported, and devices can have "many" IPv6 addresses. Each prefix is accompanied by a number of flags - the key ones here being whether autoconfig is supported (A flag) and whether the prefix is managed (M flag), defaults normally being A set and M clear. With A set and M clear, devices will use SLAAC (StateLess Address Auto Configuration) to create at least one address for itself in that prefix - these days by randomly generating an address in a 64 bit range. For partly historical, and partly philosophical reasons, SLAAC only works with 64 bit prefix lengths, leaving 64 bits for the host address part. The device can create multiple addresses, and change then as often as it likes. This roughly analogous to the address autoconfig feature in IPv4 using the 169.254/16 address ranges - except that with IPv6 the addresses are useful for more than just the local network. NOTE: You will often see comments along the lines of “but the address is just an extension of the MAC address meaning ...”. This was an early idea, but for privacy reasons was dropped a long time ago and AFAIK no modern OS uses it by default - whether they can be configured to use it I don’t know, but it was deprecated a long time ago and it is strongly recommended not to use it. So that’s the most common network setup : each router (more than one can be present) will advertise prefixes to be used on the network, and devices will automatically configure their own addresses. This will generally work out of the box once there is a router with the right IPv6 support connected to an ISP that provides IPv6 support in their network. Note that none of this involves DHCPv6 - and in fact, adding a DHCPv6 service to the network won’t have any effect. For this to work, the (IIRC) M flag needs to be set in at least one RA. This signals to the clients that this ia a managed network and they should use DHCPv6 to obtain some information. DHCP doesn’t inform of IPv6 prefixes - these are still the preserve of RAs. Setting the M flag for a prefix will involve configuration on the router. For completeness, another new concept in IPv6 is whether a prefix is “on link”. In simple terms, if the prefix is on-link then a device can talk directly to another device using addresses in that prefix - as is normally the case with ethernet networks. However, there are some networks (wireless networks with client isolation, some “locked down” secure networks, ...) where this is not the case - where an intermediary (router) is needed to get packets from one device to another - having the prefix flagged as no on-link will trigger devices to send packets via the router even for addresses that are in the same prefix. Given the number of major ISPs (e.g. Sky and BT in the UK) who have turned on IPv6, this autoconfig makes a huge proportion of users IPv6 enabled - and mostly they’ve never noticed ! And a note about Android. For mobile use, prefixes can change frequently as the phone moves about. DHCP isn’t good at handling this, whereas it’s easy to send out an RA with a new prefix and deprecating the old one by setting the lifetime to a very short value. Apart from the mobile use case, they also seem to think that no network operator should be able to control the devices on the network - with DHCP being seen as a tool for oppression and monitoring of devices. Never mind that in some sectors, such control and monitoring is a legal requirement, or needed to enforce security policies. As a result, it would appear that Google have a policy of not supporting DHCP in Android - and even go so far as to “encourage” the hardware vendors of the chipsets to filter DHCP packets at the hardware level, thus blocking third party software from working. As a result of this,
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 03:14:31PM -1000, Joel Roth via Dng wrote: > This is an older thinkpad, I think it's unlikely to need > extra firmware. When I try to install firmware-misc-nonfree I'm told: > > Package firmware-misc-nonfree is not available, but is referred to by another > package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > > I do have firmware-linux-nonfree installed. Hmmm, OK. Well, firmware-linux-nonfree should pull in firmware-misc-nonfree, so your probably fine as far as that goes, and you probably have a bad ethernet chip. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Configuring ethernet port for IPv6
-- Joel Roth --- Begin Message --- Hi Steve, Long time... > On my next router, (probably OpenBSD/pf), I'm going to block all IPV6. > I enjoy that the badguys have to jump through one more hoop (NAT) to > hit me where it hurts. IPv6 does have some security features lacking in IPv4. > I'm not an authority on firewalls and routers, but I'm going to try > hard to pass only a very few IP addresses on my LAN, and put the Wifi > on a third network card. Hopefully someone is researching this for us. > In my opinion, IOT (the Internet Of Things) is for the most part an > abomination. I don't want my thermostat on the same subnet as my LAN. I was thinking of an IOT thermometer. Don't you want to hear something like "Hi I'm your smart thermometer. You're temperature is a little high today. You might have a cold, or worse. Have you been vaccinated yet? I recommend you stay at home till you feel better." > SteveT > > Steve Litt > Spring 2021 featured book: Troubleshooting Techniques of the Successful > Technologist http://www.troubleshooters.com/techniques > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth --- End Message --- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 05:50:37PM -0700, Gregory Nowak via Dng wrote: > On Fri, Jan 28, 2022 at 12:40:36PM -1000, Joel Roth via Dng wrote: > > On Fri, Jan 28, 2022 at 12:05:06PM -0700, Bob Proulx via Dng wrote: > > > Joel Roth wrote: > > > > Gregory Nowak wrote: > > > > > Is there anything different in the dmesg(1) output for eth1 than > > > > > for your other interfaces? > > > > > > > > bingo: > > > > > > > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error > > > >... > > > > This is a used Thinkpad pad, recently purchased. > > > > Fortunately usb-ethernet adapters are easily available. > > I'm not sure, but is it possible your ethernet chip is one which > requires firmware from the firmware-misc-nonfree package? This is an older thinkpad, I think it's unlikely to need extra firmware. When I try to install firmware-misc-nonfree I'm told: Package firmware-misc-nonfree is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source I do have firmware-linux-nonfree installed. > Greg > > > -- > web site: http://www.gregn.net > gpg public key: http://www.gregn.net/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > If we haven't been in touch before, e-mail me before adding me to your > contacts. > > -- > Free domains: http://www.eu.org/ or mail dns-mana...@eu.org > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 12:40:36PM -1000, Joel Roth via Dng wrote: > On Fri, Jan 28, 2022 at 12:05:06PM -0700, Bob Proulx via Dng wrote: > > Joel Roth wrote: > > > Gregory Nowak wrote: > > > > Is there anything different in the dmesg(1) output for eth1 than > > > > for your other interfaces? > > > > > > bingo: > > > > > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error > > >... > > > This is a used Thinkpad pad, recently purchased. > > > Fortunately usb-ethernet adapters are easily available. I'm not sure, but is it possible your ethernet chip is one which requires firmware from the firmware-misc-nonfree package? Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 12:05:06PM -0700, Bob Proulx via Dng wrote: > Joel Roth wrote: > > Gregory Nowak wrote: > > > Is there anything different in the dmesg(1) output for eth1 than > > > for your other interfaces? > > > > bingo: > > > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error > >... > > This is a used Thinkpad pad, recently purchased. > > Fortunately usb-ethernet adapters are easily available. > > This is very odd. Thinkpads have been very robust and reliable and > used so much that they have been somewhat of a reference platform for > many years. The e1000 driver family is very commonly used and is in > the kernel main. > > I suggest booting a live boot image on your Thinkpad and seeing if the > wired interface works using one of those. That would eliminate > something corrupted in your current installation. It's easy to do. > It is a good quick second opinion on the network hardware. > > Also, how did you install this system? Did you use a "netinstall" > image originally? Using the wired ethernet or WiFi? Because if you > installed using wired ethernet (the most typical way I install) then > at install time the netinstall image was working okay with your wired > ethernet. > > Booting a netinstall image in "Rescue Mode" (under the advanced > options) would also be a safe way to test if the hardware is working > under a live boot system. And if this is a recent install using a > netinstall image then it's one you already have available. Great suggestions. I think I've benefitted from your advice several times of the years, directly and from reading your posts. I booted from a different kernel, same result from ip addr show eth1. 2: eth1: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 28:d2:44:1a:e0:ca brd ff:ff:ff:ff:ff:ff I'll try with a live CD, or USB drive. I've got a hard drive in the CD bay at the moment. The notebook is new used, but the system has been the same (with upgrades) for probably 15 years. I haven't done a fresh installation for a long time (except as a VM). What a great resource you are, oh bearded ones! > Bob > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
Joel Roth wrote: > Gregory Nowak wrote: > > Is there anything different in the dmesg(1) output for eth1 than > > for your other interfaces? > > bingo: > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error >... > This is a used Thinkpad pad, recently purchased. > Fortunately usb-ethernet adapters are easily available. This is very odd. Thinkpads have been very robust and reliable and used so much that they have been somewhat of a reference platform for many years. The e1000 driver family is very commonly used and is in the kernel main. I suggest booting a live boot image on your Thinkpad and seeing if the wired interface works using one of those. That would eliminate something corrupted in your current installation. It's easy to do. It is a good quick second opinion on the network hardware. Also, how did you install this system? Did you use a "netinstall" image originally? Using the wired ethernet or WiFi? Because if you installed using wired ethernet (the most typical way I install) then at install time the netinstall image was working okay with your wired ethernet. Booting a netinstall image in "Rescue Mode" (under the advanced options) would also be a safe way to test if the hardware is working under a live boot system. And if this is a recent install using a netinstall image then it's one you already have available. Bob signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Thu, Jan 27, 2022 at 04:38:37PM -0700, Gregory Nowak wrote: > Hi Joel, > redirecting back to the list. > > > On Thu, Jan 27, 2022 at 12:44:55PM -1000, Joel Roth wrote: > > Thank you for the response, Gregory. > > > > On Thu, Jan 27, 2022 at 03:33:01PM -0700, Gregory Nowak via Dng wrote: > > > On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > > > > It seems that my new router uses IPv6. Perhaps that means > > > > the ISP does so as well. > > > > > > Just because a router uses IPv6, doesn't necessarily mean the ISP > > > supports it. > > > > > > My problem is connecting via dhcp over ethernet. On IRC > > > > I was advised to try > > > > > > > > ping ff02::1%eth1 > > > > > Just to make sure, the interface connected to your router is in fact > > > eth1, and not eth0, right? > > > > Yes, it's eth1. > > > > > > which fails to get a response, indicating IPv6 is not enabled in my > > > > client. > > > > > > Posting the actual output might help. > > > > Usually ping (with no options) periodically returns a line > > with the time taken for the round trip. In this instance, > > one line beginning with PING and nothing more. > > > > > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > > > > then "ifup eth1". This fails with > > > > > > > > no link-local IPv6 address for eth1 > > > > > > Even if your interface isn't able to configure a global IPv6 address, > > > it should still get a link local address starting with fe80. > > > > This is the problem. I don't have a link local address: > > > > $ ifconfig eth1 > > eth1: flags=4099 mtu 1500 > > ether 28:d2:44:1a:e0:ca txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 0 bytes 0 (0.0 B) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > device interrupt 20 memory 0xf250-f252 > > You don't seem to have an IPv4 address, even for obtaining a dhcp > lease. Is this what you expect? If not, then the problem would seem to > be wider in scope than just IPv6. > > > > > > Also, before modifying /etc/network/interfaces, I would advise doing > > > ifdown eth1, modifying the file, and then ifup eth1. Instead of inet6 > > > dhcp, I would suggest: > > > > > > iface eth1 inet6 auto > > > > > > My understanding is this should use either dhcp6, or RA/NDP to > > > configure it. > > > > > What does the following output: > > > > > > cat /proc/sys/net/ipv6/conf/all/disable_ipv6 > > > cat /proc/sys/net/ipv6/conf/default/disable_ipv6 > > > cat /proc/sys/net/ipv6/conf/eth1/disable_ipv6 > > > > All zeroes. > > > > Do you have network-manager or the like installed which could be > trying to configure the interface on its own? > > Is there anything > different in the dmesg(1) output for eth1 than for your other > interfaces? bingo: [467072.085551] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467072.902423] e1000e :00:19.0 eth1: Hardware Error [467081.10] e1000e :00:19.0 eth1: Hardware Error [467089.669913] e1000e :00:19.0 eth1: Hardware Error [467090.624833] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [467097.725663] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467098.549348] e1000e :00:19.0 eth1: Hardware Error [467243.278267] e1000e :00:19.0 eth1: Hardware Error [467243.588770] e1000e: eth1 NIC Link is Down [467248.986061] e1000e :00:19.0 eth1: Hardware Error [467249.940380] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [467255.211266] e1000e :00:19.0 eth1: Could not acquire PHY [467255.211285] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467255.918047] e1000e :00:19.0 eth1: Hardware Error This is a used Thinkpad pad, recently purchased. Fortunately usb-ethernet adapters are easily available. > Since ifconfig is depricated, what does: > > ip address show eth1 > > give you? 2: eth1: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 28:d2:44:1a:e0:ca brd ff:ff:ff:ff:ff:ff > What does: > > cat /proc/sys/net/ipv6/conf/eth1/autoconf 1 > output? > Other than that, that's all I can think of at the moment. Thanks, Greg, you've been very helpful. -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
Joel Roth via Dng said on Thu, 27 Jan 2022 11:37:52 -1000 >Hi veteran admins, > >It seems that my new router uses IPv6. Perhaps that means >the ISP does so as well. > >My problem is connecting via dhcp over ethernet. On IRC >I was advised to try > >ping ff02::1%eth1 > >which fails to get a response, indicating IPv6 is not enabled in my >client. > >I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, >then "ifup eth1". This fails with > >no link-local IPv6 address for eth1 > >References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" >will trigger the kernel to assign an IPv6 address. Since >this is not happening, I'm asking the wisdom of the list VUAs >how to enable IPv6 for this port. > >Thanks in advance, Hi Joel, Good to see you again! On my next router, (probably OpenBSD/pf), I'm going to block all IPV6. I enjoy that the badguys have to jump through one more hoop (NAT) to hit me where it hurts. I'm not an authority on firewalls and routers, but I'm going to try hard to pass only a very few IP addresses on my LAN, and put the Wifi on a third network card. In my opinion, IOT (the Internet Of Things) is for the most part an abomination. I don't want my thermostat on the same subnet as my LAN. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
Hi Joel, redirecting back to the list. On Thu, Jan 27, 2022 at 12:44:55PM -1000, Joel Roth wrote: > Thank you for the response, Gregory. > > On Thu, Jan 27, 2022 at 03:33:01PM -0700, Gregory Nowak via Dng wrote: > > On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > > > It seems that my new router uses IPv6. Perhaps that means > > > the ISP does so as well. > > > > Just because a router uses IPv6, doesn't necessarily mean the ISP > > supports it. > > > > My problem is connecting via dhcp over ethernet. On IRC > > > I was advised to try > > > > > > ping ff02::1%eth1 > > > Just to make sure, the interface connected to your router is in fact > > eth1, and not eth0, right? > > Yes, it's eth1. > > > > which fails to get a response, indicating IPv6 is not enabled in my > > > client. > > > > Posting the actual output might help. > > Usually ping (with no options) periodically returns a line > with the time taken for the round trip. In this instance, > one line beginning with PING and nothing more. > > > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > > > then "ifup eth1". This fails with > > > > > > no link-local IPv6 address for eth1 > > > > Even if your interface isn't able to configure a global IPv6 address, > > it should still get a link local address starting with fe80. > > This is the problem. I don't have a link local address: > > $ ifconfig eth1 > eth1: flags=4099 mtu 1500 > ether 28:d2:44:1a:e0:ca txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 20 memory 0xf250-f252 You don't seem to have an IPv4 address, even for obtaining a dhcp lease. Is this what you expect? If not, then the problem would seem to be wider in scope than just IPv6. > > > Also, before modifying /etc/network/interfaces, I would advise doing > > ifdown eth1, modifying the file, and then ifup eth1. Instead of inet6 > > dhcp, I would suggest: > > > > iface eth1 inet6 auto > > > > My understanding is this should use either dhcp6, or RA/NDP to > > configure it. > > > What does the following output: > > > > cat /proc/sys/net/ipv6/conf/all/disable_ipv6 > > cat /proc/sys/net/ipv6/conf/default/disable_ipv6 > > cat /proc/sys/net/ipv6/conf/eth1/disable_ipv6 > > All zeroes. > > > -- > Joel Roth > Do you have network-manager or the like installed which could be trying to configure the interface on its own? Is there anything different in the dmesg(1) output for eth1 than for your other interfaces? Since ifconfig is depricated, what does: ip address show eth1 give you? What does: cat /proc/sys/net/ipv6/conf/eth1/autoconf output? Other than that, that's all I can think of at the moment. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > It seems that my new router uses IPv6. Perhaps that means > the ISP does so as well. Just because a router uses IPv6, doesn't necessarily mean the ISP supports it. > > My problem is connecting via dhcp over ethernet. On IRC > I was advised to try > > ping ff02::1%eth1 Just to make sure, the interface connected to your router is in fact eth1, and not eth0, right? > > which fails to get a response, indicating IPv6 is not enabled in my client. Posting the actual output might help. > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > then "ifup eth1". This fails with > > no link-local IPv6 address for eth1 Even if your interface isn't able to configure a global IPv6 address, it should still get a link local address starting with fe80. Also, before modifying /etc/network/interfaces, I would advise doing ifdown eth1, modifying the file, and then ifup eth1. Instead of inet6 dhcp, I would suggest: iface eth1 inet6 auto My understanding is this should use either dhcp6, or RA/NDP to configure it. What does the following output: cat /proc/sys/net/ipv6/conf/all/disable_ipv6 cat /proc/sys/net/ipv6/conf/default/disable_ipv6 cat /proc/sys/net/ipv6/conf/eth1/disable_ipv6 Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
Oops, I missed a negative. I can add that I have **no** problem connecting to the router via wifi. ifconfig wlan2 shows both IPv4 and IPv6 addresses. Thank you for you attention! -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6
On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > Hi veteran admins, > > It seems that my new router uses IPv6. Perhaps that means > the ISP does so as well. > > My problem is connecting via dhcp over ethernet. On IRC > I was advised to try > > ping ff02::1%eth1 > > which fails to get a response, indicating IPv6 is not enabled in my client. > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > then "ifup eth1". This fails with > > no link-local IPv6 address for eth1 > > References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" > will trigger the kernel to assign an IPv6 address. Since > this is not happening, I'm asking the wisdom of the list VUAs > how to enable IPv6 for this port. > > Thanks in advance, I can add that I have problem connecting to the router via wifi. ifconfig wlan2 shows both IPv4 and IPv6 addresses. grep CONFIG_IPV6 /boot/config-$(uname -r) shows that all the IPv6 drivers are compiled into the kernel. -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Configuring ethernet port for IPv6
Hi veteran admins, It seems that my new router uses IPv6. Perhaps that means the ISP does so as well. My problem is connecting via dhcp over ethernet. On IRC I was advised to try ping ff02::1%eth1 which fails to get a response, indicating IPv6 is not enabled in my client. I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, then "ifup eth1". This fails with no link-local IPv6 address for eth1 References suggest that "ifconfig eth1 up" or "ip link set dev eth1 up" will trigger the kernel to assign an IPv6 address. Since this is not happening, I'm asking the wisdom of the list VUAs how to enable IPv6 for this port. Thanks in advance, -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
