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

    Upgrade from 2.6 to 2.7 Cannot ping gateway now

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 333 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
      joezyz
      last edited by joezyz

      Hello everyone.

      I've found several posts with the same issues but nothing seems to work.

      On Proxmox VM.
      WAN (Static IP) 209.195.19.229\24
      LAN 192.168.1.1\24
      Gateway 209.195.10.225

      Before update All working fine.

      After update, Cannot VPN into machine, cannot ping default gateway.
      I CAN ping all other machines on the system side of the gateway (209.195.10.226-209.195.10.230).
      All the other machines CAN ping the gateway AND the internet. (i.e. 8.8.8.8)

      From PROXMOX, I can ping fine ping the gateway AND the internet. (i.e. 8.8.8.8)

      I'm at a loss. I've changed the virtual NIC's, reset the WAN via the console.
      I DONT have access the the GUI, I had access before via VPN, but now I cannot get access (I am remote from the box)

      I've removed and added the gateway via the cli multiple times. In the config.xml file the gateway shows:
      <gateway>WANGW<\gateway>
      I've changed the WAN to 209.195.19.229\30 as some suggested

      Not sure what happed. I upgraded via the GUI. Of course I didn't back anything up.

      Any ideas?

      Edit: Ping 209.195.10.225 returns Ping: Sendto: Host is down.
      But, as I said, all other machines ping this fine....

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        No default route is what initially comes to mind. However if it's showing 'host is down' that means the gateway is not responding to ARP. Since it clearly is responding to ARP from the other hosts in the subnet I'd check for something low level like an interface reorder perhaps.
        Also that subnet looks like a /29 not /30.

        Steve

        J 1 Reply Last reply Reply Quote 0
        • J
          joezyz @stephenw10
          last edited by

          Well, I was wasting too much time. I blew away the build and rebuilt from scratch. Working fine now with exact same settings.

          Very disappointed that a working site is brought down by upgrading.

          Thanks for the reply and the attempt to help me.

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