In T4506#204869, @syncer wrote:@Viacheslav @Cheeze_It this was already added, right?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Oct 30 2024
Oct 30 2024
Oct 19 2024
Oct 19 2024
Initial PR is here, https://github.com/vyos/vyos-1x/pull/4166.
Sep 29 2024
Sep 29 2024
Cheeze_It changed the status of T6750: Adding Segment Routing Traffic Engineering portion of FRR from Open to In progress.
Mar 12 2024
Mar 12 2024
Did this test again, and I got the same result.
Mar 6 2024
Mar 6 2024
@c-po, while I don't wish to put words in the mouths of others, I believe the belief is that the interface should stay oper-down.
Jan 11 2024
Jan 11 2024
Good news for the backport into Sagitta, it works :)
Jan 10 2024
Jan 10 2024
Are we going to just let EVPN be the L2VPN technology of choice and not go down the VPWS/VPLS route for L2VPN? EVPN is the future anyway, so going and adding VPWS/VPLS is kind of doing legacy work.
Cheeze_It renamed T5916: Added segment routing check for index size and SRGB size from Add protocol handler tiebreaker for Segment Routing for IS-IS and OSPF for index base values larger than label base to Added segment routing check for index size and SRGB size .
Put in the PR for this at https://github.com/vyos/vyos-1x/pull/2780
Cheeze_It changed the status of T5916: Added segment routing check for index size and SRGB size from Open to Needs testing.
Dec 10 2023
Dec 10 2023
Dec 3 2023
Dec 3 2023
Added PR for documentation here https://github.com/vyos/vyos-documentation/pull/1169
Oct 8 2023
Oct 8 2023
Sep 14 2023
Sep 14 2023
Added PR here https://github.com/vyos/vyos-1x/pull/2263
Aug 31 2023
Aug 31 2023
Jul 4 2023
Jul 4 2023
Jul 3 2023
Jul 3 2023
Under normal operations the VyOS box looks like this for OSPF:
Jun 30 2023
Jun 30 2023
I was able to test this for ISIS. I'll test OSPF hopefully tomorrow.
Apr 24 2023
Apr 24 2023
Cheeze_It changed the status of T5081: ISIS and OSPF syncronization with IGP-LDP sync from Open to Needs testing.
Apr 12 2023
Apr 12 2023
Mar 22 2023
Mar 22 2023
Added initial implementation here:
Mar 11 2023
Mar 11 2023
Nov 27 2022
Nov 27 2022
Cheeze_It changed the status of T4739: ISIS and OSPF segment routing being refactored from Unknown Status to Resolved.
OSPF and ISIS segment routing should now have been successfully refactored...at least for now.
Cheeze_It committed rVYOSONEXa835da15e0f2: ospf: T4739: Adding missing OSPF FRR template (authored by Cheeze-It <16260577+Cheeze-It@users.noreply.github.com>).
Nov 26 2022
Nov 26 2022
Adding PR to fix OSPF opaque LSA and rfc 1583 compatibility to the OSPF FRR Jinja2 template.
Nov 15 2022
Nov 15 2022
We figured out the problem. So for OSPF segment routing to work we need to enable opaque LSA capabilities. So by default VyOS doesn't have opaque LSAs (type 9, type 10, type 11) enabled. So after checking the configuration for the OSPF FRR template I noticed that the actual command to enable opaque LSAs is broken because it's not in the OSPF FRR template. Once we fix that, we'll have working OSPF segment routing.
Nov 8 2022
Nov 8 2022
One miracle at a time :)
Oct 17 2022
Oct 17 2022
I am finding out, it seems OSPF SR doesn't work properly :(
Oct 16 2022
Oct 16 2022
Here is ISIS segment routing working:
Oct 15 2022
Oct 15 2022
Cheeze_It changed the status of T4739: ISIS and OSPF segment routing being refactored from In progress to Needs testing.
Oct 14 2022
Oct 14 2022
Put in hopefully the last PR for this here, https://github.com/vyos/vyos-1x/pull/1595
Cheeze_It renamed T4739: ISIS and OSPF segment routing being refactored from ISIS segment routing being refactored to ISIS and OSPF segment routing being refactored.
Oct 11 2022
Oct 11 2022
Oct 8 2022
Oct 8 2022
Added PR for this here, https://github.com/vyos/vyos-1x/pull/1574
Cheeze_It changed the status of T4739: ISIS and OSPF segment routing being refactored from Open to In progress.
I closed the other PR, and put in https://github.com/vyos/vyos-1x/pull/1572.
Oct 7 2022
Oct 7 2022
Sep 21 2022
Sep 21 2022
Initial PR here, https://github.com/vyos/vyos-1x/pull/1551.
Sep 20 2022
Sep 20 2022
It seems we have working ISIS segment routing:
Sep 18 2022
Sep 18 2022
Sep 16 2022
Sep 16 2022
Added a new pull request to make ISIS segment routing work again.
Sep 15 2022
Sep 15 2022
It seems that we have two constraints here.
Made a fix and now we have:
Let me see if I can fix it.
Doing further testing, it seems adding the explicit-null broke the configuration:
Good news. It seems the patch worked properly. Here we show MPLS labels generated via segment routing for the prefix command:
Sep 14 2022
Sep 14 2022
Added a pull request for this fix.
Sep 13 2022
Sep 13 2022
Aug 4 2022
Aug 4 2022
Jul 21 2022
Jul 21 2022
Put in pull request https://github.com/vyos/vyos-1x/pull/1423
Jul 4 2022
Jul 4 2022
I wanted to ask you guys if this is an appropriate change to make. Considering it's on BGP, it's going to be a change in a crucial part but I think this one is probably a good one to make just to reduce ambiguity.
May 16 2022
May 16 2022
@c-po, lets run with "system-as"
Feb 22 2022
Feb 22 2022
@Viacheslav, hmmm, yeah that's a good point. I'll see what I can do to add the OP configs. I know I added the conf configs.
Feb 17 2022
Feb 17 2022
Dec 7 2021
Dec 7 2021
Cheeze_It added a comment to T4024: Access-lists and prefix-lists disappear when setting ldp hello-ipv4-interval.
Now that's......different.
Aug 8 2021
Aug 8 2021
Aug 7 2021
Aug 7 2021
Cheeze_It added a comment to T3634: Add op command option for ping for do not fragment bit to be set.
Did more checks.....and noticed it *IS* properly sending the ping command:
Aug 5 2021
Aug 5 2021
Cheeze_It added a comment to T3634: Add op command option for ping for do not fragment bit to be set.
Made the change to "do" and I noticed that.....DF is used even if there is no DF bit explicitly set...:
Cheeze_It added a comment to T3634: Add op command option for ping for do not fragment bit to be set.
It seems the man page that I looked at I either didn't read carefully enough, or I completely messed it up. You're right @Viacheslav.
Cheeze_It added a comment to T3634: Add op command option for ping for do not fragment bit to be set.
Did a quick test...
Cheeze_It added a comment to T3634: Add op command option for ping for do not fragment bit to be set.
Hmmmm....it worked last time. I'll give it another run.
Aug 1 2021
Aug 1 2021
Jul 25 2021
Jul 25 2021
Put in a PR for this....
Jul 19 2021
Jul 19 2021
@Scoopta, thank you. That's good. I *think* know how the logic should go. Shouldn't be difficult but I'll consult with @Viacheslav and @c-po on how we should tackle it. It shouldn't be hard, but I want to make sure I properly do it :)
@Viacheslav, @c-po, the ISIS FRR Jinja2 template is significantly different between 1.3 and 1.4. Should I try to make the change on 1.3 and then merge? Or should I make it on 1.4 and we'll find a way to merge it back into 1.3?
@Viacheslav, @Scoopta, I take it for default originate on IPv6 there's a requirement to have "ipv6 router isis" added on the interface? I'm thinking yes. If it's a yes (which I'm thinking it is) then I believe this should be fairly easy to add. I'll give it a check guys.
Jun 17 2021
Jun 17 2021
Cheeze_It added a comment to T3634: Add op command option for ping for do not fragment bit to be set.
Added PR:
Cheeze_It edited a custom field on T3634: Add op command option for ping for do not fragment bit to be set.
May 22 2021
May 22 2021
@fernando, this was something I was looking into adding but it'll be in 1.4 One day.....I hope soonish....maybe in a few months.
Apr 30 2021
Apr 30 2021
Will be adding the BGP op commands for it as well eventually...
Mar 25 2021
Mar 25 2021
I put in a PR for this:
Mar 17 2021
Mar 17 2021
FRR coder Donald Sharp kicked ass and fixed it here...
Mar 14 2021
Mar 14 2021
I have successfully added a *ton* of address families in my build. I will PR it, but we also have found an error. The error that we have found is an FRR error at this link here.
Mar 5 2021
Mar 5 2021
@c-po, using a value of "0" for use inbound packet would actually be the best behavior if we can specify/use that.
I know my opinion is....really not that important but I would *highly* recommend going to maximum TTL of 255 or at minimum 127. TTL is a very hard thing to troubleshoot most of the time and therefore it's almost never worth going lower than maximum for IP TTL.
Feb 26 2021
Feb 26 2021
Put in a PR for this, https://github.com/vyos/vyos-1x/pull/744