Skip to content

Rendering "src" attribute for routes using their devices.#71

Open
ams-tschoening wants to merge 1 commit intofwbuilder:masterfrom
ams-tschoening:ip_route_src_attrib
Open

Rendering "src" attribute for routes using their devices.#71
ams-tschoening wants to merge 1 commit intofwbuilder:masterfrom
ams-tschoening:ip_route_src_attrib

Conversation

@ams-tschoening
Copy link
Copy Markdown
Contributor

@ams-tschoening ams-tschoening commented Oct 29, 2018

This changes the following:

$IP route add 172.[...].0/[...] via 192.[...].16 dev enp0s9:1 \

to:

$IP route add 172.30.0.0/16 via 192.168.101.16 dev enp0s9:1 src 192.168.101.8 \

Consider this a PoC for #70 again.

While the GUI allows devices without an address, rendering scripts for such setups fails with the following error. So it seems unnecessary to check if an address is available or not and render differently.

Qt: Untested Windows version 6.2 detected!
*** Loading data ... done
[email protected]::: error: Missing IP address for interface enp0s9:1
Compile time: 00:00:00

Besides that, it's unclear to me how to handle things like different versions of the Linux kernel, because there are two different directories available:

res\configlets\linux24\routing_functions
res\configlets\linux317\routing_functions

@sarnold
Copy link
Copy Markdown

sarnold commented Oct 14, 2019

I'm pretty sure those 2 versions aren't really a reference to the running kernel, rather, they specify the split between older/newer netfilter stuff (basically which way the rules are written for the kernel interface). I think it's basically the cutoff for whether to use the newer netlink interface (which only exists in 3.1.7+).

@sirius sirius added this to the v6.1 milestone Jan 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants