Antonio Ojea 924553b7ee iptables don't do reverse DNS lookups ...

the iptables monitor was using iptables -L to list the chains,
without the -n option, so it was trying to do reverse DNS lookups.
A side effect is that it was holding the lock, so other components
could not use it.
We can use -S instead of -L -n to avoid this, since we only want
to check the chain exists.

2020-07-08 18:39:22 +02:00

..

testing

Cleanup: Change "Ip" to "IP" in func and var names

2020-04-10 15:29:50 -07:00

BUILD

Run hack/update-vendor.sh

2020-05-16 07:54:33 -04:00

doc.go

Use Go canonical import paths

2016-07-16 13:48:21 -04:00

iptables_linux.go

expose lock release error from iptables util

2017-07-05 14:31:24 -07:00

iptables_test.go

Cleanup: Change "Ip" to "IP" in func and var names

2020-04-10 15:29:50 -07:00

iptables_unsupported.go

util/iptables: fix cross-build failures due to syscall.Flock()

2017-05-14 23:37:52 -05:00

iptables.go

iptables don't do reverse DNS lookups

2020-07-08 18:39:22 +02:00

monitor_test.go

Cleanup: Change "Ip" to "IP" in func and var names

2020-04-10 15:29:50 -07:00

OWNERS

eparis to emeritus

2020-06-30 09:50:44 -07:00

save_restore_test.go

Optimize iptables

2018-07-06 14:25:56 +02:00

save_restore.go

Better error message if panic occurs during iptables-save output parsing

2019-05-28 11:38:27 +02:00