On 3/9/13 9:47 AM, "Mr Dash Four" <[email protected]> wrote:
>
>> Each address family has its own 'main' table:
>>
>So, you have different "main" tables for ipv4 and ipv6, though they are
>both called "main" and appear under the same name in
>/etc/iproute2/rt_tables, is that right?
/etc/iproute2/rt_tables simply maps names to numbers and vice versa.
That's its sole purpose; it doesn¹t 'define' tables.
You can freely add routes to a table that has no entry in
/etc/iproute2/rt_tables.
>
>If so, when you define a table (say, "dmz"), how does ip know what is it
>for: ipv4 or ipv6? Or is it a case of first-come, first-serve basis? In
>other words, if I define a custom table called "dmz" and then place ipv4
>route in it, I can't then use it for adding ipv6 routes after that and
>vice-versa? Is that how it works?
Both IPv4 and IPv6 can have a table 4. So if your /etc/iproute2/rt_tables
contains:
dmz 4
then it is okay for both families to have routes in 'dmz'.
-Tom
You do not need a parachute to skydive. You only need a parachute to
skydive twice.
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
