Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Support matching ip interface id for ip_cidr rule#2209

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
blip wants to merge7 commits intoSagerNet:dev-next
base:dev-next
Choose a base branch
Loading
fromblip:ipif-rule

Conversation

blip
Copy link

Added support for matching IPv6's interface id, using a syntax like::1/::ff inip_cidr andsource_ip_cidr.

Fix#2204

cc@dyhkwong

@nekohasekainekohasekaiforce-pushed thedev-next branch 2 times, most recently fromb0565b2 to0b5c32aCompareOctober 22, 2024 03:40
@dyhkwong

This comment was marked as outdated.

@blip
Copy link
Author

Not sure i quite understand

This is only a syntactic sugar of existing functionality.

Maybe I missed something, but how can an interface id currently be matched without this PR?

CIDR is also used elsewhere, e.g. tun.address, tun.route_address and tun.route_exclude_address.

These are not matching rules? Are you suggesting they should also support the::1/:ff syntax? But this syntax is not a valid address.

@dyhkwong
Copy link
Contributor

dyhkwong commentedOct 22, 2024•
edited
Loading

Maybe I missed something, but how can an interface id currently be matched without this PR?

So this is in fact something like#2014?

@blip
Copy link
Author

blip commentedOct 22, 2024•
edited
Loading

yep, that person was asking the same feature. But it's not really syntactic sugar if it's not already achievable with the current rules, imho.

@dyhkwong
Copy link
Contributor

Maybe this should be a new type of rule. And the author of#2014 mentioned that this is also for tun.route_address_set?

@nekohasekainekohasekaiforce-pushed thedev-next branch 4 times, most recently from6740910 to58feb8eCompareOctober 30, 2024 02:24
@nekohasekainekohasekaiforce-pushed thedev-next branch 12 times, most recently from78f8093 toac6401bCompareNovember 7, 2024 05:44
@nekohasekainekohasekaiforce-pushed thedev-next branch 11 times, most recently from3611dcd to36c095fCompareJune 21, 2025 11:43
@nekohasekainekohasekaiforce-pushed thedev-next branch 12 times, most recently from4492a53 to989034bCompareJuly 3, 2025 14:20
@nekohasekainekohasekaiforce-pushed thedev-next branch 7 times, most recently from8ec5593 tob3c1110CompareJuly 12, 2025 06:48
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Support ::1/::FF for ip_cidr and source_ip_cidr?
3 participants
@blip@dyhkwong@nekohasekai
[8]ページ先頭
©2009-2025 Movatter.jp