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

    Unable to route a static public IP over VLAN

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 2 Posters 480 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.
    • M
      mbaughan
      last edited by

      I have a tenant on my network (business centre) that require a public IP range.

      I have applied for a /28 from my ISP, which they have granted. Lets say this is 52.232.217.240/28. I have asked them to route it to a next-hop IP of my pfSense WAN IP - 52.132.180.66, they have done this.

      I want to take a /30 portion of this routed range and assign it to a VLAN. I have created a VLAN ID 111 and created an interface with the IP 52.232.217.241, subnet 255.255.255.252. I have made all the required VLAN settings on the managed switch, created the firewall rules to allow all traffic in and out and set my laptop's network card up as follows -

      IP: 52.232.217.242
      Subnet: 255.255.255.252
      GW: 52.232.217.241

      DNS: 8.8.8.8, 8.8.4.4

      I can ping the gateway from another network - 52.232.217.241, but I can't ping the laptop (with Windows firewall disabled) - 52.232.217.242

      Outbound NAT is set to 'Manual Outbound NAT rule generation', with 1:1 NAT's for all the other VLAN's.

      Any ideas why I am not getting an internet connection from the laptop?

      Thanks

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

        @dynamicuser:

        I have asked them to route it to a next-hop IP of my pfSense WAN IP - 52.132.180.66, they have done this.

        What does that exactly mean? Is there a local gateway on that new subnet?

        I guess the ISP placed the new subnet on the same WAN link? You would need Virtual IPs if this is the case.

        If it ain't broke, you haven't tampered enough with it

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