From bbaaff7218eb1145ba69ae4ca1bd4d72a6269151 Mon Sep 17 00:00:00 2001 From: teastep Date: Mon, 27 Jan 2003 17:03:43 +0000 Subject: [PATCH] Document VLAN naming fix git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@421 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall/changelog.txt | 2 ++ Shorewall/releasenotes.txt | 6 +++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/Shorewall/changelog.txt b/Shorewall/changelog.txt index 89404c8a5..abde5309e 100755 --- a/Shorewall/changelog.txt +++ b/Shorewall/changelog.txt @@ -11,3 +11,5 @@ Changes since 1.3.13 5. Use the routing table to generate list of subnets to be masqueraded when an interface name appears in the SUBNET column of /etc/shorewall/masq. + +6. Restore $dev.$vid naming of VLAN interfaces. diff --git a/Shorewall/releasenotes.txt b/Shorewall/releasenotes.txt index 260066776..43397e6b8 100755 --- a/Shorewall/releasenotes.txt +++ b/Shorewall/releasenotes.txt @@ -20,7 +20,11 @@ New features include: a) In the INTERFACE column of /etc/shorewall/masq b) In the INTERFACE column of /etc/shorewall/nat -3) When an interface name is entered in the SUBNET column of the +3) The ability to name your VLAN interfaces using the $dev.$vid + convention (e.g., "eth0.0") has been restored. This capability was + inadvertently broken in version 1.3.12. + +4) When an interface name is entered in the SUBNET column of the /etc/shorewall/masq file, Shorewall previously masqueraded traffic from only the first subnet defined on that interface. It did not masquerade traffic from: