no progress... nmap says need to specify a host...i tried both desktop ip's, but that doesnt seem to give me anything.
there was a 0.0.0.0 ip address in wireshark...? I tried everry ip address I found...the miner is running, the ethernet lights are pinging away..... huh... I'm ready to get an ulcer
Try ipconfig /all and you'll probably see the .1 is your gateway, the .51 is assigned to the machine you're using. .255 should be the broadcast address of the subnet. As I understand bridging, if done properly, the computers after the bridge should have addresses in the same subnet as the .1, .51 and .555. So, the bridge isn't setup correctly I think.
Perhaps the bridging software you added is waking up with a setup IP address 239.255.255.250 or 224.0.0.2 and you can't access the setup page simply because you don't have a route to that address.
A typical home router, wifi or otherwise, has a single downlink and a single uplink port. The single downlink port is internal and is assigned the address you designate as the gateway but come configured with the internal downlink (gateway) address as the lowest in the function downlink network. Attached to this internal single downlink is possibly a 4 port ethernet switch which will appear on the back as four RJ45 ethernet connections; the internal downlink is also attached to a wifi port (if the router has wifi); and lastly the internal downlink port is attached to a DHCP server. The internal uplink port is attached to an RJ45 ethernet port on the back marked uplink.
A home router has a setup page which has the same address as its gateway. If you log into your wifi router on 192.168.43.1 and change the gateway address to 192.168.43.13, as soon as you click SAVE on the router setup page, you'll lose connectivity - so don't do that unless you want to hide your gateway.
The DHCP server has addresses it may assign and these are some distance numerically from the gateway. A linksys router might give DHCP 50 addresses starting from 192.168.43.50 and end at 192.168.43.100. Your router likely starts its DHCP addresses at 192.168.43.50. You computer has likely been assigned 192.168.43.51 (judging by your graphic). The address 192.168.43.50 was likely assigned to a tablet or nook or kindle sometime in the last 24 hours and the router remembered it and didn't assign it to your computer but arp -a doesn't show it because it isn't in use.
So, if the bridging/routing software you added to your computer isn't accessible, you need to put your computer on the same network as it is.
Say the routing software software is showing 239.255.255.250 as its IP address and you can't access it. Let's try this: Right click your wireless icon and disable wireless so you can't get to the internet. Open a dos cmd box and do ipconfig /all and see if the wireless connection is still showing an address. Release that address with ipconfig /release 192.168.43.51 and run ipconfig /all again and see that it has been released.
Right click your ethernet icon and open network connections. Go to your Local Area Connection properties and scroll down to Internet Protocol (TCP/IP), highlight and click Properties. It might have DHCP ticked. Unclick it and assign this address 239.255.255.249, netmask 255.255.255.0, gateway 239.255.255.001, click OK
Now, in your dos box, command "route print" and see if a route to net 239.255.255.0 exists and trying entering
http://239.255.255.001 in your browser address field. With luck that's the bridging software's setup page. If not try
http://239.255.255.250 in your browser field.
If neither of those work you might try the 224.0.0.0 network address since it's showing 224.0.0.2; assign the ethernet connection an address of 224.0.0.10, gateway 224.0.0.1, and try and access
http://224.0.0.1 or
http://224.0.0.2 after checking that a route has been added to 224.0.0.0/24
If you get to the bridging software setup page you can configure it with a 192.168.43.x address, then enable wireless, change your ethernet connection back to DHCP, reboot and see what crops up.
This is mostly guess work.
The 239 and 224 network addresses are explained here
http://en.wikipedia.org/wiki/Multicast_addressLAN's see lots of traffic on theese network addresses unrelated to DHCP or regular PC/miner IP traffic.
Windows is very chatty in multicast.
Pheonix,
It looks like your BBB is asking for an address from the pic.
You mentioned a switch.
Some switches filter DHCP by default but can be manipulated to not do this.
ex: Netgear GS108T will fuck with your dope if you are unaware if this.
If a straight cable between the PC and the miner is not working something is odd.
Have you triple checked that the PC (for direct PC/miner cable) is running a DHCP server?
Have you tried another ethernet cable?
You might try physically taking your miner to a different LAN to gain access.
Then you could set the miner to have a static IP address in the web interface.
Subdivide and conquor. eliminate everything possible and go from there.
Just throwing some ideas out there, hope this helps.
