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

    Bugs related to DNS, DHCP, Bridging and the GUI

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    18 Posts 3 Posters 5.0k 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.
    • K
      kaarposoft
      last edited by

      I need to do a complete reinstall, so I will try again, making sure I wait at least one minute for the GUI to come up.

      I am not so sure the 033de7481dacd83ee5a1a16078e89c7b4e9efd8 commit fixes the problem.
      TinyDNS is reading and writing /etc/resolv.conf, not /var/etc/nameservers_*
      But I will try it out!

      1 Reply Last reply Reply Quote 0
      • K
        kaarposoft
        last edited by

        Unfortunately, I can confirm that the fix did not work.
        I did a clean install of 20100324-0246.
        Even without TinyDNS, resolving is borked, as /etc/resolv.conf does not contain any nameservers!
        (I will continue to see if I can pinpoint the problem…)

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

          can you please show me the output of ls /var/etc/nameserver_*
          Do they have any ip on them?

          1 Reply Last reply Reply Quote 0
          • K
            kaarposoft
            last edited by

            Found the problem!

            It is in system.inc function get_nameservers. You have:

            
            $master_list[] = $item;
            
            

            but it should be:

            
            $master_list[] = $dns;
            
            
            1 Reply Last reply Reply Quote 0
            • K
              kaarposoft
              last edited by

              Regarding bug #2:

              @ermal:

              Now the GUI cannot be contacted (neither on .222 nor on .254)

              Did you gave time for it to be available?!
              Usually it will take around 40-50 seconds for the gui to restart.

              I can confirm (20100324-0246 snapshot) that after 10 minutes, neither GUI nor SSH can be contacted on .222 or .254.
              After reboot GUI and SSH are available on .254

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

                An ifconfig and netstat -rn would be useful

                1 Reply Last reply Reply Quote 0
                • K
                  kaarposoft
                  last edited by

                  netstat -f inet -l
                  shows nothing listening on any ports.

                  I will try the "netstat -rn" next time I am rebuilding the box.

                  1 Reply Last reply Reply Quote 0
                  • E
                    Efonnes
                    last edited by

                    kaarposoft: netstat -rn is for showing the routing table, not the status of ports.

                    1 Reply Last reply Reply Quote 0
                    • K
                      kaarposoft
                      last edited by

                      I know, but I can only do it when I reinstall the box!

                      1 Reply Last reply Reply Quote 0
                      • K
                        kaarposoft
                        last edited by

                        I tried again: Installing 20100324-0246, upgrading to 20100324-2048 from console.
                        Following the steps of the original post.

                        After activating the bridge and setting LAN to "none", I get:

                        
                        netstat -rn
                        Destination        Gateway            Flags    Refs      Use  Netif Expire
                        default            87.52.xx.1         UGS         0       15    vr0
                        87.52.xx.0/24      link#1             U           0      708    vr0
                        87.52.xx.120       link#1             UHS         0        0    lo0
                        127.0.0.1          link#12            UH          0     1127    lo0
                        127.0.0.2          127.0.0.1          UHS         0        0    lo0
                        192.168.yy.254     link#13            UHS         0        0    lo0
                        
                        

                        (plus a lot of IPv6; xx and yy are my sanitizing).
                        Link#1 is the LAN, #12 is lo0 and #13 is the bridge.

                        After reboot I get:

                        
                        Destination        Gateway            Flags    Refs      Use  Netif Expire
                        default            87.52.xx.1         UGS         0       47    vr0
                        87.52.xx.0/24      link#1             U           0      137    vr0
                        87.52.xx.120       link#1             UHS         0        0    lo0
                        127.0.0.1          link#12            UH          0       19    lo0
                        127.0.0.2          127.0.0.1          UHS         0        0    lo0
                        192.168.yy.0/24    link#13            U           0        1 bridge
                        192.168.yy.254     link#13            UHS         0        0    lo0
                        
                        

                        But this time, I get no working GUI even after reboot  :o

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