Rewrite vyatta-conntrack in new XML and Python flavour
Description
Description
Details
Details
- Version
- -
- Is it a breaking change?
- Perfectly compatible
- Issue type
- Unspecified (please specify)
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| In progress | FEATURE REQUEST | None | T3355 Remove all remaining legacy Vyatta code | ||
| Resolved | FEATURE REQUEST | c-po | T3535 Rewrite vyatta-conntrack-sync in new XML and Python flavor | ||
| Resolved | FEATURE REQUEST | c-po | T3579 Rewrite vyatta-conntrack in new XML and Python flavour |
Event Timeline
Comment Actions
Will the custom timeout feature also be implemented in the python code? This is an option in the perl flavour (but doesn't actually work in 1.3 RC4).
vyos@r1.tvi.lan# set system conntrack timeout Possible completions: > custom Define custom timeouts per connection icmp ICMP timeout in seconds other Generic connection timeout in seconds > tcp TCP connection timeout options > udp UDP timeout [edit]
Comment Actions
Yes, also this part will be migrated in the next couple of weeks as we plan to get rid of all legacy code in the 1.4 release cycle.
Can you please show us what does not work in VyOS 1.3? And probably how it should work in your opinion?
Comment Actions
I tried to create a custom timeout rule for tcp port 80. First I assumed that everything was fine since the first commit succeeded without error messages. But when I wanted to alter the rule, it failed. Below you see an example where I first create a rule, and then try to delete it. Afterwards any commits regarding custom timeouts fails.
vyos@vyos-router:~$ conf [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 destination address 'a.b.3.74' [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 destination port '80' [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 protocol tcp established '300' [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 source address 'c.d.236.168' [edit] vyos@vyos-router# [edit] vyos@vyos-router# commit [edit] vyos@vyos-router# del system conntrack timeout custom rule 10 [edit] vyos@vyos-router# commit [ system conntrack timeout custom ] iptables: Bad rule (does a matching rule exist in that chain?). Conntrack timeout error: failed to run iptables -D VYATTA_CT_TIMEOUT -t raw -m comment --comment "timeout-10" -p tcp --source c.d.236.168 --destination a.b.3.74 --dport 80 -j RETURN iptables: Bad rule (does a matching rule exist in that chain?). Conntrack timeout error: failed to run iptables -D VYATTA_CT_TIMEOUT -t raw -m comment --comment "timeout-10" -p tcp --source c.d.236.168 --destination a.b.3.74 --dport 80 -j CT --timeout policy_timeout_10 nfct v1.4.6: netlink error: Device or resource busy Conntrack timeout error: failed to run sudo /usr/sbin/nfct timeout delete policy_timeout_10 [edit] vyos@vyos-router# discard No changes have been discarded [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 destination address 'a.b.3.74' [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 destination port '80' [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 protocol tcp established '300' [edit] vyos@vyos-router# set system conntrack timeout custom rule 10 source address 'c.d.236.168' [edit] vyos@vyos-router# [edit] vyos@vyos-router# commit [ system conntrack timeout custom ] nfct v1.4.6: netlink error: Device or resource busy Conntrack timeout error: failed to run sudo /usr/sbin/nfct timeout add policy_timeout_10 inet tcp established 300 [[system conntrack]] failed Commit failed [edit] vyos@vyos-router# discard Changes have been discarded [edit] vyos@vyos-router# exit exit vyos@vyos-router:~$ sh version Version: VyOS 1.3.0-rc4 Release Train: equuleus
Comment Actions
I believe I have found out why modification/deletion of rules fails. This is the rule definition in iptables:
sudo iptables -S -t raw| grep -i timeout ... -A VYATTA_CT_TIMEOUT -s a.b.236.168/32 -d c.d.3.74/32 -p tcp -m tcp --dport 80 -m comment --comment timeout-10 -j CT --timeout poli -A VYATTA_CT_TIMEOUT -s a.b.236.168/32 -d c.d.3.74/32 -p tcp -m tcp --dport 80 -m comment --comment timeout-10 -j RETURN ...
And this is the commands the perl script uses to delete the rules:
-D VYATTA_CT_TIMEOUT -t raw -m comment --comment "timeout-10" -p tcp --source a.b.236.168 --destination c.d.3.74 --dport 80 -j RETURN -D VYATTA_CT_TIMEOUT -t raw -m comment --comment "timeout-10" -p tcp --source a.b.236.168 --destination c.d.3.74 --dport 80 -j CT --timeout policy_timeout_10
They don't match, which results in that the rules aren't deleted from the running iptables config, and thus we are unable to delete the policy with nfct timeout delete policy_timeout_10. I'm able to manually delete the rules using
sudo iptables -D VYATTA_CT_TIMEOUT -t raw -s a.b.236.168/32 -d c.d.3.74/32 -p tcp -m tcp --dport 80 -m comment --comment timeout-10 -j CT --timeout poli sudo iptables -D VYATTA_CT_TIMEOUT -t raw -s a.b.236.168/32 -d c.d.3.74/32 -p tcp -m tcp --dport 80 -m comment --comment timeout-10 -j RETURN sudo nfct timeout delete policy_timeout_10
Comment Actions
In the crux.
set system conntrack timeout custom rule 10 destination address '203.0.113.74' set system conntrack timeout custom rule 10 destination port '80' set system conntrack timeout custom rule 10 protocol tcp established '300' set system conntrack timeout custom rule 10 source address '192.0.2.168'
commit
vyos@r2-lts# commit [ system conntrack hash-size 32768 ] Updated conntrack hash size. This change will take affect when the system is rebooted. [ system conntrack timeout custom ] iptables: No chain/target/match by that name. nfct v1.4.2: error: Device or resource busy iptables: No chain/target/match by that name. Conntrack timeout error: failed to run iptables -I VYATTA_CT_TIMEOUT 2 -t raw -m comment --comment "timeout-10" -p tcp --source 192.0.2.168 --destination 203.0.113.74 --dport 80 -j RETURN [[system conntrack]] failed Commit failed [edit]
Comment Actions
@Viacheslav / @vindenesen that is a bug I have also seen in the old iptables based implementation. Can you please file a bug report towards VyOS 1.2 and 1.3?