BRRABill's Field Report With Linux

scottalanmiller

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

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

@DustinB3403 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:

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

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

@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:

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

@BRRABill Adding a second drive to a VM is literally nothing though.

It would be better practice to add a drive, than to try and extend the existing one.

But in theory, that 15G partition is part of the 19.5GB VHD the GrayLog appliance sets up.

You're losing the 15G, right?

I know 15G isn't much, but I was just thinking for future reference, if it was more than 15G.

Losing 15GB? Not if you are thin provisioned.

Well, as of right now, this is how things rolled...

Imported the GrayLog OVA appliance to XS.

It creates a 19.5GB virtual disk where it does its magic.

Part of that magic is this 15GB partition that is now full.

So, even thin provisioned, isn't that space already taken? (AKA once the data fills it, it still uses it even if the data is deleted, correct?)

Sure it is, but after you copy that data to the new drive, you'll delete it from the old drive making it empty... Assuming XS can reclaim now empty space, you'll gain that 15 GB back.

Yes, in reality this is all that you do. Make a new one, remove the old.

But in this particular appliance scenario, that is not possible, correct?

I don't have the appliance in front of me, are there not separate disks for these things?

No, the OVA imports a single disk with 2 LV's.

That's bad design.

Why?

Using partitions instead of VHDs is pre-virtualization thinking. You lack the control that you should have. You lose benefits and gain none.

BRRABill

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?

scottalanmiller

@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)?

BRRABill

@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.

stacksofplates

@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?

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
~

momurda

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

BRRABill

@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.

dafyre

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

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

scottalanmiller

@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.

scottalanmiller

ifconfig is deal, long live ip addr

travisdh1

@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

dafyre

@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.

BRRABill

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?

travisdh1

@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.

BRRABill

@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...

travisdh1

@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?

BRRABill

@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.

travisdh1

@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.

Dashrender

@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)