os-tayga: IPv6 Interface Address field breaks when CIDR suffix entered (double /128 appended)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- The title contains the plugin to which this issue belongs
Describe the bug
IPv6 Interface Address field breaks when CIDR suffix entered (double /128 appended)
To Reproduce
enter an address like fd00:6464::1/126 in the "IPv6 NAT64 Interface Address" field, save, restart the service
Expected behavior
interface should get the IPv6 address applied correctly
Screenshots
ifconfig: fd00:6464::1/126: bad value error, resulting IFDISABLED interface state
Relevant log files
root@opnsense:~ # ifconfig nat64
nat64: flags=1008051<UP,POINTOPOINT,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=4080000<LINKSTATE,MEXTPG>
inet 192.168.254.2 --> 192.168.254.1 netmask 0xffffffff
groups: tun tayga
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
Opened by PID 62232
Environment
Software version used
OPNsense 26.7.1 (amd64).
os-tayga: rev 1.5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the os-tayga configuration entry point for the “IPv6 NAT64 Interface Address” field and trace how an entered CIDR address is saved and passed to the service. Reproduce with fd00:6464::1/126, then verify that restarting the service applies the address without appending an extra /128 and avoids the IFDISABLED state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100