Update kpn.profile #368
Open
Update kpn.profile #368
+2
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had some errors in the igmpproxy logs:
Feb 08 13:40:57 UXG-Pro udm-iptvd[2307]: The source address 195.121.94.212 for group 224.0.250.64, is not in any valid net for upstream VIF[0].
Looking for this online, it seems that KPN changed or added something. See:
https://community.kpn.com/kpn-tv-11/ontvangers-blijven-hangen-op-80-na-update-modem-626696
Adding to the NAT rules 195.121.0.0/16 showed no more of these messages in the logs.