Bitcoin Forum
September 19, 2018, 11:27:12 PM *
News: ♦♦ Bitcoin Core users must update to 0.16.3 [Torrent]. More info.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Installing Watchguard XTM2 25 on My Network...Blocking Miner Traffic  (Read 1352 times)
luckypyrate
Full Member
***
Offline Offline

Activity: 168
Merit: 100


View Profile WWW
October 03, 2014, 12:53:49 AM
 #1

I have been P2Pool mining steadily for about a year now and decided to upgrade my security to a WatchGuard XTM2 25w.  I got everything set up fine and everything works great, except no matter what I SNAT,  Policy, etc, it still blocks my miners.  I have 5 Ant miner S1's and 2 S3's.  Any ideas? Huh

Sorry if this is not the right spot to post, but it seemed most relevant to me.

Life is too serious to be taken seriously
1537399632
Hero Member
*
Offline Offline

Posts: 1537399632

View Profile Personal Message (Offline)

Ignore
1537399632
Reply with quote  #2

1537399632
Report to moderator
1537399632
Hero Member
*
Offline Offline

Posts: 1537399632

View Profile Personal Message (Offline)

Ignore
1537399632
Reply with quote  #2

1537399632
Report to moderator
1537399632
Hero Member
*
Offline Offline

Posts: 1537399632

View Profile Personal Message (Offline)

Ignore
1537399632
Reply with quote  #2

1537399632
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Ren13B
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
October 03, 2014, 11:50:42 PM
 #2

If you are in the Policy Manager add a policy, select custom, new...  Give it a name and click Add...  Under Protocols select Any and click OK.  Click Add... button.  Open up the policy you just created and add your miners ip addresses in the From section or you can just add your entire network.  Add Any to the To section.  Make sure the security stuff is unselected like Application Control and IPS and then click OK.  Check the positioning of the rule and move it to the top if it's not there already.  Save the config and you should be good to go.  
  
luckypyrate
Full Member
***
Offline Offline

Activity: 168
Merit: 100


View Profile WWW
October 04, 2014, 12:33:23 PM
 #3

Thank you for your reply.  I set up the watchguard with a bridge on the other 3 ports to a trusted bridge group which I am thinking is contributing to the problem.  I have reset the watchguard and will try again tonight.

Life is too serious to be taken seriously
Stoic Joker
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
October 05, 2014, 12:59:38 PM
 #4

I've got 2 XTM25's with a CIDR block DMZ'd between them, and am running 2 S2's behind then in the LAN. Nothing special should be required to get them running, unless you're running some type of web filtering for users on the XTM25. In that case you policy order becomes critical, as the miners-bypass-filter allow rules would need to be at the top of the rule list (e.g. evaluated first) to ensure they could get their requests out to the web.

On some of the WatchGuard routers there is a policy analysis tool that will tell you what rule can/will block traffic to/from internal and external targets.

Also be sure that the DNS servers used by the miners aren't being filtered/restricted in case the pool isn't in the allowed sites list.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!