extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-27 18:13:13 +01:00
Code Issues Packages Projects Releases Wiki Activity

Avoid double-setting proxy arp flags

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1630 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-09-16 19:30:54 +00:00
parent 93c6ef057a
commit e330130881
3 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall2/changelog.txt
View File

@ -83,3 +83,5 @@ Changes since 2.0.3
39) Relax OpenVPN source port restrictions. 39) Relax OpenVPN source port restrictions.
40) Implement DELAYBLACKLISTLOAD. 40) Implement DELAYBLACKLISTLOAD.
41) Avoid double-setting proxy arp flags.

3
Shorewall2/firewall
View File

@ -1855,7 +1855,8 @@ setup_proxy_arp() {
done < $TMP_DIR/proxyarp done < $TMP_DIR/proxyarp
for interface in $resetlist; do for interface in $resetlist; do
run_and_save_command "echo 0 > /proc/sys/net/ipv4/conf/$interface/proxy_arp" list_search $interface $setlist || \
run_and_save_command "echo 0 > /proc/sys/net/ipv4/conf/$interface/proxy_arp"
done done
for interface in $setlist; do for interface in $setlist; do

5
Shorewall2/releasenotes.txt
View File

@ -61,11 +61,6 @@ Problems corrected since 2.1.8
3) With complex proxy arp configurations involving two or more 3) With complex proxy arp configurations involving two or more
ordered pairs of interfaces, the /proc/sys/net/ipv4/conf/*/proxy_arp ordered pairs of interfaces, the /proc/sys/net/ipv4/conf/*/proxy_arp
flags were sometimes set incorrectly. This has been fixed. flags were sometimes set incorrectly. This has been fixed.
Users looking at their restore file (generated by "shorewall save")
may see that one of these flags might be first reset then set in rapid
succession. This is expected and is harmless since the correct value
(1) results.
----------------------------------------------------------------------- -----------------------------------------------------------------------
Issues when migrating from Shorewall 2.0 to Shorewall 2.1: Issues when migrating from Shorewall 2.0 to Shorewall 2.1: