How to change RRD Quality IP?

sullrich

@Gitsum:

Yeah, me to. Using latest snapshot.
I added the use_rrd_gateway with a pingable address, but it still doesn't work.

Show us the xml.

Gitsum

<pfsense><version>2.3</version>
<lastchange><theme>nervecenter</theme>
<system><use_rrd_gateway>208.67.222.222</use_rrd_gateway>
<optimization>normal</optimization>
<hostname>pfsense</hostname>
<domain>local</domain>
<username>admin</username>
<password>$1$rXQXI.xG$K0UhU.e3ci0AgQoyBs.Oi.</password>
<timezone>America/Los_Angeles</timezone>
<time-update-interval><timeservers>pool.ntp.org</timeservers>
<webgui><protocol>http</protocol>
<port><certificate><private-key></private-key></certificate></port></webgui>
<disablenatreflection>yes</disablenatreflection>
<enablesshd>yes</enablesshd>

<interfaces>-<lan></lan></interfaces></lastchange></pfsense>

sullrich

Click save on the Interfaces -> WAN screen and see if it fixes it.

RRD needs to be instructed to recreate its info

Gitsum

Nope. Even after restart, it's still showing 100% loss.

sullrich

Run this from a shell.

cat /var/db/rrd/updaterrd.sh | grep out_wan | grep ping

Does your WAN IP gateway appear correctly?

Gitsum

yes, it does.

Gitsum

So, since my WAN gateway seems to be pingable, what would be causing the RRD quality graph to not function properly?

hoba

There seems to be a bug in the latest version that maybe is causing this issues: http://forum.pfsense.org/index.php/topic,3514.0.html

jahonix

I suppose the issue is solved, isn't it?

I still get 100% loss even though I'm using an rrd_gateway in the config.xml which is pingable.

cat /var/db/rrd/updaterrd.sh | grep out_wan | grep pin
shows the ISP gateway instead of what I entered. I saved on Interfaces|WAN and rebooted but without luck. Any ideas?

For the records: I am on 1.0.1-SNAPSHOT-03-27-2007 built on Tue Apr 3 07:30:15 EDT 2007

sullrich

Did you remove /tmp/config.cache after updating config.xml? If not then your manual changes where lost.

jahonix

@sullrich:

Did you remove /tmp/config.cache after updating config.xml? If not then your manual changes where lost.

Well, no.
I edited config.xml (without package infos) on a WS and restored the configuratiion through the webGUI. Shouldn't that do the trick? After the automatic reboot the new IP is still there but not used…

sullrich

Yes that should do the trick. I imagine you added the IP to the wrong location.

The setting goes in the wan xml area.

jahonix

@sullrich:

I imagine you added the IP to the wrong location. The setting goes in the wan xml area.

Isn't it stored under <system>any longer?


 <pfsense><version>2.9</version>
	 <lastchange><theme>nervecenter</theme>
	 <system><use_rrd_gateway>217.6.10.12</use_rrd_gateway>
		<optimization>normal</optimization>
		<hostname>gateway</hostname></system></lastchange></pfsense>

I followed your instructions. Sorry if they this is outdated…

@sullrich:

<system><use_rrd_gateway>XXX.XXX.XXX.XXX</use_rrd_gateway></system>

Does it matter where exactly it goes here? I would insert it right after the <if>tags… ???

		 <wan><if>rl0</if>
			 <mtu><blockpriv><media><mediaopt><bandwidth>100</bandwidth>
			<bandwidthtype>Mb</bandwidthtype>
			 <blockbogons><spoofmac><ipaddr>pppoe</ipaddr>
			 <pppoe><pppoe-reset-type>custom</pppoe-reset-type></pppoe></spoofmac></blockbogons></mediaopt></media></blockpriv></mtu></wan> 

```</if></system>

sullrich

Needs to be between:

Placing it right behind <wan>is the safest bet.

If you remove /tmp/config.cache and edit /cf/conf/config.xml and change it then click on Save on the wan screen you should be set.</wan>

databeestje

That would be correct, since february the use rrd gateway setting applies to each interface. That, because we now monitor quality on all outbound links.

So if you have a multiwan config with wan and opt1 you could place use rrd gateway tags on both these interface sections.

If you upgrade from a previous version the system tag will automatically be moved to the wan interface section.

Hope this helps.

jahonix

I inserted it where <use_rrd_gateway>was previously in the WAN section but pfSense doesn't seem to be impressed.
It still (tries to) ping my ISP's WAN gateway and I get 100% packet loss.

		 <wan><if>fxp0</if>
			<mtu>1490</mtu>
			 <media><mediaopt><bandwidth>100</bandwidth>
			<bandwidthtype>Mb</bandwidthtype>
			 <spoofmac><blockbogons><blockpriv><use_rrd_gateway>217.6.10.12</use_rrd_gateway>
			 <pppoe><pppoe-reset-type>custom</pppoe-reset-type></pppoe> 
			 <disableftpproxy><ipaddr>pppoe</ipaddr></disableftpproxy></blockpriv></blockbogons></spoofmac></mediaopt></media></wan>

This is from my pfSense at home with Intel NICs, not the one in the office (where the behavior is the same)…

# ping 217.6.10.12
PING 217.6.10.12 (217.6.10.12): 56 data bytes
64 bytes from 217.6.10.12: icmp_seq=0 ttl=249 time=38.284 ms
64 bytes from 217.6.10.12: icmp_seq=1 ttl=249 time=38.025 ms

If this is still valid, it pings my ISP's gateway:

cat /var/db/rrd/updaterrd.sh | grep out_wan | grep pin
        out_wan=` ping -c 5 -q 217.0.116.226 `

Any ideas?</use_rrd_gateway>

databeestje

Fixed in CVS.

Snapshot in 2 hours.

jahonix

Thanks for the fast correction, pfSense is pinging the right IP now!

I don't wanna be picky, but shouldn't it look a bit different than this:

status_rrd_graph_img.php.png
status_rrd_graph_img.php.png_thumb

sullrich

It might take RRD some time to gather data?

databeestje

That is correct, nan implies there is not enough data available.