Navigation

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

    No IP when the Storage (QNAP) directly attached to the pfSense

    General pfSense Questions
    2
    3
    725
    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
      MacUsers last edited by

      Hi there,

      I've just upgraded to a SuperMicro, with a 4-port Intel I350-T4 attached to it. I created a LAGG on port igb2 & igb3:

      lagg1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
      	options=400fb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,polling,vlan_hwcsum,vlan_hwtso>ether a0:36:9f:03:8d:ea
      	inet6 fe80::a236:9fff:fe03:8dea%lagg1 prefixlen 64 scopeid 0x10 
      	inet 10.0.13.1 netmask 0xfffffff8 broadcast 10.0.13.7 
      	nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
      	status: active
      	laggproto lacp lagghash l2,l3,l4
      	laggport: igb2 flags=18 <collecting,distributing>laggport: igb3 flags=1c<active,collecting,distributing></active,collecting,distributing></collecting,distributing></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,polling,vlan_hwcsum,vlan_hwtso></up,broadcast,running,simplex,multicast>
      

      Then I created an interface: QNAP and assigned LAGG1 assigned to it: QNAP (opt4) -> lagg1 -> v4: 10.0.13.1/29

      
       <opt4><if>lagg1</if>
          <enable><ipaddr>10.0.13.1</ipaddr>
          <subnet>29</subnet>
          <blockbogons><spoofmac></spoofmac></blockbogons></enable></opt4> 
      
      

      I also have a matching FW rule:

      
      97:block drop in log quick on lagg1 from <bogons>to any label "block bogon IPv4 networks from QNAP"
      140:pass in quick on lagg1 inet from any to 10.0.13.0/29 flags S/SA keep state label "USER_RULE: Default Rule for QNAP to any"
      141:pass in quick on lagg1 inet from 10.0.13.0/29 to any flags S/SA keep state label "USER_RULE: Default allow QNAP NET to any rule"</bogons> 
      

      and a DHCP server config, that hosts the 10.0.13.0/29 network.

      On the QNAP (TS-451), I have Port Trunking enabled in 802.3ad dynamic [Layer 2+3 (Mac + IP)] mode on two interfaces. But when I connect the NAS to to pfSense, it cannot get the IP out of it. All I'm getting a 169.254.100.100 self-assigned IP. I tried whatever I possibly can think of, but nothing work. I also get the same self-assigned IP, if I put a switch in between.

      I'm completely running out of ideas. What am I doing wrong here? Can any one pls help? Thanks in advance!

      -San

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

        Does the lagg come up?

        Did you enable a DHCP server?

        Why not just assign 10.0.13.2/29 to the QNAP LACP interface?

        Not sure why you wouldn't use a switch for this but that's probably just me.

        1 Reply Last reply Reply Quote 0
        • M
          MacUsers last edited by

          @Derelict:

          Does the lagg come up?

          I think it did but what do you exactly mean?

          @Derelict:

          Did you enable a DHCP server?

          Yes, it's enabled (attached). All other DHCPs are working fine though.

          @Derelict:

          Why not just assign 10.0.13.2/29 to the QNAP LACP interface?

          You mean instead of dynamic, assign that IP on the QNAP? I'll try that in couple of hrs. time

          @Derelict:

          Not sure why you wouldn't use a switch for this but that's probably just me.

          The main reason is: The storage is used buy several other devices (security camera, A/W receiver etc.) from various part of the house, connected through different switches (and from out side) and I didn't want to lose the access to the storage, in case a switch went down. If pfSense has gone down, I take it as a game over. I'm open to other suggestions though.


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

          Products

          • Platform Overview
          • TNSR
          • pfSense
          • Appliances

          Services

          • Training
          • Professional Services

          Support

          • Subscription Plans
          • Contact Support
          • Product Lifecycle
          • Documentation

          News

          • Media Coverage
          • Press
          • Events

          Resources

          • Blog
          • FAQ
          • Find a Partner
          • Resource Library
          • Security Information

          Company

          • About Us
          • Careers
          • Partners
          • Contact Us
          • Legal
          Our Mission

          We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

          Subscribe to our Newsletter

          Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

          © 2021 Rubicon Communications, LLC | Privacy Policy