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

    [solved] second LAN-interface not working correctly

    Problems Installing or Upgrading pfSense Software
    solved
    2
    3
    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.
    • K
      karls0
      last edited by karls0

      When I installed my pfsense-box I only needed LAN and WAN ports, but I installed an additional NIC (Intel 82574L Gigabit).

      Today I wanted to use this interface for a second LAN. I assigned a fixed IP address and gave it a name (UPS in my case). I also created a firewall-rule any/any on interface UPS. I can ping this interface from my LAN network, but dont get a response when pinging from a machine on the UPS-network. Packet trace on the pfsense-box, UPS-interface, shows the echo request packages, but no replys :-((
      Any help appreciated,
      Karl

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

        Look at the protocol on the firewall rule on UPS. If it is TCP change it to any.

        If that doesn't fix it, post your interface configuration and the rule set on that interface.

        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
        • K
          karls0
          last edited by

          Thank you for your time Derelic. I looked at the interfce settings and found out, that I had left the subnet-setting for the interface at /32 instead of changing it to /24.
          Maybe this setting is bit confusing, because if I should set a single IP-address for the router interface and not a subnet. I suggest giving this setting a separate line or at least a caption "subnet size" or something similar.
          Anyway - excuse my dumbness.
          Best, Karl

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