Bitcoin Forum

Hello! I'm pretty new to Bitcoin Mining, the only mining I've done is CPU/GPU on my laptop, and the most I've gotten is 80Mh/s with my card. But, since I'm at college, and the watts on campus flow like cheap beer, I purchased a Block Erupter Cube to get into the business and turn a profit while I work on my education.

But the biggest problem I've had on campus is the IT Department's Nazi-like grip of the internet connection. Any routers set up on the network are quickly sniffed out and shut down by the RAs, and since I'm living in a dorm, there's not much I can do about it. I'm hoping to make enough coin during this semester to get a dorm off-campus next semester, but to do that, I need to start mining ASAP.

The Block Erupter Cube is alive, the firmware is updated, and I've got it plugged into the campus's LAN network. I was following the guide at https://bitcointalk.org/index.php?topic=352658 but no matter what I've tried, I can't get to the Cube's IP address to configure it. I've tried all the IP combinations I can think of, but none of them get me to the Cube. It's really frustrating; I've got the device, it's working fine, but I can't do anything with it. Also, since I can't connect a router to the LAN, I don't have any physical access to the primary router.

If anyone could help me, I'd really appreciate it!

Here's some specifications if they'll help:
Windows 7 64-bit
Miner: BFGMiner (no problems with that so far since I can't even configure the miner and don't know its IP for certain)
Hardware: ASICMiner Block Erupter Cube
My current IP address: 149.149.220.47
Subnet Mask: 255.255.254.0
Default Gateway: 149.147.220.1

I'm not very software/IT savvy so if additional information's needed I can give it (unless I can't find it).

It's possible that the network doesn't allow peer-to-peer traffic in the dorms.

Find a compsci friend, buy him/her beer.  Explain what you're trying to do.  Explain that the cube is a static IP.  They may tell you that it's all firewalled, or may have a tip or two.

In theory, you can get around it with two NICs.  Leave your PC connected as-is on NIC#1.  Set the cube network up NIC#2 static LAN.  Configure the proxy to listen for getwork on NIC#2.  Crossover cable may be required.

Cube -> PC/Proxy -> Network

This is what I did, the mining rig server uses wifi for WAN. The NIC connects to(LAN) a switch on the same subnet the cubes are on.

Also if you run one proxy per two cubes and run proxy command with -q switch for quiet, you will get fastest productivity.

That worked! I talked it over with a MIS major and he told me pretty much the same thing. A jargon-filled chat here, a greased palm there, and now my Cube is pumping 36-38 GH/s! I barely understood what he was saying, but it had something to do with a static LAN and network cards.

Thank you so much! Now I've got a passive income while I work on my studies! Thanks again!