ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    BRRABill's Field Report With Linux

    IT Discussion
    14
    148
    14.1k
    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.
    • S
      scottalanmiller @BRRABill
      last edited by

      @BRRABill said in BRRABill's Field Report With Linux:

      Linux QOTD (Question Of The Day)

      My XO instance (Ubuntu 16.04) does not automatically grab an IP address on reboot.

      How do I remedy that?

      Do you want it to grab one (DHCP) or to have one (Static)?

      B 1 Reply Last reply Reply Quote 0
      • B
        BRRABill @scottalanmiller
        last edited by

        @scottalanmiller said in BRRABill's Field Report With Linux:

        @BRRABill said in BRRABill's Field Report With Linux:

        Linux QOTD (Question Of The Day)

        My XO instance (Ubuntu 16.04) does not automatically grab an IP address on reboot.

        How do I remedy that?

        Do you want it to grab one (DHCP) or to have one (Static)?

        Grab one.

        I've never actually had this issue. It has always grabbed one.

        Not sure what happened to this instance.

        Stupid Linux.

        S 1 Reply Last reply Reply Quote 0
        • S
          stacksofplates @BRRABill
          last edited by

          @BRRABill said in BRRABill's Field Report With Linux:

          @scottalanmiller said in BRRABill's Field Report With Linux:

          @BRRABill said in BRRABill's Field Report With Linux:

          Linux QOTD (Question Of The Day)

          My XO instance (Ubuntu 16.04) does not automatically grab an IP address on reboot.

          How do I remedy that?

          Do you want it to grab one (DHCP) or to have one (Static)?

          Grab one.

          I've never actually had this issue. It has always grabbed one.

          Not sure what happened to this instance.

          Stupid Linux.

          Is the networking daemon starting when the system starts?

          What's your /etc/network/interfaces file look like?

          B 1 Reply Last reply Reply Quote 2
          • B
            BRRABill @stacksofplates
            last edited by BRRABill

            @stacksofplates said

            Is the networking daemon starting when the system starts?

            What's your /etc/network/interfaces file look like?

            As a Linux noob, never been in that file before.

            But after going into it, I immediately know (I think) what the issue was.

            It has eth1 and ifconfig shows eth0.

            Yep, that was it. More knowledge, mmmmmm!

            # This file describes the network interfaces available on your system
            # and how to activate them. For more information, see interfaces(5).
            
            source /etc/network/interfaces.d/*
            
            # The loopback network interface
            auto lo
            iface lo inet loopback
            
            # The primary network interface
            auto eth1
            iface eth1 inet dhcp
            ~
            
            1 Reply Last reply Reply Quote 3
            • M
              momurda
              last edited by

              I think you mean ip addr
              ifconfig is old-hat, apparently. I still in habit of using ifconfig myself.

              B 1 Reply Last reply Reply Quote 1
              • B
                BRRABill @momurda
                last edited by

                @momurda said in BRRABill's Field Report With Linux:

                I think you mean ip addr
                ifconfig is old-hat, apparently. I still in habit of using ifconfig myself.

                I started way back in the day of using ifconfig and just haven't broken out of it it.

                Way back in the day meaning like July.

                1 Reply Last reply Reply Quote 1
                • D
                  dafyre
                  last edited by

                  I'll likely keep typing it until it starts saying:

                  "Command not found, use ip addr, ya idjit"

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    scottalanmiller @dafyre
                    last edited by

                    @dafyre said in BRRABill's Field Report With Linux:

                    I'll likely keep typing it until it starts saying:

                    "Command not found, use ip addr, ya idjit"

                    You can fix that with an alias.

                    D 1 Reply Last reply Reply Quote 0
                    • S
                      scottalanmiller
                      last edited by

                      ifconfig is deal, long live ip addr

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        travisdh1 @scottalanmiller
                        last edited by

                        @scottalanmiller said in BRRABill's Field Report With Linux:

                        ifconfig is deal, long live ip a

                        FYFY - cause I'm lazy, and that's all I type out

                        1 Reply Last reply Reply Quote 0
                        • D
                          dafyre @scottalanmiller
                          last edited by

                          @scottalanmiller said in BRRABill's Field Report With Linux:

                          @dafyre said in BRRABill's Field Report With Linux:

                          I'll likely keep typing it until it starts saying:

                          "Command not found, use ip addr, ya idjit"

                          You can fix that with an alias.

                          True. But at that point, I'd likely just sigh and type the correct command.

                          1 Reply Last reply Reply Quote 2
                          • B
                            BRRABill
                            last edited by

                            QOTD:

                            So I installed Ubuntu 16.10 yesterday to set up a Unifi cloud controller.

                            I followed some pretty simple directions here which had me "setup the iptables" firewall.
                            https://community.ubnt.com/t5/UniFi-Wireless/Step-by-Step-Walkthrough-Set-up-Unifi-Cloud-Controller-v-4-7-6/td-p/1324666

                            But I have seen most articles reference ufw as the firewall in Ubuntu, a "front end" for iptables.

                            So, can someone explain what the heck these two things are? Are they two separate things that should not be used together?

                            ufw was installed but not enabled on my install. Is iptables enabled by default on fresh installs?

                            T 1 Reply Last reply Reply Quote 0
                            • T
                              travisdh1 @BRRABill
                              last edited by

                              @BRRABill said in BRRABill's Field Report With Linux:

                              QOTD:

                              So I installed Ubuntu 16.10 yesterday to set up a Unifi cloud controller.

                              I followed some pretty simple directions here which had me "setup the iptables" firewall.
                              https://community.ubnt.com/t5/UniFi-Wireless/Step-by-Step-Walkthrough-Set-up-Unifi-Cloud-Controller-v-4-7-6/td-p/1324666

                              But I have seen most articles reference ufw as the firewall in Ubuntu, a "front end" for iptables.

                              So, can someone explain what the heck these two things are? Are they two separate things that should not be used together?

                              ufw was installed but not enabled on my install. Is iptables enabled by default on fresh installs?

                              iptables is the user-space application to configure the tables kernel firewall. Almost every Linux based firewall app uses iptables in the background to do it's work. So this ufw is just another way to manage the firewall. Leave it to Ubuntu to do something odd.

                              I'd hope a firewall is enabled by default, that it's missing as default in CentOS7-1511 is super annoying.

                              B 1 Reply Last reply Reply Quote 0
                              • B
                                BRRABill @travisdh1
                                last edited by

                                @travisdh1 said in BRRABill's Field Report With Linux:

                                @BRRABill said in BRRABill's Field Report With Linux:

                                QOTD:

                                So I installed Ubuntu 16.10 yesterday to set up a Unifi cloud controller.

                                I followed some pretty simple directions here which had me "setup the iptables" firewall.
                                https://community.ubnt.com/t5/UniFi-Wireless/Step-by-Step-Walkthrough-Set-up-Unifi-Cloud-Controller-v-4-7-6/td-p/1324666

                                But I have seen most articles reference ufw as the firewall in Ubuntu, a "front end" for iptables.

                                So, can someone explain what the heck these two things are? Are they two separate things that should not be used together?

                                ufw was installed but not enabled on my install. Is iptables enabled by default on fresh installs?

                                iptables is the user-space application to configure the tables kernel firewall. Almost every Linux based firewall app uses iptables in the background to do it's work. So this ufw is just another way to manage the firewall. Leave it to Ubuntu to do something odd.

                                I'd hope a firewall is enabled by default, that it's missing as default in CentOS7-1511 is super annoying.

                                The "odd" thing is that when I use ufw to list the rules in place (in iptables) nothing is listed.

                                Which makes me wonder if they are separate things...

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  travisdh1 @BRRABill
                                  last edited by

                                  @BRRABill said in BRRABill's Field Report With Linux:

                                  @travisdh1 said in BRRABill's Field Report With Linux:

                                  @BRRABill said in BRRABill's Field Report With Linux:

                                  QOTD:

                                  So I installed Ubuntu 16.10 yesterday to set up a Unifi cloud controller.

                                  I followed some pretty simple directions here which had me "setup the iptables" firewall.
                                  https://community.ubnt.com/t5/UniFi-Wireless/Step-by-Step-Walkthrough-Set-up-Unifi-Cloud-Controller-v-4-7-6/td-p/1324666

                                  But I have seen most articles reference ufw as the firewall in Ubuntu, a "front end" for iptables.

                                  So, can someone explain what the heck these two things are? Are they two separate things that should not be used together?

                                  ufw was installed but not enabled on my install. Is iptables enabled by default on fresh installs?

                                  iptables is the user-space application to configure the tables kernel firewall. Almost every Linux based firewall app uses iptables in the background to do it's work. So this ufw is just another way to manage the firewall. Leave it to Ubuntu to do something odd.

                                  I'd hope a firewall is enabled by default, that it's missing as default in CentOS7-1511 is super annoying.

                                  The "odd" thing is that when I use ufw to list the rules in place (in iptables) nothing is listed.

                                  Which makes me wonder if they are separate things...

                                  Wait... Ubuntu.... and more crazy Ubuntu type things. I don't think they enable the firewall by default. They say "Just don't run a service you don't need." instead, don't they?

                                  B DashrenderD 2 Replies Last reply Reply Quote 0
                                  • B
                                    BRRABill @travisdh1
                                    last edited by

                                    @travisdh1 said

                                    Wait... Ubuntu.... and more crazy Ubuntu type things. I don't think they enable the firewall by default. They say "Just don't run a service you don't need." instead, don't they?

                                    Well, that's part of m question as well.

                                    From a little reading, it appears there is no firewall by default, because no ports are open.

                                    But then all you have to do is add ports into iptables, and that enables it?

                                    This is why I am confused.

                                    T DashrenderD 2 Replies Last reply Reply Quote 0
                                    • T
                                      travisdh1 @BRRABill
                                      last edited by

                                      @BRRABill said in BRRABill's Field Report With Linux:

                                      @travisdh1 said

                                      Wait... Ubuntu.... and more crazy Ubuntu type things. I don't think they enable the firewall by default. They say "Just don't run a service you don't need." instead, don't they?

                                      Well, that's part of m question as well.

                                      From a little reading, it appears there is no firewall by default, because no ports are open.

                                      But then all you have to do is add ports into iptables, and that enables it?

                                      This is why I am confused.

                                      Nope. You want a web server on port 80, just install apache2. Done.

                                      1 Reply Last reply Reply Quote 0
                                      • DashrenderD
                                        Dashrender @BRRABill
                                        last edited by

                                        @BRRABill said in BRRABill's Field Report With Linux:

                                        @travisdh1 said

                                        Wait... Ubuntu.... and more crazy Ubuntu type things. I don't think they enable the firewall by default. They say "Just don't run a service you don't need." instead, don't they?

                                        Well, that's part of m question as well.

                                        From a little reading, it appears there is no firewall by default, because no ports are open.

                                        But then all you have to do is add ports into iptables, and that enables it?

                                        This is why I am confused.

                                        No adding ports to iptables doesn't not enable it - you'd have to start the service that enables it, and then open the required ports (I suppose you could do it either one first, but if you don't enable the service, then there is no firewall running)

                                        B 1 Reply Last reply Reply Quote 1
                                        • B
                                          BRRABill @Dashrender
                                          last edited by

                                          @Dashrender said i

                                          No adding ports to iptables doesn't not enable it - you'd have to start the service that enables it, and then open the required ports (I suppose you could do it either one first, but if you don't enable the service, then there is no firewall running)

                                          Are you sure about that?

                                          iptables is just the interface to the firewall, which I think is always running.

                                          Now, by default, it is allowing everything.

                                          I set up another fresh droplet for testing, and this is what iptables -L gives me

                                          Chain INPUT (policy ACCEPT)
                                          Chain FORWARD (policy ACCEPT)
                                          Chain OUTPUT (policy ACCEPT)
                                          
                                          T 1 Reply Last reply Reply Quote 0
                                          • DashrenderD
                                            Dashrender @travisdh1
                                            last edited by

                                            yep, I'm sure IF the following is correct and the firewall is not enabled by default as mentioned below.

                                            @travisdh1 said in BRRABill's Field Report With Linux:

                                            Wait... Ubuntu.... and more crazy Ubuntu type things. I don't think they enable the firewall by default. They say "Just don't run a service you don't need." instead, don't they?

                                            B 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 8
                                            • 4 / 8
                                            • First post
                                              Last post