Can I get some help with my blade please?

[phazon307]

I think the problem is in my network somewhere. Let's start from the beginning I changed my ip address from a 192.168.0.x  to a 192.168.1.x ip
I got the blade to connect once seen the configuration page and everything well I changed the ip address to 192.168.1.24 yea I know I should have set it to 192.168.0.24 well I kind of rushed it a little anyways I hit update servers and such changed my Ip back to automatically find an Ip. Well after this no matter what I do go back and change my Ip to a 192.168.1. ip I cannot connect to the blade all I get is an internet explorer cannot open the search page. I have reset my router reset my blade nothing and I mean nothing will get me back to that configuration page. I pressed the reset button on my router and touched the 2 pins on the blade next to the Ethernet port and still same thing cannot connect to search page. This is very frustrating I have had this blade for about 2 weeks and cannot get it to connect to the configuration page again. All help would be appreciated.

[stacksmasher]

Just reset it and it will go back to 192.168.1.254.... its the 2 pins by the network NIC.

[phazon307]

I have done this many times it still won't let me connect again after the first time I connected I have never been able to connect again.

[stacksmasher]

can you post a screen cap of your local network settings? If the blade is on 192.168.1.254 you need to also be on the same 192.168.1.X network.

[phazon307]

I know this I have set a static Ip of 192.168.1.10 Subnet of 255.255.255.0 gateway of 192.168.1.1 try to connect to my blades configuration page and nothing. I have tried this on more than one pc I just don't understand why it connected to the configuration page once but never again.

[7queue]

OP What o/s are you using?

Your computer needs to route to 192.168.1.0/24 if the blade was indeed reset or configured to the IP you state in your post.


Assign a temporary IP address to your computer in that range and try to ping the blade at 192.168.1.254 or the IP 192.168.1.24 you configured the blade to.



You can also add a temporary static route directly to the blades IP to bypass your router.


Most are using Windows:

 In a command prompt issue:

   ipconfig    # to find the systems IP address: 192.168.0.12 for example.

Then issue:

   route add 192.168.1.254 mask 255.255.255.255 192.168.0.12   # for default blade IP

or

   route add 192.168.1.24 mask 255.255.255.255 192.168.0.12     # the IP you configured the blade at


This will not be persistent and will go away after a reboot of the computer.


If you are using Linux you should already know how to accomplish the above in your distro.

8 )

[phazon307]

How would I add that into the CMD I tried Route 192.168.1.254 then what comes next or what is the entire command line I should run so I can get to the configuration page?

[7queue]

The commands above with 'route' up to, but not including, the # is the entire command, after that try to ping the blade:

 ping 192.168.1.254

If pings reply then you should be able to get to the config page on the blade:

 http://192.168.1.254:8000

8 )

Edit: also realize that 192.168.0.12 is an example I chose and might not be your computers actual IP!

[phazon307]

Tell me if this is right
route my ip the subnest mask and the gateway # the ip of my blade?

[7queue]

I'm guessing you are using Windows yes?

Example:

    C:\WINDOWS> ROUTE ADD 192.168.1.254 MASK 255.255.255.255  192.168.0.12
                               blades IP^                         ^mask               ^computers IP

    C:\WINDOWS> PING 192.168.1.254



What is the IP of your computer?

8 )

[phazon307]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\windows\System32>ipconfig/all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Michael
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 64-5A-04-73-8E-75
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8188E Wireless LAN 802.11n PCI
-E NIC
   Physical Address. . . . . . . . . : 64-5A-04-73-8E-75
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::711b:5cac:4475:14b1%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, November 28, 2013 5:20:16 PM
   Lease Expires . . . . . . . . . . : Friday, November 29, 2013 5:20:15 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 342120964
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-9D-E2-E8-00-8C-FA-6A-F3-25

   DNS Servers . . . . . . . . . . . : 192.168.0.1
                                       205.171.3.25
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Qualcomm Atheros AR8162/8166/8168 PCI-E F
ast Ethernet Controller (NDIS 6.30)
   Physical Address. . . . . . . . . : 00-8C-FA-6A-F3-25
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 13:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:c9f:1441:51e9:d075(Prefe
rred)
   Link-local IPv6 Address . . . . . : fe80::c9f:1441:51e9:d075%16(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{02CCC91C-C959-4AE0-B7E5-CB7CE2C3B4FA}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{006B1B50-B54C-4719-8D83-3D9B321D0CD4}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\windows\System32>

[phazon307]

I tried that and it says the requested operation requires elevation.

[7queue]

OK, so 192.168.0.3 is your computers IP


You will need to run the command prompt as administrator, you usually right click on the cmd icon in the start menu and select 'Run as Administrator'

Then issue:

  C:\WINDOWS>  ROUTE ADD 192.168.1.254 MASK 255.255.255.255  192.168.0.3



8 )

[phazon307]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\windows\system32>ROUTE ADD 192.168.1.254 MASK 255.255.255.255  192.168.0.3
 OK!

C:\windows\system32>

after ping

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\windows\system32>ROUTE ADD 192.168.1.254 MASK 255.255.255.255  192.168.0.3
 OK!

C:\windows\system32>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=10ms TTL=100
Reply from 192.168.1.254: bytes=32 time=3ms TTL=100
Reply from 192.168.1.254: bytes=32 time=7ms TTL=100
Reply from 192.168.1.254: bytes=32 time=6ms TTL=100

Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 10ms, Average = 6ms

C:\windows\system32>
  Takes me strait to bing.com

[7queue]

If indeed the blade is set to 192.168.1.254, you might try unplugging the network cable and issue the ping again, it should fail.

If it fails plug the cable back in and try the config page on the blade at http://192.168.1.254:8000

8 )

[phazon307]

I got it man thanks for all your help now I just have to figure out how to get it hashing? I use EMC Pool so do you know how I would set that up I already know the server address and user name and what not so how do I direct the blade to start hashing?

[7queue]

I use bfgminer, it has built in proxy for the blades.

https://bitcointalk.org/index.php?topic=168174.0

8 )

[phazon307]

I am using BFG miner as well in the location in properties I have it already directed towards my usb block erupters how do I add the blade?

[7queue]

Add --http-port 8332 to the end of your .bat file that starts bfgminer then point the blades at your computer.

on the blades configuration setting page set

Ports: 8332,8332
Server addresses: 192.168.0.3,192.168.0.3
user:pass: blade1:pass1,blade1:pass1

if you have more than one blade set the username: blade1 unique on each blade so they show up individually in bfgminer.

8 )

[phazon307]

Tried that in BFG Miner I am using the one where I have a shortcut on my desktop remember I am also running USB miners when I enter that command line and apply it and close and open BFG miner BFG miner just shuts down.