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

    Bridgining without a primary interface

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 3 Posters 3.5k 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.
    • G
      gilf
      last edited by

      Hi,

      I am trying the following on a wrap, beta01.

      sis0 - wan (PPPoE)
      sis1 - lan (DHCP)
      sis2 - bridge to lan
      ath0 - bridge to lan

      This seems to work well, as long as sis1 is physicaly up (i.e. attached to a working device). If sis1 is down (no device, device is off or suspended), the other bridged devices will not get an IP address. I don't think that this is a bug, as I don't think bridging was designed to work this way, but I wonder if there is a way to get bridging to work, no matter which physical interface is up.

      Thanks

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by

        Why would you do such a thing?  Why not just physicall plug up sis1 and don't bridge it a second time to a unused lan?

        1 Reply Last reply Reply Quote 0
        • G
          gilf
          last edited by

          @sullrich:

          Why would you do such a thing?  Why not just physicall plug up sis1 and don't bridge it a second time to a unused lan?

          A. Sometimes the only device in use will be a wireless laptop.
          B. Sometimes the device on sis1 will be shut down (or suspended) and I want to reduce the help desk calls….

          1 Reply Last reply Reply Quote 0
          • S
            sullrich
            last edited by

            Okay, in a nutshell, I don't think this will work.

            Hook up a 2 port switch to the port in question and you're problem will go away (or should).

            1 Reply Last reply Reply Quote 0
            • G
              gilf
              last edited by

              @sullrich:

              Okay, in a nutshell, I don't think this will work.

              Hook up a 2 port switch to the port in question and you're problem will go away (or should).

              Sigh….. I thought as much. Thanks.

              1 Reply Last reply Reply Quote 0
              • A
                arno
                last edited by

                Hi, gilf, hi Scott!
                I solved this problem without additional soapbox (hub).
                I just mapped LAN interface to ath0, which is "virtually" always on.

                
                *** Welcome to pfSense 1.0-BETA1-TESTING-SNAPSHOT-2-5-06-embedded on pfsense ***
                
                  OPT2(LANBRIDGE)          ->   sis0    ->      NONE
                  WAN*                     ->   sis1    ->      172.16.128.11(DHCP)
                  OPT1(DMZ)                ->   sis2    ->      192.168.2.1
                  LAN                      ->   ath0    ->      192.168.1.1
                
                

                …and here is my ifconfig output -

                
                sis0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>mtu 1500
                        options=8 <vlan_mtu>inet6 fe80::200:24ff:fec5:6ebc%sis0 prefixlen 64 scopeid 0x1 
                        ether 00:00:24:c5:6e:bc
                        media: Ethernet autoselect (none)
                        status: no carrier
                sis1: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500
                        options=8 <vlan_mtu>inet6 fe80::200:24ff:fec5:6ebd%sis1 prefixlen 64 scopeid 0x2 
                        inet 172.16.128.11 netmask 0xffff0000 broadcast 172.16.255.255
                        ether 00:00:24:c5:6e:bd
                        media: Ethernet autoselect (100baseTX <full-duplex>)
                        status: active
                sis2: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500
                        options=8 <vlan_mtu>inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
                        inet6 fe80::200:24ff:fec5:6ebe%sis2 prefixlen 64 scopeid 0x3 
                        ether 00:00:24:c5:6e:be
                        media: Ethernet autoselect (none)
                        status: no carrier
                ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>mtu 1500
                        inet6 fe80::20b:6bff:fe37:579d%ath0 prefixlen 64 scopeid 0x4 
                        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
                        ether 00:0b:6b:37:57:9d
                        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated
                        ssid mms channel 1 bssid 00:0b:6b:37:57:9d
                        authmode WPA privacy MIXED deftxkey 2 AES-CCM 2:128-bit
                        AES-CCM 3:128-bit txpowmax 40 protmode OFF burst dtimperiod 1
                        bintval 100
                pfsync0: flags=41 <up,running>mtu 2020
                        pfsync: syncdev: lo0 maxupd: 128
                pflog0: flags=100 <promisc>mtu 33208
                lo0: flags=8049 <up,loopback,running,multicast>mtu 16384
                        inet 127.0.0.1 netmask 0xff000000 
                        inet6 ::1 prefixlen 128 
                        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 
                bridge0: flags=8043 <up,broadcast,running,multicast>mtu 1500
                        ether ac:de:48:f9:56:39
                        priority 32768 hellotime 2 fwddelay 15 maxage 20
                        member: sis0 flags=3 <learning,discover>member: ath0 flags=3 <learning,discover></learning,discover></learning,discover></up,broadcast,running,multicast></up,loopback,running,multicast></promisc></up,running></hostap></up,broadcast,running,promisc,simplex,multicast></vlan_mtu></up,broadcast,running,simplex,multicast></full-duplex></vlan_mtu></up,broadcast,running,simplex,multicast></vlan_mtu></up,broadcast,running,promisc,simplex,multicast> 
                

                I think - problem still exists, with two ethernet interfaces and without wireless i need hub again ;(
                Thanks, Arnis.

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