From: Freek de Kruijf <f.de.kruijf@gmail.com>
To: netdev@vger.kernel.org
Subject: Strange behavior of command ip
Date: Fri, 16 Aug 2024 00:16:23 +0200 [thread overview]
Message-ID: <3605451.dWV9SEqChM@eiktum> (raw)
I have the following bash script:
#!/bin/bash
getipv6() {
nmcli con modify "Wired connection 1" ipv6.addr-gen-mode eui64
nmcli con down "Wired connection 1"
nmcli con up "Wired connection 1"
/usr/bin/ip -6 a
}
getipv6
When I run the script the output is:
Connection 'Wired connection 1' successfully deactivated (D-Bus active path: /
org/freedesktop/NetworkManager/ActiveConnection/23)
Connection successfully activated (D-Bus active path: /org/freedesktop/
NetworkManager/ActiveConnection/24)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 fe80::dea6:32ff:fe55:12be/64 scope link tentative noprefixroute
valid_lft forever preferred_lft forever
When I run the command "/usr/bin/ip -6 a" the output is:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2001:4c3c:702:b700:dea6:32ff:fe55:12be/64 scope global dynamic
noprefixroute
valid_lft 4126sec preferred_lft 3466sec
inet6 fe80::dea6:32ff:fe55:12be/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Now the global IPv6 of eth0 is shown.
--
vr.gr.
Freek de Kruijf
next reply other threads:[~2024-08-15 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 22:16 Freek de Kruijf [this message]
2024-08-15 23:37 ` Strange behavior of command ip Jacob Keller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3605451.dWV9SEqChM@eiktum \
--to=f.de.kruijf@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox