It seems UPnP rules doesn't work at all task T4620
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 16 2022
@patrickli Could you send a real example? In your example, port ranges are incorrect also it is not all required UPnP configuration
If you sent all UPnP configuration, it already has been done :)
I'm not a UPnP person, so I ask for some examples.
I tried to add vrf, but it requires some permissions, service is not starting
diff --git a/data/templates/monitoring/override.conf.j2 b/data/templates/monitoring/override.conf.j2 index 9f1b4ebe..63e479af 100644 --- a/data/templates/monitoring/override.conf.j2 +++ b/data/templates/monitoring/override.conf.j2 @@ -1,7 +1,10 @@ +{% set vrf_command = 'ip vrf exec ' ~ vrf ~ ' ' if vrf is vyos_defined else '' %} [Unit] After=vyos-router.service ConditionPathExists=/run/telegraf/vyos-telegraf.conf [Service] +ExecStart= +ExecStart={{ vrf_command }}/usr/bin/telegraf -config /run/telegraf/vyos-telegraf.conf -config-directory /etc/telegraf/telegraf.d $TELEGRAF_OPTS Environment=INFLUX_TOKEN={{ influxdb.authentication.token }} CapabilityBoundingSet=CAP_NET_RAW CAP_NET_ADMIN CAP_SYS_ADMIN AmbientCapabilities=CAP_NET_RAW CAP_NET_ADMIN diff --git a/interface-definitions/service-monitoring-telegraf.xml.in b/interface-definitions/service-monitoring-telegraf.xml.in index 36f40a53..dc014ee1 100644 --- a/interface-definitions/service-monitoring-telegraf.xml.in +++ b/interface-definitions/service-monitoring-telegraf.xml.in @@ -306,6 +306,7 @@ </leafNode> </children> </node> + #include <include/interface/vrf.xml.i> </children> </node> </children>
Aug 15 2022
PR for VyOS 1.3 https://github.com/vyos/vyos-1x/pull/1470
Nice. Is this syntax supported in vyos or it needs some development?
It is possible but with specific syntax
I found some examples:
nft insert rule ip filter VYOS_FW_FORWARD ip 'saddr & 0.255.0.255 != 0.11.0.13' counter
OK. I was trying to migrate from an EdgeRouter and this is a rule I used to have.
set service upnp rule 10 action allow set service upnp rule 10 external-port-range 1024-65536 set service upnp rule 10 internal-port-range 1024-65536 set service upnp rule 10 ip 10.0.0.1/24
@patrickli nftables is not engine for iptables. It is programs to work with netfilter
That's why I ask for the real example
root@r1:/home/vyos# nft insert rule ip6 filter INPUT ip6 saddr ::dead:beef/::ffff:ffff counter
Error: syntax error, unexpected string, expecting number
insert rule ip6 filter INPUT ip6 saddr ::dead:beef/::ffff:ffff counter
^^^^^^^^^^^
root@r1:/home/vyos#Yeah nftables is just the engine for iptables. EdgeOS supports this syntax.
@patrickli In 1.4 we don't use iptables, we use nftables
LInk to nftables example will be helpful.
@patrickli Could you attach an example of VyOS configuration with set service upnp xxx
If you manually change upnpd.conf does it work correctly?
Aug 14 2022
@dmbaturin, here are the changes I made: https://github.com/vyos/vyos-build/compare/equuleus...fvlaicu:equuleus
I'm using the 1.4 kernel in 1.3.