-
Additional loopback are currently not advertized with ripv2 and ripng.
-
**Describe the bug**
When running ripng with multiple paths to the same address a failure of one upstream router which does not result in a local interface going down causes refreshes of the route ev…
-
```
Feature request
What steps will reproduce the problem?
1. We often use IPv4-only XORP custom builds with IPv6 portions stripped out.
Remnants of IPv6 are left in some CORE and config.boot files …
-
```
Feature request
What steps will reproduce the problem?
1. We often use IPv4-only XORP custom builds with IPv6 portions stripped out.
Remnants of IPv6 are left in some CORE and config.boot files …
-
```
Feature request
What steps will reproduce the problem?
1. We often use IPv4-only XORP custom builds with IPv6 portions stripped out.
Remnants of IPv6 are left in some CORE and config.boot files …
-
- FRR VERSION 8.4, 8.5, 9 from debian as well as
- Linux (pve container in debian bullseye and bookworm)
- KERNEL VERSION: 5.15
Hi guys,
Got a very easy testcase that just doesn't seem to wor…
ardje updated
8 months ago
-
```
Feature request
What steps will reproduce the problem?
1. We often use IPv4-only XORP custom builds with IPv6 portions stripped out.
Remnants of IPv6 are left in some CORE and config.boot files …
-
```
Feature request
What steps will reproduce the problem?
1. We often use IPv4-only XORP custom builds with IPv6 portions stripped out.
Remnants of IPv6 are left in some CORE and config.boot files …
-
```
Feature request
What steps will reproduce the problem?
1. We often use IPv4-only XORP custom builds with IPv6 portions stripped out.
Remnants of IPv6 are left in some CORE and config.boot files …
-
```
Feature request
What steps will reproduce the problem?
1. We often use IPv4-only XORP custom builds with IPv6 portions stripped out.
Remnants of IPv6 are left in some CORE and config.boot files …