Hi all,I am having some success and some difficulty with iproute2.We have a few separate entities all going via a single CentOS 6.4 box that manages the routing across a few inter... [by Wernervdmerwe]
I didnt find any reference for this basic question
Im porting a router application to linux and I will use iproute2 to configure the kernel with router-interfaces/addressee/nbrs etc.
Ive installed iproute2 pkg. and I want to reuse it as much as possible
What are the APIs of the iproute2 that my application can use? for example for 'ip route' commands , is the API is 'do_iproute' ?
We are about to start SW Design Reviews related to moving from VxWorks to Linux. During our researches we found out that most powerful and supported "tool" for Networking in LINUX is iproute2 where in most cases underlaying layer is NETLINK sockets. From most searches I could discover that iproute2 has no direct APIs. It should be called from various exec..().
I have a Raspberry Pi (running Raspbian) with three network interfaces (one ethernet and two USB wifi nics). What I want to achieve is this: I have two WAN connections to the internet (DSL + Cable), and I want to set up the RasPi in such a way that it offers two default gateways.
Is there any way to use a wildcard or other matching criteria when using iproute2? I have multiple tunnel interfaces that follow a naming convention. Something like ip tunnel del blah-* (which gives the error: ioctl: No such device) would be great without having to resort to creating custom scripts.
This question may seem trivial, but I'm sure I'm not alone. I am trying to a good citizen and replace my usage of ifconfig with ip (iproute2). However, for quick diagnostic checks, I am finding myself revert to ifconfig as its output seems much easier to quickly read than ip.
You maybe should post a Bug report on the Arch linux Kernel.If Arch is going to push people to use iproute2 they need to ship a kernel with at least these modules.https://lwn.net/Articles/492108/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 121 ++++++++--- drivers/net/macvlan.c | 61 +++++-