I just upgraded from RC2 to RC5. I recently configured my Windows Server 2003 R2 SP2 machine to use ipv6 to test an ipv6 news server. This worked great until I installed RC5.
I have always had host = 0.0.0.0 in my .ini file so sabnzbd would listen on all available IP addresses.
When I do this with RC5 and run a netstat -an | find ":8080" I get this:
TCP [::]:8080 [::]:0 LISTENING 0
So it's no longer listening on ipv4.
When I replace the 0.0.0.0 with one of the ipv4 addresses of my server, everything works again.
However I would like it to listen on all ipv4 addresses again, since I use different addresses for accessing sabnzbd from inside and outside my network.
Possible ipv4/ipv6 bug in RC5?
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Possible ipv4/ipv6 bug in RC5?
This was probably changed by an upgrade of the webserver package we use.
Why do you want to listen on both the external IP and localhost?
Cannot you use external IP always?
If you use
it will use the IPV4 addresss (only localhost will be missing).
Why do you want to listen on both the external IP and localhost?
Cannot you use external IP always?
If you use
Code: Select all
--server :port
Re: Possible ipv4/ipv6 bug in RC5?
It is less of a bug, and more of a feature out of our control. Since RC2 we upgraded CherryPy (the webserver) to the latest version of the 2.x branch. This has better ipv6 support.
We simply let the OS make the decisions, and for vista it places IPv6 priority above IPv4. This would be a great thing in a few years time when IPv6 use is more common, yet we are in the area where IPv6 is still on the horizon, and vista has decided to future proof themselves by prioritising IPv6.
We have two choices, either roll back to the previous cherrypy version and lose all the bug fixes, or recommend you to use a blank host (-s :8080 or your localip address)
We simply let the OS make the decisions, and for vista it places IPv6 priority above IPv4. This would be a great thing in a few years time when IPv6 use is more common, yet we are in the area where IPv6 is still on the horizon, and vista has decided to future proof themselves by prioritising IPv6.
We have two choices, either roll back to the previous cherrypy version and lose all the bug fixes, or recommend you to use a blank host (-s :8080 or your localip address)
Re: Possible ipv4/ipv6 bug in RC5?
My server has two "internal" IP addresses really, one in the 192.168.x.x range and one in the 10.x.x.x range.shypike wrote: Why do you want to listen on both the external IP and localhost?
Cannot you use external IP always?
I use the 10.x.x.x address for a Gbit cross-link with my workstation. The 192.168.x.x address is connected to my router.
So if I wanted to access sabnzbd from my workstation I used the 10.x.x.x address (through a hosts file entry) and if I wanted to access it from outside I used a port mapping in my router to the 192.168.x.x address.
Specifying an empty host/server does make sabnzbd listen on ipv4, but only on the 192.168.x.x address.
It's not really important, because I can access sabnzbd on the 192.168.x.x address from my workstation too and I don't really need the Gbit speed for that anyway

Maybe it would be possible to change the host/server parameter to allow specifying more than one IP address, separated by comma's for example?
Re: Possible ipv4/ipv6 bug in RC5?
Unfortunately, that won't be possible till we upgrade to CherryPy3. Currently this is aimed for 0.5 however don't hold your breath.