How to programatically determine if policy-based routing is compiled into the kernel?
I have a product that is dependent on policy-based (source routing) and would like to be able to scream loudly at install and startup if policy-based routing is not enabled in the kernel.
Is there some way to determine this? Specifically, I'd love a way to find out through the /proc system, but an ioctl or similar call would be OK. I'd even settle for some other tool, like 'ip', if I could just figure out what commands to tell it.
Thanks,
Ben
Signature · 7 lines
Ben Greear ([email protected]) http://www.candelatech.com Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL) http://scry.wanfear.com http://scry.wanfear.com/~greear - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · Ben Greear
I have a product that is dependent on policy-based (source routing) and would like to be able to scream loudly at install and startup if policy-based routing is not enabled in the kernel.
Is there some way to determine this? Specifically, I'd love a way to find out through the /proc system, but an ioctl or similar call would be OK. I'd even settle for some other tool, like 'ip', if I could just figure out what commands to tell it.
Run a command that attempts to use policy-based routing (doing something "benign" like a listing). If it fails then good chance that it isn't compiled in :-)
[ or it may simply mean that the appropriate modules are not loaded, so beware that one :]
That command would need to be /sbin/ip or /sbin/tc or whatever.
If you want to ferrit out what proc looks like with and without routing policy enabled, that would be another way to do it.
Cheers
Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/