On Fri, 2 Feb 2024, Ralph Aichinger wrote:
Hi fellow Debian users!
In my quest to advance the IPv6 preparedness of my home LAN I want to
find a solution to use IP tokens on all my clients. IP tokens (keeping
the host part of the IPv6 address static while getting the subnet part
by SLAAC) seem
On Fri, 2024-02-02 at 15:31 +0100, Marco Moock wrote:
> It should be if you enter "save" in the nmcli.
Thanks, I did not realize this was possible. I probably
will use nmcli more often in the future.
Ralph
Am 02.02.2024 schrieb Ralph Aichinger :
> On Fri, 2024-02-02 at 14:28 +0100, Marco Moock wrote:
> > # nmcli c mod enp4s0 ipv6.addr-gen-mode eui64
> > # nmcli c mod enp4s0 ipv6.token ::deca:fbad:c0:ffee
>
> This is not permanent, is it?
It should be if you enter "save" in the nmcli.
address is static, and its PTR resolves to
something with my surname in it ;). At least at the moment I would
prefer shorter IPv6 addresses than can be constructed from the MAC,
even considering the possibility to "fake" the MAC to something
with many zeroes, using historic/obsolet
Am 02.02.2024 schrieb Ralph Aichinger :
> In my quest to advance the IPv6 preparedness of my home LAN I want to
> find a solution to use IP tokens on all my clients. IP tokens (keeping
> the host part of the IPv6 address static while getting the subnet part
> by SLAAC) seem very e
Hi fellow Debian users!
In my quest to advance the IPv6 preparedness of my home LAN I want to
find a solution to use IP tokens on all my clients. IP tokens (keeping
the host part of the IPv6 address static while getting the subnet part
by SLAAC) seem very elegant to me, because it avoids DHCPv6
On 2024-01-12, Ralph Aichinger wrote:
> I "only" have to find out what mechanism adds the lower, en2 default
> route within a few minutes, once I delete it. I ran "radvdump", but
> that only dumped the correct announcement my provider sends for the
> net over the PPPoE connection. Hm.
>
> Thanks e
401524.305759]
ralphfilterudpIN=en2 OUT=en2 MAC=08:00:1e:02:00:02:6c:cf:39:00:42:f4:86:dd
SRC=2a02:0ab8:redacted DST=2a00:63c1:redacted LEN=96 TC=0 HOPLIMIT=63
FLOWLBL=279176 PROTO=UDP SPT=40840 DPT=123 LEN=56
with interestingly IN and OUT interfaces the same en2 (=dmz). And to my
surprise, I
found
On 2024-01-12, Ralph Aichinger wrote:
> If I insert the following rule at the bottom, everything starts to
> work:
>
> meta l4proto udp accept
Add log to see what would be dropped:
meta l4proto udp log level info prefix "udp" accept
Provide "nft list ruleset" to better see what nft understa
On Fri, Jan 12, 2024 at 05:26:57PM +, Michael Kjörling wrote:
> My suggestion would be to insert a "udp log" rule. (Pretty sure you
> only need "udp", not "meta l4proto udp".)
Thanks, I will try that. Yes "meta l4proto udp" might be cargo
cult configuration ;)
> That will give you a fireh
On 12 Jan 2024 16:19 +0100, from r...@h5.or.at (Ralph Aichinger):
> If I insert the following rule at the bottom, everything starts to
> work:
>
> meta l4proto udp accept
>
> but I don't know how to limit this over broad rule (so it does not
> forward UDP to the internal network on en0, which I
ounter drop comment "drop
connections to loopback not coming from loopback"
meta l4proto ipv6-icmp counter accept comment "accept all ICMP
types"
tcp dport 22 counter accept comment "accept SSH"
tcp dport 25 coun
On Fri, Jan 12, 2024 at 03:52:46PM +, Tom Furie wrote:
> Where is the DNS server the dmz host is resolving against? In your dmz,
> your internal network, on the firewall machine, outside? You may have
> other input/output rules that are interfering, but since you've abridged
> your ruleset we h
Ralph Aichinger writes:
> I am currently fighting with the following problem: I've got a system
> that has 3 relevant interfaces: ppp0, en0 and en2, for external,
> internal and dmz respectively.
>
> The dmz is IPv6 only, a homelab testbed more or less.
>
> I've
Hello!
I am currently fighting with the following problem: I've got a system
that has 3 relevant interfaces: ppp0, en0 and en2, for external,
internal and dmz respectively.
The dmz is IPv6 only, a homelab testbed more or less.
I've got the follwing rules in /etc/nftables.conf for
Am 08.01.2024 um 13:01:38 Uhr schrieb Andreas B:
> I haven't checked thoroughly (yet), but the only immediate difference
> I can see, is that the router lifetime is 600 seconds (RA). My ISP's
> router used a lifetime of 86400 seconds (24h), I think.
That affect when the old addresses must be remo
A follow up on this.
I recently swapped my ISP's router with my own.
New temp-addresses are now generated when old ones become deprecated, as
expected.
I haven't checked thoroughly (yet), but the only immediate difference I can
see, is that the router lifetime is 600 seconds (RA).
My ISP's rout
Pocket writes:
[...]
> I am in the process of re-configuring NFS for V4 only.
Could it be there is some misunderstanding?
IPV4 and IPV6 are quite different concepts from NFSv4: I think this
works either on IPV4 and IPV6.
--
Ciao
leandro
Hello,
On Fri, Jan 05, 2024 at 07:04:21AM -0500, Pocket wrote:
> I have this in the exports, ipv4 works
>
> /srv/Multimedia 192.168.1.0/24(rw,no_root_squash,subtree_check)
> /srv/Other 192.168.1.0/24(rw,no_root_squash,subtree_check)
> #/home 2002:474f:e945:0:0:0:0:0/64(rw,no_root_squash,subtree_c
On Fri, Jan 05, 2024 at 09:54:54AM +, debian-u...@howorth.org.uk wrote:
> plus FWIW...
>
> https://docs.oracle.com/cd/E23824_01/html/821-1453/ipv6-ref-71.html
>
> "NFS software and Remote Procedure Call (RPC) software support IPv6 in a
> seamless manner. Existing comma
On 1/5/24 04:54, debian-u...@howorth.org.uk wrote:
Marco Moock wrote:
Am 04.01.2024 um 18:19:57 Uhr schrieb Pocket:
Where can I find information on how to configure NFS to use ipv6
addresses both server and client.
Does IPv6 work basically on your machine, including name resolution?
Does
On 1/5/24 03:35, Marco Moock wrote:
Am 04.01.2024 um 18:19:57 Uhr schrieb Pocket:
Where can I find information on how to configure NFS to use ipv6
addresses both server and client.
Does IPv6 work basically on your machine, including name resolution?
Yes I have bind running and ssh to the
Marco Moock wrote:
> Am 04.01.2024 um 18:19:57 Uhr schrieb Pocket:
>
> > Where can I find information on how to configure NFS to use ipv6
> > addresses both server and client.
>
> Does IPv6 work basically on your machine, including name resolution?
>
> Does it
Am 04.01.2024 um 18:19:57 Uhr schrieb Pocket:
> Where can I find information on how to configure NFS to use ipv6
> addresses both server and client.
Does IPv6 work basically on your machine, including name resolution?
Does it work if you enter the address directly?
https://ipv6.ne
Where can I find information on how to configure NFS to use ipv6
addresses both server and client.
I haven't found any good information on how to do that and what I did
find was extremely sparce.
I have NFS mounts working using ipv4 and want to change that to ipv6
--
Hindi madal
On 01/11/2023 17:41, Timothy M Butterworth wrote:
All,
Thanks for all your help. I was able to get it mostly working:
# Generated by NetworkManager
search home.arpa
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 192.168.104.233
# NOTE: the libc resolver may not support more than 3 nameservers
All,
Thanks for all your help. I was able to get it mostly working:
# Generated by NetworkManager
search home.arpa
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 192.168.104.233
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recogniz
On 30/10/2023 20:04, Timothy M Butterworth wrote:
sudo less /etc/NetworkManager/system-connections/Pixel5.nmconnection
[...]
[ipv6]
addr-gen-mode=stable-privacy
dns=2001:4860:4860::,2001:4860:4860::8844;
dns-search=home.arpa;
ignore-auto-dns=true #I tried with this on, commented out and
etworkd does not try to manage interfaces
networkctl
should report "unmanaged". I assume that NetworkManager uses its
internal DHCP client and it is OK.
Timothy, are you sure that "Pixel5" sends a DHCP lease? I have almost no
experience with IPv6. I would try other met
thing I am
missing is the population of IPv6 DNS addresses.
sudo less /etc/dhcp/dhclient.conf
supersede domain-name "home.arpa";
supersede dhcp6.domain-search "home.arpa";
supersede dhcp6.name-servers 2001:4860:4860::,
2001:4860:4860::8844;
supersede
On Mon, Oct 30, 2023 at 1:18 PM Pocket wrote:
>
> On 10/30/23 09:04, Timothy M Butterworth wrote:
>
> Hello All,
>
> I have been following the recent emails regarding resolv.conf. I almost
> have my system running perfectly. The only thing I am missing is the
> populati
dr-change]
match-device=driver:eagle_sdio,driver:wl
wifi.scan-rand-mac-address=no
# no-auto-default file "/var/lib/NetworkManager/no-auto-default.state"
> ls -l /etc/resolv.conf
>
lsattr /etc/resolv.conf
>
I just changed this back to using chattr +i with the IPv6 addresse
On 10/30/23 09:04, Timothy M Butterworth wrote:
Hello All,
I have been following the recent emails regarding resolv.conf. I
almost have my system running perfectly. The only thing I am missing
is the population of IPv6 DNS addresses.
sudo less /etc/dhcp/dhclient.conf
supersede domain-name
Am 30.10.2023 um 22:08:46 Uhr schrieb Max Nikulin:
> On 30/10/2023 20:04, Timothy M Butterworth wrote:
> > sudo less /etc/resolv.conf
> > domain home.arpa
> > search home.arpa
> > nameserver 8.8.8.8
> > nameserver 8.8.4.4
>
> I do not see "# Generated by NetworkManager" here.
That is because N
ls -l /etc/resolv.conf
lsattr /etc/resolv.conf
As to /etc/dhcp/dhclient.conf and /etc/network/interfaces, I may be
wrong, but perhaps independent instances for IPv4 and IPv6 may be
running (if actual connection is managed through ifupdown)
Hello All,
I have been following the recent emails regarding resolv.conf. I almost
have my system running perfectly. The only thing I am missing is the
population of IPv6 DNS addresses.
sudo less /etc/dhcp/dhclient.conf
supersede domain-name "home.arpa";
supersede dhcp6.domain-search
ppp interface and start a dhcpv6
client there, if your ISP distribute IPv6 via dhcp.
basti writes:
> My changes where attached in my last mail. Did you seen it?
> Have a look at the mailing archive:
>
> https://lists.debian.org/debian-user/2023/09/msg00157.html
No, you posted only your new versions so I can't know what you
actually changed. You posted originally that you have:
On 07.09.23 10:27, Anssi Saari wrote:
basti writes:
Am 06.09.23 um 09:37 schrieb Marco:
Am 06.09.2023 09:24 schrieb Anssi Saari:
That should be enough but I don't really know how pppoe works, I've
only used IPv6 with tunneling, 6rd and 6in4 with the late route48.org.
With PPP I
basti writes:
> Am 06.09.23 um 09:37 schrieb Marco:
>> Am 06.09.2023 09:24 schrieb Anssi Saari:
>>
>>> That should be enough but I don't really know how pppoe works, I've
>>> only used IPv6 with tunneling, 6rd and 6in4 with the late route48.org.
>&g
Am 06.09.23 um 09:37 schrieb Marco:
Am 06.09.2023 09:24 schrieb Anssi Saari:
That should be enough but I don't really know how pppoe works, I've
only used IPv6 with tunneling, 6rd and 6in4 with the late route48.org.
With PPP IPv6CP (RFC 2472 is being used.
It negotiates a 64 bit
Am 06.09.2023 09:24 schrieb Anssi Saari:
> That should be enough but I don't really know how pppoe works, I've
> only used IPv6 with tunneling, 6rd and 6in4 with the late route48.org.
With PPP IPv6CP (RFC 2472 is being used.
It negotiates a 64 bit interface identifier to creat
basti writes:
> Hello,
>
> I have switch my network config from ifup to systemd-networkd.
>
> IPv4 is working well but IPv6 is broken now.
>
> In the past I used dhcpcd to delegate the ipv6 prefix to my LAN
> interface. It seems not working with systemd.
>
> On my P
Hello,
I have switch my network config from ifup to systemd-networkd.
IPv4 is working well but IPv6 is broken now.
In the past I used dhcpcd to delegate the ipv6 prefix to my LAN
interface. It seems not working with systemd.
On my PPP interface I get an IPv4 and a IPv6 Address.
On my LAN
On 8/13/23 13:59, Celejar wrote:
On Fri, 10 Feb 2023 16:20:00 +0300
Reco wrote:
Hi.
On Fri, Feb 10, 2023 at 08:04:38AM -0500, Greg Wooledge wrote:
On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
hosts: files mymachines dns myhostname
This is wrong.
But I
On Fri, 10 Feb 2023 16:20:00 +0300
Reco wrote:
> Hi.
>
> On Fri, Feb 10, 2023 at 08:04:38AM -0500, Greg Wooledge wrote:
> > On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
> > > hosts: files mymachines dns myhostname
> >
> > This is wrong.
>
> You're correct, but f
100% into ipv6
terminology, but I think my ISP uses dhcp-pd to give me a prefix.
Other than that I don't think dhcpv6 is in use. I use SLAAC with and
without privacy extensions (basically, a complete default setup).
In any case, I do not believe that my ISP changed anything in those 30
minute
Hi Andreas,
Am 26.06.2023 um 11:13 schrieb Andreas B:
Hi,
I'm very puzzled by the behaviour of ipv6 temp addresses on Debian 12.
Expected behaviour: as soon as a temp address becomes deprecated, a
new one is generated. This is the behaviour on Debian 11.
Reasonable expectation, I
Hi,
I'm very puzzled by the behaviour of ipv6 temp addresses on Debian 12.
Expected behaviour: as soon as a temp address becomes deprecated, a
new one is generated. This is the behaviour on Debian 11.
What actually happens: When the (first) temp address becomes
deprecated (in my case,
On Wed, 24 May 2023, cor...@free.fr wrote:
greetings,
today I got a server from OVH with ipv6 only.
is there any lightweight getting started tutorial for using ipv6 on debian?
such as ipv6 setup, route, filters, DNS, etc.
thanks in advance.
Corey
Do you mean already configured and working
greetings,
today I got a server from OVH with ipv6 only.
is there any lightweight getting started tutorial for using ipv6 on
debian?
such as ipv6 setup, route, filters, DNS, etc.
thanks in advance.
Corey
On Tue, 28 Mar 2023, Andy Smith wrote:
Thirdly, if no special handling is in use then your operating
system chooses which address to use. There's an RFC for that, and
all of that is configured in /etc/gai.conf on Debian. The default
behaviour is to try IPv6 first.
The default differs
th authoritative and resolver) do decide to
give you filtered results which may for example exclude
records. No records, no possibility of an IPv6 connection.
Secondly, your application that gets a list of answers (A and
records) might do something special. It is after all free to d
On 2023-03-27 13:48, Richmond wrote:
I have configured an ipv6 tunnel. If I visit this site:
http://ip6.me/
The "normal" test shows my ipv4 address, and the:
http://ip6only.me/
shows the ipv6 address.
However if I switch my DNS from opendns to the one provided by my ISP
and th
On Mon, Mar 27, 2023 at 12:48:13PM +0100, Richmond wrote:
I have configured an ipv6 tunnel. If I visit this site:
http://ip6.me/
The "normal" test shows my ipv4 address, and the:
http://ip6only.me/
shows the ipv6 address.
However if I switch my DNS from opendns to the one provided
Vincent Lefevre writes:
> On 2023-03-27 12:48:13 +0100, Richmond wrote:
>> I have configured an ipv6 tunnel. If I visit this site:
>>
>> http://ip6.me/
>>
>> The "normal" test shows my ipv4 address, and the:
>>
>> http://ip6only.me/
>&
On 27/3/23 20:05, Richmond wrote:
Jeremy Ardley writes:
Both DNS return records. I am not sure why this choice of DNS
should make a difference.
host -v ip6.me |grep
IN
9306IN 2001:4838:0:1b::201
host -v ip6.me 8.8.8.8|grep
an
> record.
>
> The A record is IPv4 and the record is IPv6
>
> When you get both it is then up to your application to choose IPv4 or
> IPv6 for the connection.
>
> If either fails the application will then try the other before finally
> failing.
>
> You need
On 2023-03-27 12:48:13 +0100, Richmond wrote:
> I have configured an ipv6 tunnel. If I visit this site:
>
> http://ip6.me/
>
> The "normal" test shows my ipv4 address, and the:
>
> http://ip6only.me/
>
> shows the ipv6 address.
>
> However if I swi
IPv6
When you get both it is then up to your application to choose IPv4 or
IPv6 for the connection.
If either fails the application will then try the other before finally
failing.
You need a DNS that can return A and records, and an application
that can use either.
I have noticed in
I have configured an ipv6 tunnel. If I visit this site:
http://ip6.me/
The "normal" test shows my ipv4 address, and the:
http://ip6only.me/
shows the ipv6 address.
However if I switch my DNS from opendns to the one provided by my ISP
and then run the "normal" test it shows
On 15/3/23 01:53, David Wright wrote:
I had hoped (not very hopefully) the solution wouldn't involve bashing
kernel parameters.
From previous journeys in this area systemd-networkd does a much
neater job and has huge numbers of options.
This is my worstation config
I hope it gets better :
On Tue 14 Mar 2023 at 17:06:19 (+0800), jeremy ardley wrote:
> On 14/3/23 16:21, Tim Woodall wrote:
> > On Tue, 14 Mar 2023, Jeremy Ardley wrote:
> > > I conclude there is no IPv6 DHCP involved but there must be
> > > something that listens to RA announcements and ge
r more information, see interfaces(5).
> > >
> > > source /etc/network/interfaces.d/*
> > >
> > > # The loopback network interface
> > > auto lo
> > > iface lo inet loopback
> > >
> > > # The primary network interface
> > >
On Tue, 14 Mar 2023 12:29:22 +0800
jeremy ardley wrote:
> (I'm quite annoyed they have done away with /var/log/syslog)
See the README in /var/log for work-arounds.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
On 14/3/23 16:21, Tim Woodall wrote:
On Tue, 14 Mar 2023, Jeremy Ardley wrote:
I conclude there is no IPv6 DHCP involved but there must be something
that listens to RA announcements and generates a MAC derived address
from that.
I still need to know how to control that as there are options
inet loopback
# The primary network interface
allow-hotplug enp0s3
iface enp0s3 inet dhcp
# This is an autoconfigured IPv6 interface
iface enp0s3 inet6 auto
↑↑
I'm not very familiar with interfaces nowadays, but that looks
as if it's asking for enp0s3 to be auto
. Nothing was changed from the original install.
>
> My problem today is identifying what bit of the system is getting the
> IPv6 address. I can find nothing in journalctl
[ removed the typo ]
> cat /etc.network/interfaces
> # This file describes the network interfaces available on your
l.
My problem today is identifying what bit of the system is getting the
IPv6 address. I can find nothing in journalctl
The networking is pure systemd networkd.service controlled
Correction. I mistyped above. My system uses the systemd networking.service
root@debian12:/etc/network# s
t of the system is getting the
IPv6 address. I can find nothing in journalctl
The networking is pure systemd networkd.service controlled
root@debian12:/etc/network# systemctl status networking
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.s
Am Tue, Feb 14, 2023 at 01:41:41PM -0500 schrieb gene heskett:
Hello Gene and Dave,,
> On 2/14/23 10:49, David Wright wrote:
> > Wisely done: we don't need it twice … and logs can be lengthy.
[...]
> Alright guys, I may have an existing system here that shows a 169, but not
> as default. Runnin
esponds or not is, I think, irrelevant here. The thing
gets cut short by the -EINVAL, which stems from the missing interface
specification (well, "zone index" in IPv6 jargon). Without zone index,
an IPv6LL is (may be?) underspecified. So it would be fe80::1%eth0
or something similar.
On 2/15/23 17:05, Felix Miata wrote:
gene heskett composed on 2023-02-15 16:24 (UTC-0500):
I've got around 5 machines
Every one of them has had avahi removed by a root rm, and has some
variation of this in an /etc/resolv.conf that is a real file, before the
local network worked.
Do you ha
On Wed, Feb 15, 2023 at 04:24:36PM -0500, gene heskett wrote:
you basically just made this up
No Michael, just recalling our interaction history, the general tone
being to give me hell for using hosts files instead of running a dns.
I have not told you that you need to use bind instead of hos
On Wed, Feb 15, 2023 at 05:05:42PM -0500, Felix Miata wrote:
> gene heskett composed on 2023-02-15 16:24 (UTC-0500):
>
> > I've got around 5 machines
> > Every one of them has had avahi removed by a root rm, and has some
> > variation of this in an /etc/resolv.conf that is a real file, before
gene heskett composed on 2023-02-15 16:24 (UTC-0500):
> I've got around 5 machines
> Every one of them has had avahi removed by a root rm, and has some
> variation of this in an /etc/resolv.conf that is a real file, before the
> local network worked.
Do you have TDE on none of these machine
On 2/15/23 13:08, Michael Stone wrote:
On Wed, Feb 15, 2023 at 09:30:57AM -0500, gene heskett wrote:
True. But I'd also suggest that if you do not want to support
/etc/hosts files name resolution methods
/etc/hosts works and has worked fine on debian for decades
I've got around 5 machines sti
On Wed, Feb 15, 2023 at 01:07:29PM -0500, Michael Stone wrote:
> On Wed, Feb 15, 2023 at 09:30:57AM -0500, gene heskett wrote:
> > True. But I'd also suggest that if you do not want to support /etc/hosts
> > files name resolution methods
>
> /etc/hosts works and has worked fine on debian for decad
On Wed, Feb 15, 2023 at 10:12:32AM -0500, Greg Wooledge wrote:
Sorry, Gene's line was actually "search hosts, nameserver".
So, "ping coyote" should have triggered name resolution for "coyote.hosts"
and/or "coyote.nameserver".
It's just barely conceivable that *something* might have created a
re
On Wed, Feb 15, 2023 at 09:30:57AM -0500, gene heskett wrote:
True. But I'd also suggest that if you do not want to support
/etc/hosts files name resolution methods
/etc/hosts works and has worked fine on debian for decades
to. Your attitude that everybody with a two machine home network
shou
On Wed, Feb 15, 2023 at 10:04:14AM -0500, Greg Wooledge wrote:
> The part I still don't understand is how adding "search files, nameserver"
> to /etc/resolv.conf and rebooting could change the behavior of any of
> Gene's commands.
Sorry, Gene's line was actually "search hosts, nameserver".
So, "p
> 192.168.71.12 bpi54.coyote.denbpi54
> > > > gene@bpi54:~$ getent hosts bpi54
> > > > fe80::4765:bca4:565d:3c6 bpi54
> >
> > Where does getent pull that IPv6 address from? That's not what I get
> > when I look myself up:
>
On 2/15/23 09:20, Charles Curley wrote:
On Wed, 15 Feb 2023 07:57:09 -0500
gene heskett wrote:
192.168.71.4sixty40.coyote.den sixty40
192.168.71.7vna.coyote.deb vna
I think you have a typo in the line for vna.
Correct, Charles, but that machine died 2 o
On 2/15/23 08:41, Michael Stone wrote:
On Wed, Feb 15, 2023 at 07:57:09AM -0500, gene heskett wrote:
And this disclosed that I had not properly added coyote.coyote.den to
the /etc/hosts file on that machine. That mistake, fixed, now makes
the local net pingable. The rest of it, whats powered up
On Wed, 15 Feb 2023 07:57:09 -0500
gene heskett wrote:
> 192.168.71.4 sixty40.coyote.den sixty40
> 192.168.71.7 vna.coyote.deb vna
I think you have a typo in the line for vna.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescu
On Wed, Feb 15, 2023 at 03:46:21PM +0300, Reco wrote:
libnss-myhostname does that.
Why it chooses ipv6 link-local over ipv4 static IP is another question.
perhaps because ipv6 is preferred and there is no public ip6. it doesn't
really matter because normal users won't notice or ca
On Wed, Feb 15, 2023 at 07:57:09AM -0500, gene heskett wrote:
And this disclosed that I had not properly added coyote.coyote.den to
the /etc/hosts file on that machine. That mistake, fixed, now makes
the local net pingable. The rest of it, whats powered up, was/is all
pingable. It just wasn't t
65:bca4:565d:3c6 bpi54
Where does getent pull that IPv6 address from? That's not what I get
when I look myself up:
probably mymachines, which is yet another new twist to add to this
already ridiculous saga
.
That said, I'm curious about this part oF Gene's result:
gene@bpi54:~$ grep -i bpi54 /etc/hosts
192.168.71.12 bpi54.coyote.denbpi54
gene@bpi54:~$ getent hosts bpi54
fe80::4765:bca4:565d:3c6 bpi54
Where does getent pull that IPv6 address from? Tha
gene@bpi54:~$ getent hosts bpi54
> > > fe80::4765:bca4:565d:3c6 bpi54
>
> Where does getent pull that IPv6 address from?
libnss-myhostname does that.
Why it chooses ipv6 link-local over ipv4 static IP is another question.
Much better question is - what exactly one should
On 2/15/23 02:30, Michel Verdier wrote:
Le 15 février 2023 gene heskett a écrit :
gene@bpi54:~$ grep -i bpi54 /etc/hosts
192.168.71.12 bpi54.coyote.denbpi54
gene@bpi54:~$ getent hosts bpi54
fe80::4765:bca4:565d:3c6 bpi54
gene@bpi54:~$ ping -c1 coyote (this machines alias in /e
works and
responds to pings. It could be a printer that he used in 2003 and no
longer exists, but is still in the /etc/hosts file. Anything.
That said, I'm curious about this part oF Gene's result:
> > gene@bpi54:~$ grep -i bpi54 /etc/hosts
> > 192.168.71.12
x27;t, why would you expect it to respond?
Whether it responds or not is, I think, irrelevant here. The thing
gets cut short by the -EINVAL, which stems from the missing interface
specification (well, "zone index" in IPv6 jargon). Without zone index,
an IPv6LL is (may be?) underspecified. So it would be fe80::1%eth0
or something similar.
Cheers
[1] https://en.wikipedia.org/wiki/IPv6_address#zone_index
--
t
signature.asc
Description: PGP signature
Le 15 février 2023 gene heskett a écrit :
> gene@bpi54:~$ grep -i bpi54 /etc/hosts
> 192.168.71.12 bpi54.coyote.denbpi54
> gene@bpi54:~$ getent hosts bpi54
> fe80::4765:bca4:565d:3c6 bpi54
> gene@bpi54:~$ ping -c1 coyote (this machines alias in /etc/hosts)
> ping: coyote: Name or s
On 2/14/23 18:12, Greg Wooledge wrote:
On Tue, Feb 14, 2023 at 05:51:52PM -0500, gene heskett wrote:
Already done that a month or so ago, to satisfy my own curiosity, the answer
is yes host lookups did fail again without it.
And just to make sure, I just went to it, removed the lsattr i, from
r
On Tue, Feb 14, 2023 at 05:51:52PM -0500, gene heskett wrote:
> Already done that a month or so ago, to satisfy my own curiosity, the answer
> is yes host lookups did fail again without it.
>
> And just to make sure, I just went to it, removed the lsattr i, from
> resolv.conf, commented that line
On 2/14/23 15:20, Greg Wooledge wrote:
On Tue, Feb 14, 2023 at 03:01:18PM -0500, Michael Stone wrote:
On Thu, Feb 09, 2023 at 03:02:22PM -0500, gene heskett wrote:
Yes Greg, you keep telling me that. But I'm in the process of bringing
up a 3dprinter farm, each printer with a bpi5 to manage octo
On Tue, Feb 14, 2023 at 03:01:18PM -0500, Michael Stone wrote:
> On Thu, Feb 09, 2023 at 03:02:22PM -0500, gene heskett wrote:
> > Yes Greg, you keep telling me that. But I'm in the process of bringing
> > up a 3dprinter farm, each printer with a bpi5 to manage octoprint. Joing
> > the other 4 on t
On Fri, Feb 10, 2023 at 02:33:12PM +, Tim Woodall wrote:
On Fri, 10 Feb 2023, jeremy ardley wrote:
you can ping them as in
ping fe80::87d:c6ff:fea4:a6fc
ooh, I didn't know that worked.
Same as
ping fe80::87d:c6ff:fea4:a6fc%eth0
on my machines at least. No idea how it picks the interfac
On Thu, Feb 09, 2023 at 03:02:22PM -0500, gene heskett wrote:
Yes Greg, you keep telling me that. But I'm in the process of bringing
up a 3dprinter farm, each printer with a bpi5 to manage octoprint.
Joing the other 4 on this net running buster and linuxcnc.
Just last week I added another bpi5
1 - 100 of 1071 matches
Mail list logo
