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

    Changing Gateway configuration results in broken gateway

    2.0-RC Snapshot Feedback and Problems - RETIRED
    5
    9
    9.8k
    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.
    • C
      casinmirad
      last edited by

      My working configuration:

      pfsense 2.0 BETA4 -Sep 23 23:45:17 - i386

      2 WANs (WAN1: PPPoE, WAN2: DHCP)
      2 Gateways (one for each WAN)
      1 Gateway Group (WAN1 + WAN2 balanced as Tier 1)

      The setup works fine, except for 2 things:

      1. If I disconnect WAN2, gateway go "offline" but pfsense still try to connect via this gateway half of time. Half of opened explorer windows just doesn't work on LAN clients.
      EDIT: WAN2 is a ADSL router, this happens when I disconnect the phone line, so WAN2 (Ethernet cable) is "up" but not connected to internet (phone line).

      2. If I change anything via webgui in WAN2 gateway, for example change "Weight" setting, the gateway go into a corrupted state: the "interface" and "gateway" setting dissapear. Pfsense show a warning: "[config.xml]pfSense is restoring the configuration /cf/conf/backup/config-1285387502.xml".
      And trying to modify or even delete the gateway is not working (clicking the "X" delete button shows no errors, but the gateway is still there)

      The image is the gateway config corrupted after trying to modify "weight" setting.
      ![gateway corrupted.png](/public/imported_attachments/1/gateway corrupted.png)
      ![gateway corrupted.png_thumb](/public/imported_attachments/1/gateway corrupted.png_thumb)

      1 Reply Last reply Reply Quote 0
      • G
        gnhb
        last edited by

        There are known issues with gateways. I'm working on several of them. See redmine.pfsense.org for details.

        GB

        1 Reply Last reply Reply Quote 0
        • T
          thomas777
          last edited by

          Hi

          The same thing happened to me. Did you find a way to resolve it, to repair the gateway.

          1 Reply Last reply Reply Quote 0
          • G
            gnhb
            last edited by

            The gateways code should be in good shape now.

            If your config is corrupted, you will probably be able to just delete the corrupted gateway entry in System => Routing screen.

            If that doesn't work, then you can restore the config from a backup, or reset to factory defaults and re-configure.

            1 Reply Last reply Reply Quote 0
            • G
              grazman
              last edited by

              Moving from the SEPT 25 build to the OCT 5 build, still not able to delete gateways or edit them, add group, etc.

              Final measure: Backup, edit backup and remove gateways (for me) with pppoe (not interfaces), manually entered monitor ip's, then restore.

              The dynamic IP interfaces recreated the gateways on reboot, with the monitor IP in the status screen, but not visible when viewing the gateway itself (monitor IP blank).

              At that point a gateway group could be created and used.

              A lingering issue perhaps is that gateway status is not updating on all gateways, showing "gathering data" one one gateway (only gateways receiving dhcp). The interface status shows it has an IP, is passing data and properly/accurately passes traffic. Is this also part of that bug, another known bug, or a new unreported bug?

              1 Reply Last reply Reply Quote 0
              • N
                n1ko
                last edited by

                I got the newest build (OCT5) also and having the same kind of trouble. Same thing on the oct4 too.

                So basicly WAN works as it should, gathering data works but WAN2 never gets a status. Always just gathering data. I tried removing the gateway and adding it again, no luck. I tried resetting factory defaults, still no luck. Both of my gateways use dhcp and both of those gateways can ping their gateways and custom servers I also tried (didnt help).

                Only difference I can see is that on status->gateways page the "monitor" table is empty for WAN2 but has an ip for WAN.

                Loadbalancing and failover doesnt work because of this so it would be awesome to get it fixed asap

                1 Reply Last reply Reply Quote 0
                • G
                  gnhb
                  last edited by

                  @grazman:

                  The dynamic IP interfaces recreated the gateways on reboot, with the monitor IP in the status screen, but not visible when viewing the gateway itself (monitor IP blank).

                  MonitorIP = Gateway IP for dynamic interfaces UNLESS you enter an alternate monitorIP and save the gateway.

                  If you've saved an alternate monitor IP because your gateway doesn't respond to pings, then it will be visible when viewing the gateway itself. Otherwise, it won't, because the code shouldn't internally save a dynamic gateway IP as a monitor IP, otherwise if your interface gets a new IP/gateway pair on the next boot or re-connect, your monitoring will not work, because it's related to the last time the link came up.

                  @grazman:

                  A lingering issue perhaps is that gateway status is not updating on all gateways, showing "gathering data" one one gateway (only gateways receiving dhcp). The interface status shows it has an IP, is passing data and properly/accurately passes traffic. Is this also part of that bug, another known bug, or a new unreported bug?

                  n1ko and grazman we need more details of your config to understand what is going on with this issue.

                  Please post your config.xml and the contents of /var/etc/apinger.conf and /tmp/apinger.status.

                  If you don't know how to get the files, just go to Diagnostics Menu => Command prompt and enter
                  cat /tmp/apinger.status
                  and press Execute button. (Same for the other file.)

                  GB

                  1 Reply Last reply Reply Quote 0
                  • N
                    n1ko
                    last edited by

                    Here you go: http://pastebin.org/64276

                    seems that status doesnt even report WAN2 altough its clearly present in the aping config. Weird.

                    1 Reply Last reply Reply Quote 0
                    • G
                      gnhb
                      last edited by

                      Thanks, that helps. It's a definite bug.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post