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

    VLAN Inaccessible and dhcp not assigning

    General pfSense Questions
    2
    5
    1.2k
    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.
    • P
      pollardhimself
      last edited by

      I've created my 4th vlan Interface "JACE"  and for some reason I cant get it to assign ip addresses and ive I manually type an IP address into a machine and I am unable to ping the 192.168.1.1 interface on VLAN 400.

      I have verified the switch is working correctly by connecting to 2 machines on 2 ports on the vLAN 400 network and they communicate.

      I set it exactly the same as the perimeter network and that is working.

      Currently Running Version 2.0-RC3

      Here's a diagram of my network before the addition of vlan 400. I am plugged directly into the 5448 switch. And the firewall/router is the pfsense server.


      1.JPG
      1.JPG_thumb
      2.JPG
      2.JPG_thumb
      3.JPG
      3.JPG_thumb
      4.JPG
      4.JPG_thumb
      5.JPG
      5.JPG_thumb
      6.JPG
      6.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Are you sure that when you set the address manually and ping 192.168.1.1 you're really pinging pfSense?

        Leave pfSense alone.  There's nothing more to change there.  Verify that VLAN 400 is properly tagged from there through the switching to vsphere to the vswitch to the VMs, etc.

        You can do a quick test of DHCP by putting an untagged vlan 400 port on the 5448 and doing a DHCP request from a test device.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • P
          pollardhimself
          last edited by

          You can do a quick test of DHCP by putting an untagged vlan 400 port on the 5448 and doing a DHCP request from a test device.

          That's exactly what I did and its not getting a IP address so I manually typed one in 192.168.1.100/24 gateway 192.168.1.1. And that couldn't ping the interface 192.168.1.1 either.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Then your VLAN's hosed.  Check that.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • P
              pollardhimself
              last edited by

              Im such a newb just thought about it I forgot to add vlan 400 to the trunk to pfsense. :o

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