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

    Bridge Interface Startup Issues

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    6 Posts 3 Posters 3.6k Views
    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.
    • T
      tangel
      last edited by

      It appears that startup is having trouble bringing up my bridge interface. My intended setup is as follows:

      LAN(LAN)*                ->  re0    ->      10.14.41.1
        WAN(WAN)*                ->  xl0    ->      10.14.22.46(DHCP)
        OPT1(OPT1)              ->  re1    ->      NONE
        OPT2(OPT2)*              ->  re2    ->      NONE
        OPT3(OPT3)              ->  re3    ->      NONE
        OPT4(GigaLAN)            ->  bridge0 ->      10.14.20.1

      bridge0 = OPT1/2/3

      I can configure this while pfsense is running and everything works great. The problem is only if I reboot the bridge doesn't get setup correctly and is missing its IP and dhcpd doesn't start at all because of the missing bridge.

      My snapshot:

      FreeBSD pforta.bass.enate.org 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Tue Jan 20 14:47:04 EST 2009    sullrich@freebsd7-releng_1.bgn.pfsense.org:/usr/obj.pfSense/usr/src/sys/pfSense_SMP.7  i386

      system.log:

      {…}
      Jan 21 23:53:32 pforta kernel: ugen0: <ituner 0="" inc="" usb-lcd-20x2,="" class="" 0,="" rev="" 2<br="">.00/0.01, addr 2> on uhub2
      Jan 21 23:53:32 pforta kernel: Timecounters tick every 1.000 msec
      Jan 21 23:53:32 pforta kernel: IPsec: Initialized Security Association Processin
      g.
      Jan 21 23:53:32 pforta kernel: ad1: 95396MB <seagate st910021as="" 4.06="">at ata0-sl
      ave SATA150
      Jan 21 23:53:32 pforta kernel: SMP: AP CPU #1 Launched!
      Jan 21 23:53:32 pforta kernel: Trying to mount root from ufs:/dev/ad1s1a
      Jan 21 23:53:32 pforta kernel: re0: link state changed to UP
      Jan 21 23:53:32 pforta kernel: re0: link state changed to DOWN
      Jan 21 23:53:33 pforta kernel: re1: link state changed to DOWN
      Jan 21 23:53:33 pforta kernel: re2: link state changed to UP
      Jan 21 23:53:33 pforta kernel: re2: link state changed to DOWN
      Jan 21 23:53:33 pforta kernel: re3: link state changed to DOWN
      Jan 21 23:53:33 pforta php: : The command '/sbin/ifconfig 'bridge0' '10.14.20.1/
      24'' returned exit code '1', the output was 'ifconfig: interface bridge0 does no
      t exist'
      Jan 21 23:53:33 pforta php: : The command '/sbin/ifconfig 'bridge0' up' returned
      exit code '1', the output was 'ifconfig: interface bridge0 does not exist'
      Jan 21 23:53:33 pforta kernel: xl0: link state changed to UP
      Jan 21 23:53:33 pforta php: : Could not bring realwanif up in interface_dhcp_con
      figure()
      Jan 21 23:53:33 pforta dhclient: netstat
      Jan 21 23:53:33 pforta dhclient: PREINIT
      Jan 21 23:53:33 pforta dhclient[16452]: DHCPREQUEST on xl0 to 255.255.255.255 po
      rt 67
      Jan 21 23:53:33 pforta sshd[19027]: Server listening on :: port 22.
      Jan 21 23:53:33 pforta sshd[19027]: Server listening on 0.0.0.0 port 22.
      Jan 21 23:53:33 pforta dhclient[16452]: DHCPACK from 10.14.22.1
      Jan 21 23:53:33 pforta dhclient: netstat
      Jan 21 23:53:33 pforta dhclient: REBOOT
      Jan 21 23:53:33 pforta sshlockout[19064]: sshlockout starting up
      Jan 21 23:53:33 pforta sshlockout[19064]: sshlockout starting up
      Jan 21 23:53:33 pforta dhclient: Starting add_new_address()
      Jan 21 23:53:33 pforta dhclient: ifconfig xl0 inet 10.14.22.46 netmask 255.255.2
      55.0 broadcast 10.14.22.255
      Jan 21 23:53:33 pforta dhclient: New IP Address (xl0): 10.14.22.46
      Jan 21 23:53:33 pforta dhclient: New Subnet Mask (xl0): 255.255.255.0
      Jan 21 23:53:33 pforta dhclient: New Broadcast Address (xl0): 10.14.22.255
      Jan 21 23:53:33 pforta dhclient: New Routers (xl0): 10.14.22.1
      Jan 21 23:53:33 pforta dhclient: Adding new routes
      Jan 21 23:53:33 pforta dhclient: /sbin/route add default 10.14.22.1
      Jan 21 23:53:33 pforta dhclient: Creating resolv.conf
      Jan 21 23:53:33 pforta dhclient[16452]: bound to 10.14.22.46 – renewal in 10800
      0 seconds.
      Jan 21 23:53:34 pforta php: : The command '/sbin/ifconfig bridge0 destroy' retur
      ned exit code '1', the output was 'ifconfig: interface bridge0 does not exist'
      Jan 21 23:53:34 pforta kernel: bridge0: Ethernet address: 46:26:1f:bb:22:42
      Jan 21 23:53:34 pforta php: : The command '/sbin/ifconfig ''''re1'''' up' retu
      rned exit code '1', the output was 'ifconfig: interface 're1' does not exist'
      Jan 21 23:53:34 pforta kernel: re1: promiscuous mode enabled
      Jan 21 23:53:34 pforta php: : The command '/sbin/ifconfig ''''re2'''' up' retu
      rned exit code '1', the output was 'ifconfig: interface 're2' does not exist'
      Jan 21 23:53:34 pforta kernel: re2: promiscuous mode enabled
      Jan 21 23:53:34 pforta php: : The command '/sbin/ifconfig ''''re3'''' up' retu
      rned exit code '1', the output was 'ifconfig: interface 're3' does not exist'

      {...}</seagate></ituner>

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by

        I did a bunch of testing and experienced similar problems.  I believe its a 2.0 bug.  You can see my work and the advise of others here.  http://forum.pfsense.org/index.php/topic,12101.msg73547.html#msg73547  If you have any questions with what I have done or ideas how to troubleshoot this problem further, feel free to PM me.

        Good luck,
        -V

        1 Reply Last reply Reply Quote 0
        • T
          tangel
          last edited by

          Do you know if we should open a bug for them or do other people do that from reading the forums?

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            If you find a bug, make a post on the forum.  There are a couple posts detailing this issue not to mention I sent a PM to one of the ADMINS asking the same question as well as describing this issue.  I switched back to 1.2.3 for the time but will setup my test PC with 2.0 as soon as I finish another project.

            Good luck,
            -V

            1 Reply Last reply Reply Quote 0
            • E
              eri--
              last edited by

              This should be fixed on the latest snapshots.

              1 Reply Last reply Reply Quote 0
              • T
                tangel
                last edited by

                Verified as fixed.

                Thank you!

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