Skip to content

Conversation

@kkelley1
Copy link
Contributor

@kkelley1 kkelley1 commented Jun 9, 2025

  • Give your PR a recognizable title. For example: "FE-123: Add new prop to component" or "Resolve Issue Create new-pricing-increases-costs #123: Fix bug in component"
  • Your PR title will be visible in changelogs

What Changed

  • What changes does this PR propose?
  • Provide screenshots or screen recordings for any visual changes.

How To Test or Verify

  • Describe any steps that may help reviewers verify changes.
  • Anything beyond basic unit testing, such as assistive tech usage, or special interactions.

PR Checklist

Below are some checklists to follow for the correct procedure in different circumstance. The first list ("All PRs Checklist") should be followed for ALL PRs. The next 2 are additive to this list depending on what type of PR you are using.

For example: If you are submitting a content change to one of the support documents, your checklist would include the:

  • "All PRs Checklist"
  • AND the "Content Changes Checklist

If you are submitting a feature addition, enhancement, or bug fix, your checklist would include the:

  • "All PRs Checklist"
  • AND the "Development Changes Checklist"

All PRs Checklist

  • Give your pull request a meaningful name.
  • Use lowercase filenames.
  • Apply at least one team label according to which team is the content expert (ie. team-FE or team-SAZ)
  • Pull request approval from the FE team or content experts (see label applied above) that isn't the content creator.

Content Changes Checklist

  • Check that your article looks correct in the preview here or in a Netlify deploy preview.
  • Check the links in your article.
  • Check the images in your article (if there are any)
  • Check to make sure you are using markdown appropriately as outlined in examples/article.md in the root of the project directory and on the momentum doc's preface article
  • Check to make sure the Copy and Tone Guidelines are followed.

Development Changes Checklist (some checks are automatic github actions and will not be listed here. ie. "all tests pass")

  • The appropriate tests are created in cypress/ directory in the root of the project
  • The lighthouse score is passing according to the FE Support Docs' Service Outline SLI/SLOs

@netlify
Copy link

netlify bot commented Jun 9, 2025

Deploy Preview for support-docs failed.

Name Link
🔨 Latest commit ed049a7
🔍 Latest deploy log https://app.netlify.com/projects/support-docs/deploys/68472ff3cfe77000089c4c05

---

* [Momentum 5.0 Changelogs](/momentum/changelog/5/5-0)
* [Momentum 5.1 Changelogs](/momentum/changelog/5/5-1)
Copy link
Contributor

Choose a reason for hiding this comment

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

could you please point me to where 5-1 changelog is?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just added it.

# Configure the RADIUS client
auth_radius {
NAS-IP-Address = 10.0.0.1 # the IP address of this SMTP server
NAS-IP-Address = fd01:345::1 # the IP address of this SMTP server
Copy link
Contributor

Choose a reason for hiding this comment

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

Did we test with IPv6 address? If not, we shall keep the example in IPv4.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was asked to add IPv6 examples.

server "two" {
host = "radius-2.example.com"
server "ipv6wport" {
host = "[2001:fd3::1]:2812"
Copy link
Contributor

Choose a reason for hiding this comment

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

We can keep the example in IPv4.

<dd>

The hostname or IP address of the RADIUS server. If a colon is present in the string then the left side of the string will be used as the hostname/IP address and the right hand side will be used as the port number on the server. If left unspecified, the RADIUS standard port number of 1812 will be used.
The hostname or IP address of the RADIUS server. The hostname/IP address can be followed by a colon and the port number on the server. If left unspecified, the RADIUS standard port number of 1812 will be used. An IPv6 address must be enclosed in brackets if a port was added.
Copy link
Contributor

Choose a reason for hiding this comment

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

We can mention that since 5.1, IPv6 address can be used but must be enclosed in bracket if a port is specified.

@dkoerichbird dkoerichbird changed the base branch from main to TASK-10736 July 10, 2025 18:15
@dkoerichbird dkoerichbird merged commit 0eece23 into TASK-10736 Jul 10, 2025
2 of 8 checks passed
@dkoerichbird dkoerichbird deleted the TASK-6411-ipv6-improvements branch July 10, 2025 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants