You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
The following figure shows the communication topology. The initial configuration is as follows: Services are enabled on each node: IPforword and quagga routing protocols, such as zebra and ospfv3;
And open in the terminal of each node: sysctl -w net.ipv4.conf.all.forwarding=1 sysctl -w net.ipv4.conf.default.forwarding=1 sysctl -w net.ipv6.conf.all.forwarding=1 sysctl -w net. Ipv6. Conf. Default.forwarding = 1.
Because I wanted to test the functionality of the SRv6 protocol, I removed the ipv4 address of the relay node.
After the simulation is started, I find that if I do not configure a static route, the ping -6 X.X.X command cannot be used to ping the nodes through X.X.X.
When I check the ipv6 routing table of the node (route -6 -n), I find that each node only has the routing information of its own network segment, but does not learn the routing information of neighboring network segments.
This means that I have to manually configure every route, which seems silly because as the node size increases, the effort is impossible. So I wonder if core does not support the related protocol stack of ipv6? To Reproduce
Steps to reproduce the behavior:
Select the routing node and configure the services and ip,
Open simulation,
Node communication failure,
The static routing table can be manually configured(vtysh) for communication。
Expected behavior
Communication is possible without manually configuring the static routing table!
Screenshots
Desktop (please complete the following information):
OS: [e.g. Ubuntu 20.04]
CORE Version [e.g. 9.0.1] core-gui-legacycore-guiAlso can not run normally
EMANE Version [e.g. 1.2.4]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
The routing nodes just use example configurations and are not meant to be end all solutions for every use case, nor the end all be all for routing software.
You can change the configuration of the routing software or use something else if desired. CORE itself does not facilitate routing.
Describe the bug
A clear and concise description of what the bug is.
The following figure shows the communication topology. The initial configuration is as follows:
Services
are enabled on each node:IPforword
and quagga routing protocols, such aszebra
andospfv3
;And open in the terminal of each node:
sysctl -w net.ipv4.conf.all.forwarding=1
sysctl -w net.ipv4.conf.default.forwarding=1
sysctl -w net.ipv6.conf.all.forwarding=1
sysctl -w net. Ipv6. Conf. Default.forwarding = 1
.Because I wanted to test the functionality of the SRv6 protocol, I removed the ipv4 address of the relay node.
After the simulation is started, I find that if I do not configure a static route, the
ping -6 X.X.X
command cannot be used to ping the nodes through X.X.X.When I check the ipv6 routing table of the node (
route -6 -n
), I find that each node only has the routing information of its own network segment, but does not learn the routing information of neighboring network segments.This means that I have to manually configure every route, which seems silly because as the node size increases, the effort is impossible. So I wonder if core does not support the related protocol stack of ipv6?
To Reproduce
Steps to reproduce the behavior:
services
andip
,vtysh
) for communication。Expected behavior
Communication is possible without manually configuring the static routing table!
Screenshots
Desktop (please complete the following information):
core-gui-legacy
core-gui
Also can not run normallyAdditional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: