Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post 8 months ago by Monica Cellio‭.

51 / 255
  • There are a couple of ways of handling this (on PC's in general. I do use Linux, but not Arch, and this will work)
  • The first way is to statically assign an IP address. While you SHOULD be able to assign a static IP address in the DHCP range, it is better to assign it outside the range (the range is configured in the DHCP server - in this case your OpenWRT router). To statically assign an IP address you need to specify the IP address, the Netmask, the Gateway and the nameservers.
  • Here is a link on how to do this in Archhttps://ostechnix.com/configure-static-dynamic-ip-address-arch-linux/
  • I would argue the better way is to dynamically assign a static IP address. This is not strictly speaking what you asked, but is very relevant. The idea here is to map the MAC address of the Arch Linux LAN Interface to an IP, and have the DHCP server assign it dynamically. The nice thing here is you don't need to make any changes to your Arch Box, and if you shift to another network nothing needs to change to get connectivity.
  • https://openwrt.org/docs/guide-user/base-system/dhcp_configuration outlines how to do this on OpenWRT.
  • You can find your Arch Boxes IP address with a command like
  • sudo ip addr show
  • The MAC address is the bit after the words link/ether for the appropriate device.
  • There are a couple of ways of handling this (on PC's in general. I do use Linux, but not Arch, and this will work).
  • The first way is to statically assign an IP address. While you SHOULD be able to assign a static IP address in the DHCP range, it is better to assign it outside the range (the range is configured in the DHCP server - in this case your OpenWRT router). To statically assign an IP address, you need to specify the IP address, the Netmask, the Gateway, and the nameservers.
  • Here is a link on how to do this in Arch: https://ostechnix.com/configure-static-dynamic-ip-address-arch-linux/
  • I would argue the better way is to dynamically assign a static IP address. This is not strictly speaking what you asked, but is very relevant. The idea here is to map the MAC address of the Arch Linux LAN Interface to an IP, and have the DHCP server assign it dynamically. The nice thing here is you don't need to make any changes to your Arch box, and if you shift to another network, nothing needs to change to get connectivity.
  • https://openwrt.org/docs/guide-user/base-system/dhcp_configuration outlines how to do this on OpenWRT.
  • You can find your Arch box's IP address with a command like
  • ip addr show
  • The MAC address is the bit after the words link/ether for the appropriate device. You will need this information to tell OpenWRT's DHCP server how to identify this box (or, strictly speaking, this particular network interface).

Suggested 8 months ago by tripleee‭