Re: can't set default route for virtual interface

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wednesday 2011-12-28 11:21, Andrew Beverley wrote:
>On Tue, 2011-12-27 at 23:36 -0600, Lloyd Standish wrote:
>> >Have you tried *not* using ifconfig to set up your interfaces? You
>> > should only be using iproute2.
>> 
>> I've seen that mentioned before, and I'm confused.  iproute2 means, for
>>  firewall code, "ip" and "tc" - is that right?
>
>Yes, and "ip" can do everything that all the various net-tools commands
>do.

...and more!

>>   I usually bring up interfaces with "ifup" when I can
>
>Ah, therein lies an interesting situation. ifup is pretty old too, and
>makes calls to the ifconfig command, which is a real pain.

More precisely: ifup is a distribution-specific script, not to be
confused with net-tools/iproute2 (different layer). In that regard,
its age may not mean anything.

ifup also refers to _multiple_ scripts; for example, openSUSE's ifup
uses iproute - since a looong time (therefore it is also old, but at
least it is current).
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux