Skip to main content ↑ ↓

Poll

How do you set your ip address?

connman
[ 1 ] (11.1%)
networkmanager
[ 5 ] (55.6%)
ifupdown
[ 0 ] (0%)
iproute
[ 0 ] (0%)
through DE GUI
[ 1 ] (11.1%)
netifrc
[ 2 ] (22.2%)

Total Members Voted: 9

Topic: ip address configuration census. (Read 3638 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

ip address configuration census.

I'm curious on how people here on Artix set them up. I'm thinking of making a short guide (for option 4), but I'm hesitant to do so because it is probably redundant because of the Arch wiki: https://wiki.archlinux.org/title/Network_configuration. As well as I don't think I can make one for wireless devices as well as I've no laptop to test it on. And I'm not sure if people even care for such things.

Notes:

1.) ifupdown is an external package for those who do not know you would need to compile it: https://aur.archlinux.org/packages/ifupdown-ng

2.) iproute is the manual way. No network connection managers.

Re: ip address configuration census.

Reply #1 –
netifrc

Re: ip address configuration census.

Reply #2 –
Quote from: gripped – on
netifrc
Didn't knew about this one, let me add it to the poll. Learned a new one today. Thanks.

Edit:
1.) upon checking it out at: https://wiki.gentoo.org/wiki/Netifrc. It seems similar to ifupdown in how to set it up/usage. Both are lighter than the more commonly used networkmanager and connman. I like it.

Re: ip address configuration census.

Reply #3 –
Quote from: clappingsnowdrop – on
Didn't knew about this one, let me add it to the poll. Learned a new one today. Thanks.
It's the feature that keeps me on openrc. Simple but powerful.

Re: ip address configuration census.

Reply #4 –
If i'm out and about with laptop or android phone, then NetworkManager for the laptop and normal dhcp for the android, but at home on the LAN all the devices have static ip addresses so i don't use anything because the ip is already pre set in the router (machine specific).

Re: ip address configuration census.

Reply #5 –
Quote from: gripped – on
It's the feature that keeps me on openrc. Simple but powerful.

Less bloat too. Like How I choose my programs.

Quote from: Zendjinn – on
If i'm out and about with laptop or android phone, then NetworkManager for the laptop and normal dhcp for the android, but at home on the LAN all the devices have static ip addresses so i don't use anything because the ip is already pre set in the router (machine specific).

I've haven't tried setting it via the router (static). How do you set it for the lan devices, dhcp as well? (like PC = dhcp, but router = set static ip for pc?)

Re: ip address configuration census.

Reply #6 –
Quote from: clappingsnowdrop – on

I've haven't tried setting it via the router (static). How do you set it for the lan devices, dhcp as well? (like PC = dhcp, but router = set static ip for pc?)

I guess it depends on the router, but mine is just a cheap(ish) tp-link Archer thing. Go into the router settings and find the dhcp settings or network section. Look at the machines that are connected and find out which ones are which (sometimes they're named, and sometimes i just check the MAC address) and then just choose a range of local ip address numbers (for example, if you want 10 devices totally, you might use 192.168.1.25 to 192.168.1.35) and then set the ip address (as appropriate) for each machine. Refresh and that's it. The router will automatically assign the associated ip (within that address range that you have specified) every and any time you connect.  Effectively what you're doing is removing dhcp for the chosen device(s) and assigning static ip addresses. Everything else that is configured to use dhcp will do so.

I'll also add that it can be whatever local ip addresses you want. It doesn't have to be in a particular range of address (192.168.1.25-35 for instance) - i only do this to make it easier to manage and remember. You can organise it however you want to.
Also, on the Android devices, i set the MAC addresses to be static for the LAN, so whenever they connect on my home network the ip address is the same because the router will recognise the MAC address of each device?

With the PC's the MAC address remains the same anyway so whenever i reboot or connect, regardless of what OS i'm using, the IP address is always the same. It makes working with things overall a lot easier. Just remember to make a note of what ip addresses are associated with which device and that's about it. This all works the same whether it's ethernet or wifi.

Re: ip address configuration census.

Reply #7 –
the ip commands are really command line tools for manipulating networking.  If you use them for start up, you really need to put them in an init scricpt.  One should learn how to use them.


ADDITIONALLY, wifi access a whole 'nother beast.  you have iw commands that give you limited access, and it is quit clumsy.  At that point, it is useful to have nm tools around (not to be confused with nm that show symbols in binaries)

flatbush:[ruben]:~$ pacman -F nmtui
world/networkmanager 1.48.4-1
    usr/bin/nmtui
extra/networkmanager 1.48.6-1
    usr/bin/nmtui


Quote
I guess it depends on the router, but mine is just a cheap(ish) tp-link Archer thing.

FWIW - one can do their own routing and set up dhcpd.

Re: ip address configuration census.

Reply #8 –
Quote from: mrbrklyn – on

FWIW - one can do their own routing and set up dhcpd.

Thanks, i'm always happy to learn new things so appreciate the info. :) However, as the original question was "ip address configuration census" and the OP was asking how different people set up their respective ip addresses (or at least that's how i read it) i replied accordingly with how i do it.

Re: ip address configuration census.

