| View previous topic :: View next topic |
| Author |
Message |
Flo2
Joined: 26 Sep 2012
Posts: 3
|
 Posted: Wed Sep 26, 2012 8:44 am Post subject: minissdpd stops working after some minutes |
 |
|
Hi,
I'm running on my server minissdpd-1.2, miniupnpd-1.7.20120824 on gentoo/linux and on all machines miniupnpc-1.7.20120830.
The server has a wifi and an two wired interface. eth1 and wlan0 bridged as br0 and eth0 as connection to External.
I'm starting
minissdpd -i 192.168.1.1 # <- ip on br0
my miniupnpd conf:
| Code: | ext_ifname=eth0
listening_ip=br0
port=0
minissdpdsocket=/var/run/minissdpd.sock
enable_natpmp=yes
enable_upnp=yes
upnp_forward_chain=forwardUPnP
upnp_nat_chain=UPnP
lease_file=/var/log/upnp.leases
bitrate_up=500000
bitrate_down=3000000
secure_mode=no
system_uptime=yes
notify_interval=60
clean_ruleset_interval=600
uuid=4735fda9-59bd-470f-a1e5-b3f2ba6c1d1a
serial=12345678
model_number=1
allow 1024-65535 192.168.1.0/24 1024-65535
deny 0-65535 0.0.0.0/0 0-65535 |
If I'm run upnpc on server it works fine - always: upnpc -m br0 -s
If I'm run upnpc on a client it works fine for some minutes after restart. But then It can't find the igd anymore:
| Code: | $ upnpc -m eth0 -s
upnpc : miniupnpc library test client. (c) 2006-2012 Thomas Bernard
Go to URL1 or URL2
for more information.
List of UPNP devices found on the network :
desc: http :// 192.168.1.20:34257 / 7ee5cd05-3165-4555-b115-cf6359806714.xml
st: upnp:rootdevice
UPnP device found. Is it an IGD ? : http :// 192.168.1.20:34257 / ## <<- no it isn't!!
Trying to continue anyway
Local LAN ip address : 192.168.1.20
GetConnectionTypeInfo failed.
GetStatusInfo failed.
Time started : Wed Sep 26 10:28:40 2012
GetLinkLayerMaxBitRates failed.
GetExternalIPAddress failed. (errorcode=-3)
Bytes: Sent: 4294967293 Recv: 4294967293
Packets: Sent: 4294967293 Recv: 4294967293 |
On debug log of minissdpd it shows first correct requests:
| Code: | | SSDP M-SEARCH from 192.168.1.20:56381 ST:urn:schemas-upnp-org:device:InternetGatewayDevice:1 |
but after a while no log entry is shown if I try to call upnpc on a client.
Only solution to make it work again: stop miniupnpd, stop minissdpd, start minissdpd, start miniupnpd
Any ideas what I can try to find the problem?
Last edited by Flo2 on Wed Sep 26, 2012 11:51 am; edited 1 time in total |
|
| Back to top |
|
 |
Flo2
Joined: 26 Sep 2012
Posts: 3
|
|
| Back to top |
|
|
miniupnp
Site Admin
Joined: 14 Apr 2007
Posts: 1589
|
| Posted: Thu Sep 27, 2012 9:31 am Post subject: |
|
|
Looks like a bug in minissdpd...
maybe you can run minissdpd in gdb, wait a few minute for him to hang and see in gdb where it is blocked ?
_________________
Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
| Back to top |
|
|
Flo2
Joined: 26 Sep 2012
Posts: 3
|
| Posted: Fri Sep 28, 2012 9:14 pm Post subject: |
|
|
mhm minissdpd don't crash. So I don't get a backtrace in gdb. I don't know if minissdpd really hangs because requests from same host works fine.
Is it possible that some network stuff is wrong because it works in promiscuous mode.
(I'm ~ 1 week afk - my reply may need some time) |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
