[ZBX-15399] „::/0“ in allowed hosts for Zabbix Trapper Items doesn't allow IPv4 anymore Created: 2019 Jan 03 Updated: 2024 Apr 10 Resolved: 2019 Jan 20 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G), Proxy (P), Server (S) |
Affects Version/s: | 4.0.3, 4.2.0alpha2 |
Fix Version/s: | 4.0.4rc1, 4.2.0alpha3, 4.2 (plan) |
Type: | Problem report | Priority: | Minor |
Reporter: | Sebastian Kremer | Assignee: | Andrejs Kozlovs |
Resolution: | Fixed | Votes: | 0 |
Labels: | API, Trigger | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
LinuxUbuntu 18.04 LTS and Zabbix v4.0.3 |
Issue Links: |
|
||||||||||||
Team: | Team A | ||||||||||||
Team: | Team A | ||||||||||||
Sprint: | Sprint 47, Dec 2018, Sprint 48, Jan 2019 | ||||||||||||
Story Points: | 0.125 |
Description |
Steps to reproduce:
Result: The Zabbix Server reports "xxx cannot process item "test3" trap: connection from "192.168.40.115" rejected, allowed hosts: '::/0'" If we change the allowed hosts from '::/0' to '::/0, 0.0.0.0/0' it works Expected:
We have over 90k Trapper Items in hundreds of software projects that reports values to our zabbix servers and with an update from 3.4 to 4.x the automatic creation of new items doesn't work anymore, but we can't upgrade all of our projects (the zabbix integration) for this. Our Workaround right now will be a cronjob every minute to remove all '::/0' from new created trapper items (update items set trapper_hosts = '' where trapper_hosts = '::/0') |
Comments |
Comment by Vladislavs Sokurenko [ 2019 Jan 03 ] |
Could you please show Zabbix srver startup allowed features ? |
Comment by Sebastian Kremer [ 2019 Jan 03 ] |
9218:20190102:165714.947 ****** Enabled features ****** |
Comment by richlv [ 2019 Jan 03 ] |
It might be useful to change "trigger" to "trapper" throughout the summary and description. |
Comment by Sebastian Kremer [ 2019 Jan 03 ] |
You are right, Sorry, I can't change/modify this, @SupportTeam please correct this. Thank you! |
Comment by Vladislavs Sokurenko [ 2019 Jan 03 ] |
Looks like caused by |
Comment by Andrejs Kozlovs [ 2019 Jan 07 ] |
Fixed in:
|