Navigation

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

    Automatic interface assignment?

    Installation and Upgrades
    2
    3
    1694
    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.
    • Z
      zbuzanic last edited by

      Is it possible to add automatic assignment for interfaces.
      Sometimes I have situation when I have to reset to default pfsense and I don't have monitor/kayboard, so what I'd like to see is to automaticaly assign ethernet interface to 192.168.1.1/24 after 60 seconds, and to set all other interfaces to dhcp. Think that would be really great.

      1 Reply Last reply Reply Quote 0
      • H
        hoba last edited by

        Maybe a not so "unpredictable" half-automatic sequence might make sense.

        System with unassigned interfaces goes to automatic link up sensing by default. Then you have to plug in cables in the order LAN, WAN, OPT1, OPT2,… . When system awaits a link up on an interface we could force this by a beepjingle. Now you can either start configuration via console or just plug a cable. Single beep confirms LAN interface assignment, dual beep confirms WAN, tripple beep confirms OPT1,... As you always need at least WAN and LAN these steps should have no timeout. For OPT1,2,3,... a 20 second timeout could finish the sequence and play another jingle. This procedure wouldn't involve any keypress/input/output at all and still the interface assignment is not unpredictable.

        I'm not sure though if it's worth the effort and if somebody is willing to code it  ;)

        1 Reply Last reply Reply Quote 0
        • Z
          zbuzanic last edited by

          What we need is forcing interfaces to some default IP's so we can get acess to it via wireless, that's the main problem, or at least to force LAN, and skip other interfaces (DHCP) so the system would be acessible via LAN.
          Anyway… yup, it's not a worthy feature, maybe with some bonty? ;)

          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