-
Notifications
You must be signed in to change notification settings - Fork 463
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
Comments
Doesn't it leak your public ip address? |
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. |
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. |
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.
The text was updated successfully, but these errors were encountered: