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

    Adding vlan to physical interface downs connection on other physical interface

    2.0-RC Snapshot Feedback and Problems - RETIRED
    2
    2
    1.4k
    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.
    • C
      clarknova
      last edited by

      2.0-BETA4
      built on Sat Aug 7 15:30:29 UTC 2010
      FreeBSD 8.1-RELEASE
      AMD64

      To recreate:

      1. Create mlppp bundle from vlans on em0 and connect
      2. Create interfaces with static IPs on vlans on em1 and enable dhcp servers
      3. Connect hosts to subnets on em1 vlans
      4. Create a new vlan on em1
      5. Create and enable interface with static IP on new vlan

      At this point the LAN interfaces will become unresponsive for 30-60 seconds. When the pfsense web UI becomes responsive the WAN PPPoE interface will have a new IP address.

      I don't know if this is known behaviour, but I consider it undesirable, as I don't want to disrupt everybody's service to create an interface. Obviously  all states involving the WAN (at least) will be broken by this, gravely affecting voip, gaming, video streaming, etc.

      Is this something that can or will be improved?

      db

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        Interfaces will drop when you add one at interfaces>assign, though I'm seeing 6-8 seconds or so. The longer delay, and what seems like a delay in a different area, is likely MLPPP related. Doubt if that will change for 2.0 release, though that depends on gnhb likely, he may know how to fix it.

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