Why is it so difficult to get my current ip address, subnet mask, default gateway, DNS server...

Why is it so difficult to get my current ip address, subnet mask, default gateway, DNS server, and DHCP server from a single command in Linux?

Attached: 1.jpg (575x768, 99K)

ip a

> ip a; route -n | egrep '^0'; cat /etc/resolve.conf

Everything is hard when you don't know how.

Did you even read the OP? They want all this shit at once.

OP, some of this comes down to the "not our job" mindset. ip handles........IP. DNS is a completely separate thing, and so is DHCP. That's why there's no single command to get you all of this. The exception to this is if you use a network management daemon like NetworkManager/Netctl/Wicd. Then you might have a better shot.

Does this provide the DHCP server too? I can't see how it would but I don't daily any Linux systems to know.

Because users don't need that?

IDK, I don't DHCP in my lab. You can grep your logs for 'DHCPOFFER' to get that. Normally /var/log/syslog or whatever the journald equivalent of that is.

I am using network manager, it appears that my DHCP server does not show up

I'll try it out

And yet windows has had since... Forever...Maybe because they realized someone would have to administrate their systems

what's her ip address?

idk but she's addressing my pp

That boy has a nice bum.

ipconfig /all
Come home, white man.

Do you think port 0 might be firewalled off?

Just make an alias that performs all the commands that you want

that is a boy face

nice maxi 5 cab

What ethnicity is that?

because you are a brainlet

Attached: 1551385111207.png (900x600, 770K)

can I have her IP address haha? damn what a nice ass.

>being this ignorant and retarded

$ ifconfig

It gives you 1/4th if the details I need

It really shouldn't be more difficult than a single line guys

>It really shouldn't be more difficult than a single line guys
There’s this thing called Unix made up of really small programs. When you figure out the magic keys to type to get what you need, you make what’s called a “shell script” and combine them into a new command. I suggest you call this command opisapedophile.

SwimsuitSuccubus, aka susu.

Because there are separate small tools for each functionality and putting them together in a "single command" is a trivial task.
Duplicating functionality makes no sense whatsoever from a pragmatic and resource-conservation point of view.

>tech support thread
the answer is a search engine away...

slut.com

this.

write script, chmod +x, mv net.sh /usr/lib net

also tfw no gf fuck

(what you said about networkmanager)
Imagine being this fucking retarded.
>nmcli
Shows you
>all interfaces
>their type
>what connection name you're connected to (useful for WiFi SSIDs)
>what driver the interface uses
>their addresses in CIDR notation
>routes
>MAC addresses
>DNS configuration

nmcli con show -a
nmcli con show [name]

OP, this is the true answer. nmcli is the superior command if you can operate it.

OP is a pedophile.

>just use a compiled C script
k, or just write your own. no less retarded you angry man.

imagine the smell....

>everyone uses networkmanager

Everyone who isn't out of their minds

Are you implying I can fuck that cute boy in the ass with just a one-liner?

i have a bad news for you