Displaying 2 results from an estimated 2 matches for "lxdbr0".
2017 Aug 07
3
[Bug 1166] New: negated rule and rule with mistyped interface name looks identical in non-verbose iptables output
...I was adding rule for masquerading packets from VM bridge, and I wanted to add
rule that applies masquerade for packages leaving laptop with VMs on all
interfaces excluding one (vm bridge) because why not.
And I made little typo
Instead of
iptables -t nat -A POSTROUTING -s 10.118.196.0/24 \! -o lxdbr0 -j MASQUERADE
I typed:
iptables -vv -t nat -A POSTROUTING -s 10.118.196.0/24 -o \! lxdbr0 -j
MASQUERADE
I noticed that rule wasn't matching so after a while I noticed what was the
problem.
But funny thing is:
both rules when displaying them with `iptables -t nat -nvL` are shown as
follows:...
2024 Jul 13
2
[Bug 1758] New: Design flaw in chain traversal
...ble
}
}
which, at a first glance, worked like expected. But then I noticed that the
virtual guest machine in LXD virtualization cannot resolve DNS queries anymore.
The reason: LXD itself installs a ruleset like (again, just an excerpt to show
the problem)
table inet lxd {
chain in.lxdbr0 {
type filter hook input priority filter; policy accept;
iifname "lxdbr0" tcp dport 53 accept
iifname "lxdbr0" udp dport 53 accept
iifname "lxdbr0" icmp type { destination-unreachable,
time-exceeded, param...