Reply #9 –
I use good old dhcpcd on a service combined (wpa_supplicant does the low level connection with wifi's ssid before dhcpcd requests the dhcp server for IP). 

Re: ip address configuration census.

Reply #10 –
Quote from: Zendjinn – on
Quote from: clappingsnowdrop – on

I've haven't tried setting it via the router (static). How do you set it for the lan devices, dhcp as well? (like PC = dhcp, but router = set static ip for pc?)

I guess it depends on the router, but mine is just a cheap(ish) tp-link Archer thing. Go into the router settings and find the dhcp settings or network section. Look at the machines that are connected and find out which ones are which (sometimes they're named, and sometimes i just check the MAC address) and then just choose a range of local ip address numbers (for example, if you want 10 devices totally, you might use 192.168.1.25 to 192.168.1.35) and then set the ip address (as appropriate) for each machine. Refresh and that's it. The router will automatically assign the associated ip (within that address range that you have specified) every and any time you connect.  Effectively what you're doing is removing dhcp for the chosen device(s) and assigning static ip addresses. Everything else that is configured to use dhcp will do so.

I'll also add that it can be whatever local ip addresses you want. It doesn't have to be in a particular range of address (192.168.1.25-35 for instance) - i only do this to make it easier to manage and remember. You can organise it however you want to.
Also, on the Android devices, i set the MAC addresses to be static for the LAN, so whenever they connect on my home network the ip address is the same because the router will recognise the MAC address of each device?

With the PC's the MAC address remains the same anyway so whenever i reboot or connect, regardless of what OS i'm using, the IP address is always the same. It makes working with things overall a lot easier. Just remember to make a note of what ip addresses are associated with which device and that's about it. This all works the same whether it's ethernet or wifi.

I see, was a bit confused there. But basically router is set as the dhcp server. Simple and gets the job done.






Quote from: mrbrklyn – on
the ip commands are really command line tools for manipulating networking.  If you use them for start up, you really need to put them in an init scricpt.  One should learn how to use them.
Yep, it's what I've currently setup. The commands itself are simple, but one needs some bare minimum networking knowledge.


Quote from: mrbrklyn – on
ADDITIONALLY, wifi access a whole 'nother beast.  you have iw commands that give you limited access, and it is quit clumsy.  At that point, it is useful to have nm tools around (not to be confused with nm that show symbols in binaries)
I want to experiment on(iw/iwd) this once I get a wireless nic. Am always curious to learn on doing things the "less bloat/suckless" way.

Quote from: mrbrklyn – on
FWIW - one can do their own routing and set up dhcpd.
What do you mean by routing, like setting up a dhcp server? (I'm confused since in most SOHO setups there isn't really much any routing to do.)






Quote from: kixik – on
I use good old dhcpcd on a service combined (wpa_supplicant does the low level connection with wifi's ssid before dhcpcd requests the dhcp server for IP). 

So one only needs to login/authenticate and wpa_supplicant and dhcp takes care of everything. Is my assumption correct?

Re: ip address configuration census.

Reply #11 –
Quote from: clappingsnowdrop – on

I see, was a bit confused there. But basically router is set as the dhcp server. Simple and gets the job done.


Is it simple? I guess it is but it's the only way i know of at the moment and so far (years) it's worked really well. I'm happy to find other (perhaps more extensible, adaptable & maybe a lot better) ways of doing the same thing though. :) 

Re: ip address configuration census.

Reply #12 –
Quote from: Zendjinn – on
Quote from: clappingsnowdrop – on

I see, was a bit confused there. But basically router is set as the dhcp server. Simple and gets the job done.


Is it simple? I guess it is but it's the only way i know of at the moment and so far (years) it's worked really well. I'm happy to find other (perhaps more extensible, adaptable & maybe a lot better) ways of doing the same thing though. :) 

As the saying goes: "If it ain't broke, don't fix it."

It can definitely be streamlined. If you want to do more, you will need the mentioned bare minimum. It's what I have in mind if I were to make the manual config guide/tutorial. It's more on some of the basics of networking than the command itself since the commands are simple (at least in the context of basic static IP configuration in your home).

From I learned on our short conversation, it seems that the issue is more on you putting the carriage before the horse (not much info yet so maybe I am wrong). Common thing to do, I did that mistake a lot as well. Especially on my earlier days on Linux trying to master it. Like installing arch and then Gentoo with very little knowledge on basic terminal utilities and no knowledge in shells (i.e. bash). Definitely not the smartest choice I've made. I did succeed, but it took me weeks.  :D
 

Re: ip address configuration census.

Reply #13 –
Quote from: clappingsnowdrop – on
It's more on some of the basics of networking than the command itself since the commands are simple (at least in the context of basic static IP configuration in your home).


Well, it used to be but the new "ip ro" and  "ip add" command are more complex now and then there is the whole issue of IP6.

I agree with you, fundamentally, though.  Part of the problem is that networks are being set up without basic understanding of network mechanics or nomenclature.   It really leaves the end use in the dark about an essential part of their system that they use every day and are completely dependent on. 

I was just talking last night to some NYLXS members about just this issue.  Basic networking is not hard and not rocket science.  Any 4th grader can learn it and should learn it since it is part and parcel of their adult lives.

A home network now can have 10 devices on it, 5 of them dynamic ip's on wireless, and those cheap shit routers people depend on completely suck, especially the ones assigned you from the ISP.

It is really useful to CHOOSE your private IP space and assign your gateway routers, not to mention to secure your internal network... not that anyones "smart phone" connected to your wifi can ever be a threat to your network.

The rudementaries of the ip commands is, IMO, an essential thing to learn.  Everything else is implementation.  And you should definitely take control of your own DHCP services.   You run LINUX - a network aware OS!!!  USE IT!!

Re: ip address configuration census.

Reply #14 –
I read in the Linux Bible once that the most important application in Linux is xterm, followed by xterm and sh...