<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</head><body><p>I will try all that shortly, thanks. They are static addresses.<br></p><p>I had ****.140 on DMZ, and ***.199 on port fwd:9001, because it would not open the ORport otherwise - now I understand why. After that, the DMZ would not find :9001, the fwd seemed to circumvent it. So I changed the DMZ to port 443, but still had 2 days of no ORport. The Dirport & Controlport have continued to function all the time.<br></p><p>I assume I change the torrc to reflect any port changes. I will try with your suggestions.<br></p><p><br></p><p>Thx, G<br></p><blockquote type="cite"><p>On June 24, 2015 at 10:46 AM s7r <s7r@sky-ip.org> wrote:<br><br><br>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA256<br><br>Hello<br><br>Thanks for adding one more relay.<br><br>It's ok to have 2 relays on one IP address, both should work.<br><br>What do you mean you have enabled DMZ and port forwarding?<br><br>If you enable DMZ, that will forward ALL ports to 1 IP address in the<br>subnet (NAT). You cannot enable DMZ on 2 different internal IP<br>addresses in the same LAN. Also, if DMZ is enabled one time, port<br>forwarding for the second IP won't work since all ports are already<br>forwarded to the DMZ host.<br><br>Use static internal LAN IP addresses for both relays. IP1 for relay1<br>and IP2 for relay2. So after a power cutoff everything will get back<br>online with the same IP config and port forwards will work.<br><br>Forward port 443 to internal IP1<br>forward port 80 to internal IP1 (if you also use DirPort)<br>forward port 9001 to internal IP2<br>forward port 9030 to internal IP2 (if you also use DirPort)<br><br>Examples are informative, use whatever ports you want/can.<br><br>Let me know if it worked.<br><br><br>On 6/24/2015 5:22 PM, TORnet Zone wrote:<br>> Really need some help here, just cannot find the answer.<br>> <br>> I've been running 2 middle relays for a year now, from a<br>> home/business IP, one DSL and the other cable. Only problems were<br>> brief and IP induced all has served the system well.<br>> <br>> I recently attempted to add a 3rd relay on the same cable feed as<br>> one of my others, but there is no way the ORport will connect. I<br>> have DMZ'd the static address, forwarded the ports, changed the<br>> ports - the ORport just will not open. And yes I realize diversity<br>> is tightened, but I'm trying to help all I can on my budget. First<br>> - CAN there be two relays on the same dynamic address (different <br>> port numbers) ? How? Do I need some form of DNS service to help?<br>> <br>> Relay 1 is Linux 3.2.0-86 and Tor 0.2.6.9. Relay 2 is Linux<br>> 3.16.0-30 and Tor 0.2.6.9. The DMZ'd relay worked until I had to<br>> forward 9001 to the 2nd, then it quit. Uptime was normally 40 - 50<br>> days until a kernel update, or something major. Both are old<br>> laptops on battery backups that never have power down. Router is an<br>> Archer C7, latest firmware.<br>> <br>> -Gumby _______________________________________________ tor-relays<br>> mailing list tor-relays@lists.torproject.org <br>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br>> <br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v2.0.22 (MingW32)<br><br>iQEcBAEBCAAGBQJVisK1AAoJEIN/pSyBJlsRuKAH/iCxwhmKu4jv+VprwZ7c3M5o<br>E5Bx01V9Dhi2AL4tu2QfSA4FQJFmvBOJr1v2LytvdLswfdale26+wZM9x/NLMlfS<br>E8mM5FrEiJ+vi4MmSxgx94SoeAPzFJ+dlnrNuvYihdGkAJwchT5+WdtcM0t4YqM8<br>CJ95LZRh3r6w36AO6RiDTYRBfG4AhsZmUjftsvSSntFTcleJJV+uC5wM9SBuUq5f<br>Ne9MXIXC8+pmfAsYhmS7MwkWcB8IP1k/0vgLRhh/EbZAxc5eYsEyO502TxR4HFt0<br>BzGMBuP0yMl4Frn4oiKnB4jiUfJPLrHc8vT5hIA8U6CA+4BYHTbKGU1tgmjP0qY=<br>=jdzn<br>-----END PGP SIGNATURE-----<br>_______________________________________________<br>tor-relays mailing list<br>tor-relays@lists.torproject.org<br>https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays<br></p></blockquote></body></html>