Skip to content
#

iptables

Here are 446 public repositories matching this topic...

Metaception
Metaception commented Aug 31, 2017

I noticed a conflict in the documentation when attempting to change the default DNS.

The DNS section says:

$IPTABLES -t nat -A OUTPUT -p tcp --dport 53 -j DNAT --to-destination 208.67.222.222:53 || true
$IPTABLES -t nat -A OUTPUT -p udp --dport 53 -j DNAT --to-destination 208.67.222.222:53 || true

While the [Custom

murali-reddy
murali-reddy commented Mar 11, 2020

VM's provisioned on OpenStack have anti-spoofing measures which will drop packets if the source address is not matching to the assigned VM's ip. This prevents pod-to-pod traffic across the nodes getting routed when kube-router is used in direct routing mode.

Following are options to overcome this limitation:

  • configure OpenStack to allo pod-to-pod traffic. Steps are documented for kubespray
antoooks
antoooks commented Sep 3, 2019

After I created the Daemonset on the remote cluster, the kube-iptables-tailer were running but it throws this error

E0903 11:47:30.085747       1 parser.go:31] Error retrieving log time to check expiration: parsing time "Sep" as "2006-01-02T15:04:05.000000-07:00": cannot parse "Sep" as "2006"

Time format expected by kube-iptables-tailer

2019-02-04T10:10:12.345678-07:00 host

Improve this page

Add a description, image, and links to the iptables topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the iptables topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.