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

[FEAT] Forcing IPv6 in output by default #1459

Open
Disinterpreter opened this issue Dec 22, 2024 · 4 comments
Open

[FEAT] Forcing IPv6 in output by default #1459

Disinterpreter opened this issue Dec 22, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@Disinterpreter
Copy link

Disinterpreter commented Dec 22, 2024

Wanted features:

At the moment, doing a fastfetch command i've get only my IPv4 address with a subnet.
I think it is little wrong, IPv6 must be preferred as in all services.
So I suggest to change network output:
IPv6 GUA on interface (if it exist 2000::/3)
IPv6 ULA on interface (if it exist fc00::/7)
and after that IPv4 address.

and making a flag for link-local(fe80::/10) like --localip-show-link-local

Motivation:

IPv4 actual protocol, but it gonna be old in future, we should force IPv6 output everywhere for next generation of engineers.

@Disinterpreter Disinterpreter added the enhancement New feature or request label Dec 22, 2024
@CarterLi
Copy link
Member

IPv6 GUA on interface (if it exist 2000::/3)
IPv6 ULA on interface (if it exist fc00::/8)

Doesn't it leak your public ip address?

@Disinterpreter
Copy link
Author

IPv6 GUA on interface (if it exist 2000::/3)
IPv6 ULA on interface (if it exist fc00::/8)

Doesn't it leak your public ip address?

  1. Is it really somebody cares, especially if we show address by rfc8981
  2. "Leaking" isn't security issue, it's just an address.
  3. If i launch fastfetch now at my server, it shows me my "white" ipv4 address. Same thing.

I really read FAQ and as network engineer, I truly don't understand the problem of "leaking" IP. But if people want to hide their IP, we could make a flag which hide IP or replace some octets/hextets to :XXXX: / .xxx.

Image

@CarterLi
Copy link
Member

Many people hate that

If you want to show IPv6, you can set the config

{
    "type": "localip",
    "showAllIps": true,
    "showIpv6": true,
    "format": "{ipv6} [v6] {ipv4} [v4]"
}

Sorting is not supported though.

@Disinterpreter
Copy link
Author

Disinterpreter commented Jan 22, 2025

Many people hate that

If you want to show IPv6, you can set the config

{
"type": "localip",
"showAllIps": true,
"showIpv6": true,
"format": "{ipv6} [v6] {ipv4} [v4]"
}

Sorting is not supported though.

OFFTOPIC! If somebody trying to hack by its IP it isn't problem of fastfetch, it is OS/Software problem, and it will happen anyway, with fastfetch or not. Moreover you are the maintainer of this repo, and if you want to show IP, who cares? Showing IPv6 really safe, like with IPv4. And IPv6 anyway will change if it be given by RA.

"It should not require secrecy, and it should not be a problem if it falls into enemy hands;" you know...

Anyway I think it's better to consider to devide pools of addresses by ULA, GUA, link-locals, because in IPv6 having few addresses on the interface is a normal thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants