1
18.7 Legacy Series / Re: Update telegraf package
« on: July 20, 2018, 02:09:53 am »
Great - thank you!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
18.7 Legacy Series / Re: Update telegraf package
« on: July 17, 2018, 02:27:42 am »
Sorry for the late reply.
Yes, I was talking about 1.7.0. In the meantime they released 1.7.0 (2018-06-12 - the day of your last post - just some hours later
and 1.7.1 .
Thank you
Yes, I was talking about 1.7.0. In the meantime they released 1.7.0 (2018-06-12 - the day of your last post - just some hours later
and 1.7.1 .Thank you
3
18.7 Legacy Series / Re: Update telegraf package
« on: June 08, 2018, 01:33:59 am »
You need to wait for opnsense to release a new version with 1.70 onboard.
If you want to test it install the package from opnsense and replace the binary with the one from the nighly build:
https://github.com/influxdata/telegraf
If you want to test it install the package from opnsense and replace the binary with the one from the nighly build:
https://github.com/influxdata/telegraf
4
18.7 Legacy Series / Re: Update telegraf package
« on: June 07, 2018, 11:19:19 am »
Its fixed in 1.70 nightly. Cheers 
5
18.7 Legacy Series / Re: Update telegraf package
« on: June 07, 2018, 12:04:53 am »
Ok - it should be fixed in 1.70. I will check the nightly build tomorrow.
Cheers
Cheers
6
18.1 Legacy Series / Re: [BUG] Tinc configuration problem
« on: June 06, 2018, 11:42:34 pm »
After a reboot the changes came into effect.
7
18.1 Legacy Series / [BUG] Tinc configuration problem
« on: June 05, 2018, 04:18:21 pm »
Hello,
i just misconfigured the Tinc package with a wrong Subnet for the "local" firewall.
After fixing the subnet from xx.xx.xx.66/28 to xx.xx.xx.64/28 there is no configuration change in the config file.
Local editing does not help since it is overwritten when restarting the service.
Two questions: Can you please fix the configuration update and how could i manually edit the configuration data?
Thank you!
i just misconfigured the Tinc package with a wrong Subnet for the "local" firewall.
Code: [Select]
tinc.xxxGlobal[8816]: Network address and prefix length do not match for configuration variable Subnet in /usr/local/etc/tinc/xixxGlobal/hosts/xxx line 2
After fixing the subnet from xx.xx.xx.66/28 to xx.xx.xx.64/28 there is no configuration change in the config file.
Local editing does not help since it is overwritten when restarting the service.
Two questions: Can you please fix the configuration update and how could i manually edit the configuration data?
Thank you!
8
18.7 Legacy Series / Re: Update telegraf package
« on: June 04, 2018, 12:40:50 am »
i missed the point when they started building freebsd builds.
thank you
https://github.com/influxdata/telegraf/issues/4227
thank you
https://github.com/influxdata/telegraf/issues/4227
9
18.7 Legacy Series / Re: Update telegraf package
« on: June 03, 2018, 01:02:42 am »
ok thank you.
Can you point me to the direction where i can find the source ? Seems that i am too ...
Cheers
Can you point me to the direction where i can find the source ? Seems that i am too ...
Cheers
10
18.7 Legacy Series / Re: Update telegraf package
« on: June 01, 2018, 02:59:46 am »
Sorry for my late reply.
My mistake - its 1.6.3
I am missing the ping rtt etc. on opnsense i get:
But it should be something like:
My mistake - its 1.6.3
I am missing the ping rtt etc. on opnsense i get:
Code: [Select]
# telegraf --config telegraf.conf --input-filter ping --test
* Plugin: inputs.ping, Collection 1
> ping,host=router.hamburg.test.de,url=8.8.8.8 result_code=0i 1527814612000000000
> ping,host=router.hamburg.test.de,url=heise.de result_code=0i 1527814612000000000
But it should be something like:
Code: [Select]
$ ./telegraf --config telegraf.conf --input-filter ping --test
* Plugin: ping, Collection 1
ping,host=WIN-PBAPLP511R7,url=www.google.com result_code=0i,average_response_ms=7i,maximum_response_ms=9i,minimum_response_ms=7i,packets_received=4i,packets_transmitted=4i,percent_packet_loss=0,percent_reply_loss=0,reply_received=4i 1469879119000000000
11
18.7 Legacy Series / Update telegraf package
« on: May 10, 2018, 01:15:44 pm »
Currently features like ping metrics from the telegraf plugin are more or less useless since rtt etc. is skipped in the reporting (to influxdb or others).
Telegraf 1.3.1 was releases on 2017-05-31. A more recent version in the package system would be great
cheers
Martin
Telegraf 1.3.1 was releases on 2017-05-31. A more recent version in the package system would be great
cheers
Martin
12
18.1 Legacy Series / Re: Problems with IPv6 address delegation
« on: February 26, 2018, 02:34:04 am »
It "suddenly" started working. I will compare the config backups later. Thank you for your support.
13
18.1 Legacy Series / Re: Problems with IPv6 address delegation
« on: February 25, 2018, 11:43:23 pm »
No. Well.
Selected is "WAN" - so no that is not the PPPoE Interface. See the attached screenshots.
Selected is "WAN" - so no that is not the PPPoE Interface. See the attached screenshots.
14
18.1 Legacy Series / Re: Problems with IPv6 address delegation
« on: February 25, 2018, 09:45:57 pm »
yes, ifconfig (LAN interface):
inet6 XXXX:4540:6522:f00:82ee:73ff:febd:b4a7 prefixlen 56
inet6 XXXX:4540:6522:f00:82ee:73ff:febd:b4a7 prefixlen 56
15
18.1 Legacy Series / Re: Problems with IPv6 address delegation
« on: February 25, 2018, 07:28:48 pm »
I just installed a fresh 18.1 and only configured PPPoE and IPv6 over IPv4. No change so far 
The router has a IPv6 address on both interfaces and can ping6 google.com but the LAN Clients dont get an IPv6 address.
Since my default GW is a private IPv6 route i tried the "only request a prefix" but this did not help (the WAN interface does not get an public IPv6 address but everything else works).
Help!
The router has a IPv6 address on both interfaces and can ping6 google.com but the LAN Clients dont get an IPv6 address.
Since my default GW is a private IPv6 route i tried the "only request a prefix" but this did not help (the WAN interface does not get an public IPv6 address but everything else works).
Help!