openwrt / openwrt/packages

stubby: Use standard notation for IPv6 local loopback address ( ::1 instead of 0::1 )

Open
#17,252 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

release/21.02 stale
Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

Maintainer: @jamesmacwhite
Environment:

Item Value
Model BT Home Hub 5A
Architecture xRX200 rev 1.2
Firmware Version OpenWrt 21.02.1 r16325-88151b8303 / LuCI openwrt-21.02 branch git-21.295.67054-13df80d
Kernel Version 5.4.154

Description:

Within the documentation and config files of stubby and the OpenWrt instructions you use the address 0::1 for the IPv6 local loopback address (which does work) but I cannot find anywhere else that uses this form, everyone uses ::1

I think these instances should be changed to keep things easier to read unless there is a technical reason for this.

These are a few that I found

README.md (several occurances)
https://github.com/openwrt/packages/blob/master/net/stubby/files/README.md

https://github.com/openwrt/packages/blob/04b82e9da01e8c067702867e3ad2a604f481b169/net/stubby/files/stubby.conf#L19

https://github.com/openwrt/packages/blob/04b82e9da01e8c067702867e3ad2a604f481b169/net/stubby/files/stubby.yml#L14

I have posted this over at getdnsapi/stubby aswell ****

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review net/stubby/files/README.md and the referenced stubby.conf and stubby.yml entries, then search the directory for other 0::1 occurrences. Confirm the notation is safe to standardize, replace the documented instances with ::1, and verify the documentation and configuration remain consistent.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.