search

coreemu / core

Common Open Research Emulator
BSD 2-Clause "Simplified" License
683 stars 165 forks source link

[BUG]wlan default subnet doesn't work #898

Open sei-gseroka opened 4 days ago

sei-gseroka commented 4 days ago

Describe the bug When creating a wlan node in core-gui the subnet is set to 10.0.0.0/32. Connecting two nodes to the same wlan without changing the defaults results in nodes being connected on the GUI but unable to reach other as they are on different subnets. Changing the mask to /24 on the wlan node causes all connections to fail.

Desktop (please complete the following information): OS: Ubuntu 22.04 CORE Version 9.1

bharnden commented 3 days ago

/32 is intentional by default, as it is assumed you would connect a node running routing software. Adjusting the prefix to something else would be one way to adjust around that.

Not sure what you meant by all connections to fail. I do not observe that myself.

sei-gseroka commented 3 days ago

What do you mean connect a node running routing software? It was my understanding that wlan nodes don't do any routing on their own just traffic shaping. In tutorial 2 all the mdr nodes are in a /24 together.

  1. create a wlan node
  2. open the wlan configuration and change the ipv4 mask to /24 and apply
  3. create a container node router
  4. use the link tool between the wlan and container node
  5. no link is actually created
bharnden commented 3 days ago

MDR nodes run routing software by default. They do not, need to be /24. WLAN nodes also determine connectivity as an on/off by pixel distance. So potentially your nodes are too far and out of range, so no connection.

bharnden commented 3 days ago

The nodes being /24 in the example is bad and not what it should be, thanks for pointing it out, the example will need to be adjusted.

sei-gseroka commented 3 days ago

two routers on independent /32s are unable to ping each other.

bharnden commented 3 days ago

Assuming you are using MDR nodes and a WLAN network and they are in range with a connection between them. That would mean you do not have the routing software installed or something with running it is failing. You could inspect within those nodes when running to see if the routing processes are running, etc.

sei-gseroka commented 3 days ago

just plain routers, my instance of CORE doesn't have MDR installed.

bharnden commented 3 days ago

That would likely be related, the example is specifically using MDR nodes for a reason. Plain router nodes also would want to run routing software by default as well, so you would still need something installed. So there is definitely things not aligned in your environment, compared to what is expected.

I will likely update the documentation to make it very clear of what is expected to be installed, in the context of these examples.