Topic: [SOLVED] 2BTC Reward to get ASICMiner Blades >12 GH/s on stratum - page 2. (Read 7604 times)

http://imageshack.us/a/img856/8769/bladev.png

Uploaded with ImageShack.us

A couple shots in the dark (but based on actual thoughts)

1) When you were messing with the CTS settings, did you try enabling it and setting the type to 'rts_cts'

2) Did you try reducing the wireless compatibility settings all the way down to 'performance mode (n only)' (I realize it may cut off some of your wireless devices, just curious if lowering it down helps the hashrate)


EDIT: I am confused as to why the new router didn't work, but I am assuming the other guy is having a different issue.
Did you make sure the firmware of that new router matched the version of the other guys firmware version?

I would also try the 'legacy mode' on number 2  

I totally agree. I've also seen where a particular wireless device has had a corrupted firmware that would essentially DDOS the system, because it would keep sending the all TCP tx request packets, even after getting an answer. It was weird, almost like a memory leak, it would accumulate requests, and just keep sending them ALL. It would start out causing moderate collisions, and then with much use at all, the whole thing would snowball, and bring the whole network down HARD (even though everything still APPEARED functional). The wireless device would still function on the network (to a point) but it completely fucked network traffic for everything else. Every time the user would turn on his laptop, it would kill his roommates' xbox live connectivity, and they all wanted to kill him badly enough that they paid me to come figure out WTF was going on. Firmware update for his wireless card (and one for their router, just for good measure), and a reinstall of the driver, fixed everything up quite nicely, and I never got another call over that issue.

Hence the suggestion to update firmware on the router and all devices, but I guess he took it as a joke... Meh.

I'd really love to be able to watch the system monitoring while you attempt to mine with them... I feel like something should be shown in the logs that gives some type of clue as to what's going on... any chance on enabling remote management and giving me your IP/username/password?    

You have static ip's on all devices?
If you have, do you have DHCP on?

Edit: Your router has the ability to specify the amount of bandwidth that each ip can use?
It can be that some of your mates is using too much bandwidth.

Have you went down the vlan path yet?...

Some other ideas - have you tried running a constant ping (from the proxy system) on the pool's IP while you attempt to mine with the blades... to see if any packet loss or increased latency is being caused?   Its just odd that some of the hashing gets through and some doesn't... this seems to indicate some type of packet loss or for some reason the verizon router is dropping some of the communication when the wifi is enabled. There is a chance that the communication between the switch and the proxy is having issues, but I believe you have already eliminated this by hooking the blade directly to the router and it wouldn't explain why enabling the wifi on the router causes the issue. (sorry, thinking 'out loud')

I'd also run a constant ping on some of the other machines to see what happens when the wifi is enabled, and if it effects the pings at all.

I suggested separate vlans to the OP. I don't think he tried it though.

I've checked multiple times, it's not an IP conflict.

Hi.
You said that you have static ip's on the blades, right?
And the rest of the network? The other computers and etc.
It may be that another device that is connected to the wifi is using the same ip as the blades.
Check all the ip's on the entire network. If you have some device that is using dynamic ip, change to static as well.
Hope it helps you.

The proxy system is on the switch with the blades. I've tried running the proxy on other local PCs not on the switch, it makes no difference.

New router connected, using verizon router as a bridge. Same problem. Ready to chuck blades out the window. Taking a break, be back later.

If the new router doesn't work... you may also need to try and find the same firmware version that the other guy is using - if it is older...
 (as a last ditch effort to try and get the new router to work)

I love the WRT54GL for a wireless router, nothing beats old school.

Another idea would be to try and get the proxy system connected to the switch (if it isn't already)... it sounds like the proxy is currently connected to the router, which means the blades have to go through the router to communicate to the proxy, then the proxy comes back through the router and out to the pool... might be a simpler setup if the proxy is connect to the switch, and the blades communicate through the switch to the proxy system... and ultimately out through the router when communicating to the pool.

I am starting to stretch for ideas now, so I am going to wait until Nave replies to go any further... before my head explodes    


EDIT:  and, of course you reply now... good luck with the new router, hopefully the easy solution!

I just got the new router, I'll be setting it up in a couple minutes. If it doesn't work I'll probably try setting up a couple vlans and seeing if segregating the traffic makes a difference. I really doubt its wifi interference, as I would imagine the amount of other people using blades and having a wireless network running simultaneously would be creating many more problems than my little posting. I'll let you guys know if this new router solves things.

This will narrow it down to some weird wifi interference with the blades (which would be odd) and some ip address dhcp conflict, which seems more likely.  Unless one of the wireless devices is running upnp and is stealing port the stratum port (3333?) for itself.

I don't believe this will work, because the issue doesn't seem to have much to do with the connectivity between the blades and the proxy...  (because the traffic still has to pass through the verizon router to get to the internet, and I feel like the router is causing the issue)... although the laptop idea may be something to try... because that forces the traffic through the wifi which may have different results, might be the same issue though... it would be worth a try if you have a laptop or a wifi card you could put onto the proxy system.

But, this did give me another idea if the new router doesn't work... which would be to try and segment the wifi/wired traffic and basically create 2 different vlans on the router. This *may* force the router to handle the traffic differently and may circumvent the problem... but setting up vlans on a verizon router can prove challenging... and involves breaking the bridged connections that Verizon routers create, creating the vlans and assigning them to specific ethernet ports. I have done it before... it's just not pretty, especially if you ever have to reset that verizon router (which verizon support loves doing in the event of any issue)... here is a basic guide I found for doing it: http://blog.jeffreyberg.net/?p=56

But you need to be prepared to handle any troubleshooting once you start this process, as you may drop off the internet while doing it.

That's known as the "Shotgun approach" and it rarely works. There is a methodology to troubleshooting things. You don't rebuild the engine when the tires are wobbling. 

So you know what the problem is? Is this already fixed? Everything is worth a try in my opinion.

Do you have a second NIC lying around?  Since the blades only need to connect to your stratum proxy you might try creating a new LAN with a different subnet and hooking your blade switch directly to your proxy computer.  If you don't have a second NIC you could test by installing the proxy on a laptop and using its ethernet controller as the new lan and its wireless to connect to your router.

And I forget if you've tried it without the switch?  Connect one blade and your proxy directly to your router.