Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why does phosphor-network change full ipv6 to short form? #72

Open
Journey-x opened this issue Jan 18, 2024 · 1 comment
Open

Why does phosphor-network change full ipv6 to short form? #72

Journey-x opened this issue Jan 18, 2024 · 1 comment

Comments

@Journey-x
Copy link

Journey-x commented Jan 18, 2024

busctl call xyz.openbmc_project.Network /xyz/openbmc_project/network/eth0 xyz.openbmc_project.Network.IP.Create IP ssys "xyz.openbmc_project.Network.IP.Protocol.IPv6" "1000:0000:0000:0000:AAAA:0000:00C2:0002" 64 "1000:0000:0000:0000:AAAA:0000:00C2:0001"

But the busctl show DefaultGateway6 is "1000::aaaa:0:c2:1"

busctl get-property xyz.openbmc_project.Network /xyz/openbmc_project/network/eth0 xyz.openbmc_project.Network.EthernetInterface DefaultGateway6
s "1000::aaaa:0:c2:1"

@Journey-x Journey-x reopened this Jan 18, 2024
@williamspatrick
Copy link
Member

Is there something you expect us to do about this? This sounds like a systemd bug if you can't get it to work? We're using unchanged systemd/networkd for the services you pointed to.

@Journey-x Journey-x changed the title OpenBmc Cannot open the systemd-networkd log level to debug Why does phosphor-network change full ipv6 to short form? Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants