BGP EVPN SDN and 10.255.255.x subnet

mfed

Well-Known Member
Feb 28, 2020
71
25
58
55
I started testing BGP EVPN configuration and noticed that on some nodes (looks like the exit nodes) there is 10.255.255.1 and 10.255.255.2 addresses assigned. I do use 10.255.255.0/24 subnet for one of my vlans. Is it possible to reconfigure SDN to use something else? I can find the addresses in /etc/network/interfaces.d/sdn, but I guess you are not supposed to edit those...
 
I started testing BGP EVPN configuration and noticed that on some nodes (looks like the exit nodes) there is 10.255.255.1 and 10.255.255.2 addresses assigned. I do use 10.255.255.0/24 subnet for one of my vlans. Is it possible to reconfigure SDN to use something else? I can find the addresses in /etc/network/interfaces.d/sdn, but I guess you are not supposed to edit those...
arf damned, It's not configurable currently, I had choose to subnet because it was the very last subnet of 10.0.0.0, and I didn't think that somebody was using it.


Note that's this 10.255.255.0/24 is only used when you enable "exit node local routing" option is enabled.
This is only needed if you want to connect from the exit node main ip to a vm ip address on the same node.

Do you really needed this on your exit node ?


I could look to add an option to change subnet if it's really needed.
 
Note that's this 10.255.255.0/24 is only used when you enable "exit node local routing" option is enabled.
This is only needed if you want to connect from the exit node main ip to a vm ip address on the same node.
I should have read the docs ;)... Without looking at the docs I assumed that 'exit node local routing' means to use the local route tables on the exit nodes to reach the rest of the network, so I thought it should be enabled...

Anyway, hard-coded IP addresses probably not the best thing and sooner or later it might bite somebody. Maybe you can address that in the future version... I think the prompt in the configuration interface to provide a /30 subnet whenever the option 'exit node local routing' is enabled (with the default of '10.255.255.0/30') would be clear enough.
Also, don't you think that a /30 subnet from 169.254.x.x range would be a better default option for this use?
 
I should have read the docs ;)... Without looking at the docs I assumed that 'exit node local routing' means to use the local route tables on the exit nodes to reach the rest of the network, so I thought it should be enabled...

Anyway, hard-coded IP addresses probably not the best thing and sooner or later it might bite somebody. Maybe you can address that in the future version... I think the prompt in the configuration interface to provide a /30 subnet whenever the option 'exit node local routing' is enabled (with the default of '10.255.255.0/30') would be clear enough.
Also, don't you think that a /30 subnet from 169.254.x.x range would be a better default option for this use?
yes, I should really use a /30 ;) This options was added as workaround for a specfic user need, so I think I can change it without breaking things.
I'll try to fix that in the coming weeks.

thanks for the report !