| To: | Ben Greear <greearb@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: Redirect-Device |
| From: | Thomas Graf <tgraf@xxxxxxx> |
| Date: | Fri, 1 Apr 2005 00:46:40 +0200 |
| Cc: | hadi@xxxxxxxxxx, "'netdev@xxxxxxxxxxx'" <netdev@xxxxxxxxxxx> |
| In-reply-to: | <424C7813.4000101@xxxxxxxxxxxxxxx> |
| References: | <424C6089.1080507@xxxxxxxxxxxxxxx> <1112303627.1073.71.camel@xxxxxxxxxxxxxxxx> <424C6B10.6030200@xxxxxxxxxxxxxxx> <1112306031.1073.109.camel@xxxxxxxxxxxxxxxx> <424C7813.4000101@xxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
* Ben Greear <424C7813.4000101@xxxxxxxxxxxxxxx> 2005-03-31 14:22 > My personal opinion is that netlink sockets are a pain in the ass to deal > with, and there is no way I want to try to programatically parse the tc > input or output. libnl will make your life a lot easier, the tc support is not yet finished but I'll be releasing a version this week which at least fully support all the basics (link, neigh, address, routes, rules). It's only a matter of time until one can use the tc interface with only a few library calls. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: RFC: Redirect-Device, David S. Miller |
|---|---|
| Next by Date: | Re: RFC: Redirect-Device, Ben Greear |
| Previous by Thread: | Re: RFC: Redirect-Device, jamal |
| Next by Thread: | Re: RFC: Redirect-Device, Ben Greear |
| Indexes: | [Date] [Thread] [Top] [All Lists] |