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

    Dual WAN - Time Based Gateway Changes

    Scheduled Pinned Locked Moved Routing and Multi WAN
    16 Posts 4 Posters 6.6k 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.
    • J Offline
      jgottlieb
      last edited by

      I'd be happy to try it out.  I grabbed the latest snapshot, but I think it was a 7.2 build. Can you point me at the latest ISO that would have it?

      Thanks,

      Joshua

      1 Reply Last reply Reply Quote 0
      • E Offline
        eri--
        last edited by

        http://snapshots.pfsense.org/FreeBSD8/HEAD/

        1 Reply Last reply Reply Quote 0
        • J Offline
          jgottlieb
          last edited by

          Great!  I'll try this out and see how the time based gateway rules work.  Thanks again for pointing me at these.

          1 Reply Last reply Reply Quote 0
          • J Offline
            jgottlieb
            last edited by

            Quick question, will the config from the 1.2 system I have work with the new version?  Or do I need to manually rebuild all the rules and config etc?

            1 Reply Last reply Reply Quote 0
            • E Offline
              eri--
              last edited by

              It should upgrade correctly.

              1 Reply Last reply Reply Quote 0
              • J Offline
                jgottlieb
                last edited by

                Well the policy based routing seems to be up and working.  The only thing that is not working right now seems to be the RRD traffic graphs.

                I've tried a few different CVS builds.  But they all seem to have the same issue.  I'm currently using:pfSense-Full-Update-2.0-ALPHA-ALPHA-20090505-1808.tgz

                I get the following error: pfSense php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'inpass' in '/var/db/rrd/wan
                -traffic.rrd'/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rr
                d-16h.png –start -57600 -e -60 --vertical-label "bits/sec" --color SHADEA#eeeee
                e --color SHADEB#eeeeee --title "hostname - WAN :: Traffic - 16 hours - 1 minu
                te average" --height 200 --width 620 -x "MINUTE:30:HOUR:1:HOUR:1:0:%H" DEF:wan-i
                n_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE DEF:wan-out_bytes_pass=/
                var/db/rrd/wan-traffic.rrd:outpass:AVERAGE DEF:wan-in_bytes_block=/var/db/rrd/wa
                n-traffic.rrd:inblock:AVERAGE DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rr
                d:outblock:AVERAGE CDEF:"wan-in_bits_pass=wan-in_bytes_pass,8," CDEF:"wan-out_b
                its_pass=wan-out_bytes_pass,8,
                " CDEF:"wan-in_bits_block=wan-in_bytes_block,8,"
                CDEF:"wan-out_bits_block=wan-out_bytes_block,8,
                " CDEF:"wan-in_bytes=wan-in_byt
                es_pass,wan-in_bytes_block,+" CDEF:"wan-out_bytes=wan-out_bytes_pass

                1 Reply Last reply Reply Quote 0
                • J Offline
                  jgottlieb
                  last edited by

                  I found a link to fix the issue - http://forum.pfsense.org/index.php/topic,10855.msg69541.html#msg69541

                  1 Reply Last reply Reply Quote 0
                  • J Offline
                    jgottlieb
                    last edited by

                    So, I'm finding that while the rules work, when the policy based routing cuts over, the actual traffic doesn't cut over for a while.  If I reset the state table, then everything routes properly.  Is there any way to do that via a script or shell command?  Then I could setup a simple cron job to reset the state table after the WAN cutover.

                    Any ideas?

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      databeestje
                      last edited by

                      What you are seeing is normal intended behaviour, I am sure you can kill the traffic, but the failover is always gradual so that stuff just keeps working.

                      I don't want filter reloads at work to shoot down the box.

                      1 Reply Last reply Reply Quote 0
                      • E Offline
                        eri--
                        last edited by

                        If you are using schedules and polict-routing rules it should be fixed in last snapshots.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.