• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

How to change RRD Quality IP?

Scheduled Pinned Locked Moved General pfSense Questions
45 Posts 9 Posters 34.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    Gitsum
    last edited by Jan 30, 2007, 1:50 AM Jan 30, 2007, 12:52 AM

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

    1 Reply Last reply Reply Quote 0
    • S
      sullrich
      last edited by Jan 30, 2007, 12:59 AM

      @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.

      1 Reply Last reply Reply Quote 0
      • G
        Gitsum
        last edited by Jan 30, 2007, 1:50 AM

        • <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>

        <maximumstates><dnsallowoverride></dnsallowoverride></maximumstates></time-update-interval></system>

        • <interfaces>-<lan></lan></interfaces></lastchange></pfsense>
        1 Reply Last reply Reply Quote 0
        • S
          sullrich
          last edited by Jan 30, 2007, 3:32 AM

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

          RRD needs to be instructed to recreate its info

          1 Reply Last reply Reply Quote 0
          • G
            Gitsum
            last edited by Jan 30, 2007, 4:03 AM

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

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by Jan 30, 2007, 4:07 AM

              Run this from a shell.

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

              Does your WAN IP gateway appear correctly?

              1 Reply Last reply Reply Quote 0
              • G
                Gitsum
                last edited by Jan 30, 2007, 4:14 AM

                yes, it does.

                1 Reply Last reply Reply Quote 0
                • G
                  Gitsum
                  last edited by Jan 31, 2007, 4:26 PM

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

                  1 Reply Last reply Reply Quote 0
                  • H
                    hoba
                    last edited by Jan 31, 2007, 9:15 PM

                    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

                    1 Reply Last reply Reply Quote 0
                    • J
                      jahonix
                      last edited by Apr 5, 2007, 8:26 PM

                      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

                      1 Reply Last reply Reply Quote 0
                      • S
                        sullrich
                        last edited by Apr 5, 2007, 8:41 PM

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

                        1 Reply Last reply Reply Quote 0
                        • J
                          jahonix
                          last edited by Apr 5, 2007, 8:47 PM

                          @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…

                          1 Reply Last reply Reply Quote 0
                          • S
                            sullrich
                            last edited by Apr 5, 2007, 9:26 PM

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

                            The setting goes in the wan xml area.

                            1 Reply Last reply Reply Quote 0
                            • J
                              jahonix
                              last edited by Apr 5, 2007, 11:13 PM

                              @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>
                              1 Reply Last reply Reply Quote 0
                              • S
                                sullrich
                                last edited by Apr 6, 2007, 4:54 AM

                                Needs to be between:

                                <wan></wan>

                                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>

                                1 Reply Last reply Reply Quote 0
                                • D
                                  databeestje
                                  last edited by Apr 6, 2007, 5:31 AM

                                  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.

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    jahonix
                                    last edited by Apr 8, 2007, 11:02 AM

                                    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>

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      databeestje
                                      last edited by Apr 8, 2007, 11:54 AM

                                      Fixed in CVS.

                                      Snapshot in 2 hours.

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        jahonix
                                        last edited by Apr 8, 2007, 11:21 PM Apr 8, 2007, 11:17 PM

                                        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

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          sullrich
                                          last edited by Apr 9, 2007, 12:13 AM

                                          It might take RRD some time to gather data?

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received