vilane
Dabbler
- Joined
- May 6, 2015
- Messages
- 32
SOLUTION Don't use Comcast DNS servers. They are blocking public torrent trackers in DNS.
hello all, I've been running my Freenas 9.3 stable build for about 4 months now (love it!) and I recently moved to a new apartment. The first major change at the new apartment was that I started using a new router (sonicwall tz100) and that I threw in the towel on changing the subnet addressing to use 192.168.1.0 instead of it's default 192.168.168.0. I believe that I went through and updated all the necessary static IP assignments for my jails and the Freenas host itself in the sonicwall. I can't seem to find any other sections in the Freenas where it has any 192.168.1.xxx addresses anymore, so I may have that completed too.
port forwarding: I created the necessary UDP and TCP service objects in the sonicwall for Transmission (using port 52444) and have them translated from the WAN to the Static for the Transmission Jail. From the Jail, I can ping 1 of 2 of the trackers on a torrent currently where I am getting the connection failed. I had checked the /etc/resolv.conf to ensure my DNS was set correctly, and I have 2 comcast DNS points and my router as the nameservers. Transmission interface is configured for port 52444 for peers and to not randomly assign a port on boot. When I look at the "port test" in transmission it tells me the port is closed, so this leads me to believe that maybe the port forwarding for the service objects is still not making it? I have it configured correctly as far as I can tell from the sonicwall as my Sickrage ports pass through perfectly using the same duplicated rules with different ports. I tried the "swap the port back and forth" trick to force the trackers to try and re-announce, but no joy.
to further complicate the jail, I have an openvpn tunnel active, which is working and is active (noted by some torrents still working correctly despite the tracker snafu, likely because of the PEX settings in Transmission maybe) but I will still get connection issues to trackers. I have tried changing around my VPN tunnel endpoint server to various USA sites to test if it was a blocklisted ip from the VPN service with the trackers, but that hasn't bore any fruit either.
Suggestions? Thoughts? Assistance?
Anything would be much appreciated guys/gals. The system isn't really down or non-functional, it's just partially working and a lot slower than it should be.
Thanks so much in advance.
hello all, I've been running my Freenas 9.3 stable build for about 4 months now (love it!) and I recently moved to a new apartment. The first major change at the new apartment was that I started using a new router (sonicwall tz100) and that I threw in the towel on changing the subnet addressing to use 192.168.1.0 instead of it's default 192.168.168.0. I believe that I went through and updated all the necessary static IP assignments for my jails and the Freenas host itself in the sonicwall. I can't seem to find any other sections in the Freenas where it has any 192.168.1.xxx addresses anymore, so I may have that completed too.
port forwarding: I created the necessary UDP and TCP service objects in the sonicwall for Transmission (using port 52444) and have them translated from the WAN to the Static for the Transmission Jail. From the Jail, I can ping 1 of 2 of the trackers on a torrent currently where I am getting the connection failed. I had checked the /etc/resolv.conf to ensure my DNS was set correctly, and I have 2 comcast DNS points and my router as the nameservers. Transmission interface is configured for port 52444 for peers and to not randomly assign a port on boot. When I look at the "port test" in transmission it tells me the port is closed, so this leads me to believe that maybe the port forwarding for the service objects is still not making it? I have it configured correctly as far as I can tell from the sonicwall as my Sickrage ports pass through perfectly using the same duplicated rules with different ports. I tried the "swap the port back and forth" trick to force the trackers to try and re-announce, but no joy.
to further complicate the jail, I have an openvpn tunnel active, which is working and is active (noted by some torrents still working correctly despite the tracker snafu, likely because of the PEX settings in Transmission maybe) but I will still get connection issues to trackers. I have tried changing around my VPN tunnel endpoint server to various USA sites to test if it was a blocklisted ip from the VPN service with the trackers, but that hasn't bore any fruit either.
Suggestions? Thoughts? Assistance?
Anything would be much appreciated guys/gals. The system isn't really down or non-functional, it's just partially working and a lot slower than it should be.
Thanks so much in advance.
Last edited: