miniupnpd: The latest updated version does not work properly beasue of detected wrong wan port
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
this bug reported in The latest updated version does not work properly.There are no active redirects. #556
Miniupnpd Contributor can not find any bugs
I have 3 wan. one have public ipv4 ,the other 2 have private ipv4,and 1 public ipv6
the upnp use the port with 1 privat ipv4 and 1 public ipv6 to work
with OpenWrt SNAPSHOT r16765-6f3a05ebb0 / LuCI Master git-21.124.24916-0faf9a4 and miniupnpd 2.2.1-2
they work very well
with OpenWrt SNAPSHOT r17247-022d1fe80f / LuCI Master git-21.196.22411-7d9ab8d and miniupnpd 2.2.2-3
luci can not see any upnp clients
some message can help to fix bug
ip add show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP group default qlen 1000
link/ether be:08:f2:14:e8:7a brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 6e:28:59:37:ad:f4 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.2/24 brd 192.168.100.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::6c28:59ff:fe37:adf4/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 4e:98:29:33:46:24 brd ff:ff:ff:ff:ff:ff
inet 192.168.150.2/24 brd 192.168.150.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::4c98:29ff:fe33:4624/64 scope link
valid_lft forever preferred_lft forever
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 7a:c9:43:45:77:61 brd ff:ff:ff:ff:ff:ff
inet 192.168.200.2/24 brd 192.168.200.255 scope global eth3
valid_lft forever preferred_lft forever
inet6 fe80::78c9:43ff:fe45:7761/64 scope link
valid_lft forever preferred_lft forever
7: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether be:08:f2:14:e8:7a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
valid_lft forever preferred_lft forever
inet6 fe80::bc08:f2ff:fe14:e87a/64 scope link
valid_lft forever preferred_lft forever
9: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet 10.0.0.1/24 brd 10.0.0.255 scope global wg0
valid_lft forever preferred_lft forever
13: pppoe-cmcc_wan: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN group default qlen 3
link/ppp
inet 10.255.52.207 peer 10.255.0.1/32 scope global pppoe-cmcc_wan
valid_lft forever preferred_lft forever
inet6 240**:8a44:c40:c0bd:f8f5:ce59:ca1b:d9f8/64 scope global dynamic noprefixroute
valid_lft 258218sec preferred_lft 171818sec
inet6 fe80::f8f5:ce59:ca1b:d9f8 peer fe80::f22f:a7ff:fe02:350a/128 scope link
valid_lft forever preferred_lft forever
22: pppoe-ct_wan: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN group default qlen 3
link/ppp
inet 10.16.109.94 peer 10.16.0.1/32 scope global pppoe-ct_wan
valid_lft forever preferred_lft forever
24: pppoe-cu_wan: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN group default qlen 3
link/ppp
inet 115.55.146*** peer 115.55.144.1/32 scope global pppoe-cu_wan
valid_lft forever preferred_lft forever
inet6 24**:8220:c02:360f:6e28:5991:f437:adf4/64 scope global dynamic noprefixroute
valid_lft 2591549sec preferred_lft 604349sec
inet6 fe80::6e28:5991:f437:adf4 peer fe80::4e09:b4ff:fefc:a690/128 scope link
valid_lft forever preferred_lft forever
/etc/config/upnpd
config ` upnpd 'config
option download '1024'
option upload '512'
option internal_iface 'lan'
option port '5000'
option upnp_lease_file '/var/run/miniupnpd.leases'
option ext_ip_reserved_ignore '1'
option enabled '1'
option uuid 'b12a26f3-e262-4cd3-978b-2f67e8b17c85'
option igdv1 '1'
config perm_rule
option action 'allow'
option ext_ports '1024-65535'
option int_addr '0.0.0.0/0'
option int_ports '1024-65535'
option comment 'Allow high ports'
config perm_rule
option action 'deny'
option ext_ports '0-65535'
option int_addr '0.0.0.0/0'
option int_ports '0-65535'
option comment 'Default deny'
/var/etc/miniupnpd.conf
ext_ifname=pppoe-cmcc_wan
ext_ifname6=pppoe-cmcc_wan
listening_ip=br-lan
enable_natpmp=yes
enable_upnp=yes
secure_mode=yes
system_uptime=yes
force_igd_desc_v1=yes
ext_perform_stun=no
ipv6_disable=no
ext_ip_reserved_ignore=yes
bitrate_down=8388608
bitrate_up=4194304
lease_file=/var/run/miniupnpd.leases
port=5000
uuid=b12a26f3-e262-4cd3-978b-2f67e8b17c85
allow 1024-65535 0.0.0.0/0 1024-65535 #Allow high ports
deny 0-65535 0.0.0.0/0 0-65535 #Default deny
ps w|grep upnp
17462 root 1088 R grep upnp
29977 root 8740 S /usr/sbin/miniupnpd -f /var/etc/miniupnpd.conf
with OpenWrt SNAPSHOT r16765-6f3a05ebb0 / LuCI Master git-21.124.24916-0faf9a4 and miniupnpd 2.2.1-2
they work very well
miniupnpd_ok log is here
upnp_ok.log
with OpenWrt SNAPSHOT r17247-022d1fe80f / LuCI Master git-21.196.22411-7d9ab8d and miniupnpd 2.2.2-3
luci can not see any upnp clients
miniupnpd_false log is here
upnp_false.log
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing miniupnp_ok.log with miniupnp_false.log and the provided miniupnpd.conf between versions 2.2.1-2 and 2.2.2-3. Review the /etc/config/upnpd settings and multi-WAN interface selection; done means LuCI detects UPnP clients and the correct WAN port is used in the reported OpenWrt setup.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100