Skip to content

Conversation

@sspencerwire
Copy link
Contributor

@sspencerwire sspencerwire commented Sep 19, 2022

Author checklist (Completed by original Author)

  • Contribution a good fit for the Rocky project? Title and Author MetaTags inserted ?
  • Is this a non-English contribution?
  • If applicable, steps and instructions have been tested to work on a real system
  • Did you perform an initial self-review to fix basic typos and grammatical correctness

Rocky Documentation checklist (Completed by Rocky team)

  • 1st Pass (Check that document is good fit for project and author checklist completed)
  • 2nd Pass (Technical Review - check for technical correctness)
  • 3rd Pass (Basic Editorial Review)
  • 4th Pass (Detailed Editorial Review and Peer Review)
  • Final pass/approval (Final Review)

* This document is a copy of the current network configuration. I'm
editing sections and replacing them with the correct information for
9.0.
* The lab for this is using a Virtual Box installed version of Rocky
Linux 9.0, as it will more closely emulate a real machine.
* NOTE: I know there is a bunch of content here that still needs to be
changed.
* forgot to save current changes
@sspencerwire sspencerwire changed the title Network configuration WIP: Network configuration 9.0 Sep 19, 2022

The static IP configuration scheme is very popular on server class systems or networks.

The dynamic IP approach is popular on home and office networks - or workstation and desktop class systems. The dynamic scheme usually needs _something_ extra that is locally available that can supply proper IP configuration information to requesting workstations and desktops. This _something_ is called the Dynamic Host Configuration Protocol (DHCP).

This comment was marked as resolved.


The dynamic IP approach is popular on home and office networks - or workstation and desktop class systems. The dynamic scheme usually needs _something_ extra that is locally available that can supply proper IP configuration information to requesting workstations and desktops. This _something_ is called the Dynamic Host Configuration Protocol (DHCP).

Very often, home/office users don't have to worry or know about DHCP. This is because the somebody or something else is automagically taking care of that in the background. The only thing that the end user needs to do is to physically or wirelessly connect to the right network (and of course make sure that their systems are powered on)!
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Very often, home/office users don't have to worry or know about DHCP. This is because the somebody or something else is automagically taking care of that in the background. The only thing that the end user needs to do is to physically or wirelessly connect to the right network (and of course make sure that their systems are powered on)!
Very often, home/office users don't have to worry or know about DHCP. This is because somebody or something else is automagically taking care of that in the background. The only thing that the end user needs to do is to physically or wirelessly connect to the right network (and of course make sure that their systems are powered on)!

* ran out of time for now, added most of the nmtui section
* still need the nmcli section on how this is done
@sspencerwire
Copy link
Contributor Author

@SergeCroise Most of the content you are highlighting is from the older document here: https://docs.rockylinux.org/guides/network/basic_network_configuration/, which was copied to start working on this document for Rocky Linux version 9.0. It needs a bunch of changes, and I've not gotten through most of your commented sections as yet. I very much do appreciate you taking a look at this, however, and welcome your feedback once I've completed changing the instructions so that they work for 9.0. If you'd like to help with that effort, I'm totally fine with that too!

sspencerwire and others added 2 commits September 20, 2022 08:33
Good catch!

Co-authored-by: Serge Croisé <SergeCroise@users.noreply.github.com>
* completed sections
* checked spelling and structure
* tweaked `ip` section to remove `ifcfg` as this is no-longer relavent
for 9
* checked formatting for images and admonitions - OK
@sspencerwire
Copy link
Contributor Author

@all-contributors please add @SergeCroise for content

@allcontributors
Copy link
Contributor

@sspencerwire

I've put up a pull request to add @SergeCroise! 🎉

@sspencerwire
Copy link
Contributor Author

@SergeCroise I've completed my changes for version 9. Would you like to take a look at this document now? Please feel free to suggest any changes or make corrections.

I'd like you to review the original document, which will be renamed to "Network Configuration - Rocky Linux 8.6" and push any changes to that document that you would like to fix. Some of your earlier comments to this document before it was completed would apply to that document. You can find that here.

Thank you very much!

@sspencerwire sspencerwire closed this by deleting the head repository Sep 20, 2022
@SergeCroise
Copy link
Contributor

ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants