SABnzbd Forums

Hey all,

I set SAB to listen on <blank>, which is responds on it's internal IP (192.168.x.x), which was fine. I have IPv6 access at home, and a few other locations, and would like to be able to access SAB that way. So I configured it to listen on that, and it works, however I can't access it using an IPv4 address anymore.

Is there any way to get it to listen on both? Either I'm missing something, or this is an oversight by the fine folks who make this software. Because I can't access IPv6 from everywhere yet, it's a bit of a pain.

Which OS?

This is on Windows 7

xero9 wrote:This is on Windows 7

On Linux, when you fill out "::" as listening host in SAB, both IPv4 and IPv6 work.
I rarely use Windows, so could you check out & report back what the result is of :: on Windows?

FWIW: I vaguely remember something with ::, IPv4/IPV6 in SAB 0.7.0, but I can't remember what. Maybe it is just something with some browsers not understanding :: nor ::1, but maybe it is the point you mention...

Is your external IP an IPv6 address?
As it is likely that you have a router, it's the router that handles IPv6.
SABnzbd will still use internal addresses, which are likely to be IPv4.
The mapping from your external IPv6 address to the system running SABnzbd
is done by port-forwarding on your router. Something that you
must explicitly setup yourself.

shypike wrote:Is your external IP an IPv6 address?
As it is likely that you have a router, it's the router that handles IPv6.
SABnzbd will still use internal addresses, which are likely to be IPv4.
The mapping from your external IPv6 address to the system running SABnzbd
is done by port-forwarding on your router. Something that you
must explicitly setup yourself.

Shypike, with IPv6 it's not like that. With IPv6 there is no more NAT as each LAN (or home network) will have 2^64 different IPv6 addresses. (So that's IPv6 addresses on your LAN than IPv4 addresses on the public Internet.) With such an IPv6 address, there is straight, non-NATed traffic to other IPv6 systems. Please note: IPv4 is still there for IPv4 connections.

FYI:
I have native IPv6 at home (provided by Telfort) and on my VPS. So I can directly access the SAB instances running on all my systems.

I hope the router still protects you from incoming traffic.
Otherwise IPv6 is an accident waiting to happen.

shypike wrote:I hope the router still protects you from incoming traffic.
Otherwise IPv6 is an accident waiting to happen.

A lot of routers/ISPs indeed default to drop unknown inbound IPv6 traffic, and you have to add IPv6 exceptions or disable the IPv6 fiewall completely ... which I have done on my Zyxel P-2812HNU-F1: with 18446744073709551616 dynamic IPv6 addresses on my LAN, I'm not too scared of port scanning ...

BTW, Shypike: what does http://test-ipv6.com/ tell about *your* IPv6? It's built in in Windows Vista and higher (only blocked by silly, non-MS firewalls and virusscanners)

sander wrote:

shypike wrote: BTW, Shypike: what does http://test-ipv6.com/ tell about *your* IPv6?

As IPv4 as can be.

any updates on this for the windows front? looks like we can only pick either ipv4 or ipv6?

So far, the answer is still: no progress.
It's also a numbers game: active IPv6 users like you are rare creatures.