Author

Topic: Should I Be Traffic Shaping Port 8332 On My Dedicated Mining Router? (Read 1864 times)

full member
Activity: 140
Merit: 100
Mining uses so little bandwidth I doubt it makes much of a difference but it can't hurt.

Mining isn't a problem, but the bitcoin client will saturate the outbound link (when uploading block chain to other clients) causing your pool miners to have connection problems.
donator
Activity: 1218
Merit: 1079
Gerald Davis
It shouldn't matter much but I gave ports 8330 to 8450 highest priority on my router (since I use a couple different pools w/ different ports it was easiest to make one range).

If the outbound link becomes saturated the router will delay other traffic to ensure timely mining traffic.

Mining uses so little bandwidth I doubt it makes much of a difference but it can't hurt.
full member
Activity: 140
Merit: 100
I have a DIR-655 Dlink wireless router I am using to supply internet access to 4 mining rigs each running about 5 cards.

I am having troubles connecting to deepbit.net occasionally using phoenix miner. I will mine great for a few hours/days but eventually some of the cards go offline and never come back on. This is always preceeded by a "deepbit.net unavailable" type message...

Would It make sense to optimize port 8332 or my router in the QOS/traffic shaping section?

I have read phoenix miner is no good at re-connecting from downed internet connections (I am using the version available in linuxcoin v0.2a, not sure what version of phoenix it is, perhaps I have to upgrade?)

Any suggestions are appreciated!

Necromancy FTW!!!

I've noticed my bitcoin client will saturate the outgoing link a couple times a day which causes timeout errors from the miners, and I've been trying to get traffic shaping to work with the Tomato firmware on my Linksys router. Does anyone have any suggestions?
sr. member
Activity: 280
Merit: 252
it's probably due to DDOS on the major pools and isn't something traffic shaping would fix

Well I am not 100% sure what the problem is.

Do the newer versions of phoenix miner recoup from a downed internet connection and/or ddos downed pool in general?
full member
Activity: 154
Merit: 100
it's probably due to DDOS on the major pools and isn't something traffic shaping would fix
sr. member
Activity: 280
Merit: 252
I have a DIR-655 Dlink wireless router I am using to supply internet access to 4 mining rigs each running about 5 cards.

I am having troubles connecting to deepbit.net occasionally using phoenix miner. I will mine great for a few hours/days but eventually some of the cards go offline and never come back on. This is always preceeded by a "deepbit.net unavailable" type message...

Would It make sense to optimize port 8332 or my router in the QOS/traffic shaping section?

I have read phoenix miner is no good at re-connecting from downed internet connections (I am using the version available in linuxcoin v0.2a, not sure what version of phoenix it is, perhaps I have to upgrade?)

Any suggestions are appreciated!
Jump to: