Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A routing node that uses only ipv6 cannot forward packets properly![BUG] #836

Open
jhonzy0928 opened this issue Nov 27, 2023 · 1 comment
Assignees
Labels

Comments

@jhonzy0928
Copy link

jhonzy0928 commented Nov 27, 2023

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:

  1. Select the routing node and configure the services and ip
  2. Open simulation,
  3. Node communication failure,
  4. The static routing table can be manually configured(vtysh) for communication。

Expected behavior
Communication is possible without manually configuring the static routing table!

Screenshots
1701079527905

Desktop (please complete the following information):

  • OS: [e.g. Ubuntu 20.04]
  • CORE Version [e.g. 9.0.1] core-gui-legacy core-guiAlso can not run normally
  • EMANE Version [e.g. 1.2.4]

Additional context
Add any other context about the problem here.

@jhonzy0928 jhonzy0928 added the bug label Nov 27, 2023
@bharnden
Copy link
Contributor

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.

@bharnden bharnden self-assigned this Nov 27, 2023
@bharnden bharnden added question and removed bug labels Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants