Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 59. (Read 324176 times)
March 19, 2012, 09:43:57 PM
it didnt pick up my adapter either, i use this one http://www.meritline.com/airlink101-awll5088-wireless-n-ultra-mini-usb-adapter---p-45923.aspx
March 19, 2012, 09:23:30 PM
Unfortunatelly, BAMT not support wireless network 
I've had no problem in running bamt over a wireless network.Well, you are one of the few.
I have 3 USB adapters, 2 RaLink and a Broadcomm, all listed as supported for debian sqeeze. 1 RaLink doesn't even show up when attached, the other and the Broadcomm chip show up, but refuse to connect to the network. I got a old "g" adapter to connect, once, it stayed connected for about 2 hours, disconnected, then refused to be recognized after that.
In fact, it has been stated that by the author that wireless is not supported.
It was not supported in 0.4, but as of the 0.5 image it should work fine. Does for me at least. I have only a few adapters to test with, but they all "just work". this is first i've heard of trouble since 0.5.
Don't know what to tell you. Simply doesn't work for me with four different adapters and chipsets. Are you using encryption? WES? WPA? WPA2? Using WPA2 with AES here. wpasupplicant loaded via aptitude install.
March 19, 2012, 07:25:45 PM
Unfortunatelly, BAMT not support wireless network
I've had no problem in running bamt over a wireless network.Well, you are one of the few.
I have 3 USB adapters, 2 RaLink and a Broadcomm, all listed as supported for debian sqeeze. 1 RaLink doesn't even show up when attached, the other and the Broadcomm chip show up, but refuse to connect to the network. I got a old "g" adapter to connect, once, it stayed connected for about 2 hours, disconnected, then refused to be recognized after that.
In fact, it has been stated that by the author that wireless is not supported.
It was not supported in 0.4, but as of the 0.5 image it should work fine. Does for me at least. I have only a few adapters to test with, but they all "just work". this is first i've heard of trouble since 0.5.
March 19, 2012, 07:24:20 PM
Unfortunatelly, BAMT not support wireless network
what?
March 19, 2012, 04:14:12 PM
Unfortunatelly, BAMT not support wireless network
I've had no problem in running bamt over a wireless network.Well, you are one of the few.
I have 3 USB adapters, 2 RaLink and a Broadcomm, all listed as supported for debian sqeeze. 1 RaLink doesn't even show up when attached, the other and the Broadcomm chip show up, but refuse to connect to the network. I got a old "g" adapter to connect, once, it stayed connected for about 2 hours, disconnected, then refused to be recognized after that.
In fact, it has been stated that by the author that wireless is not supported.
March 19, 2012, 04:01:05 PM
Maybe try with another network controller (PCI ethernet card)?
March 19, 2012, 03:48:48 PM
Unfortunatelly, BAMT not support wireless network
I've had no problem in running bamt over a wireless network. 
March 19, 2012, 03:33:11 PM
Unfortunatelly, BAMT not support wireless network
March 19, 2012, 02:03:33 PM
Oy...
I have 1 machine that is having problems. It has an IP assigned in the router, and it gets assigned that IP when it first boots. After an indeterminate amount of time, its IP address and routing information will simply cease to exist. I can then assign an IP address manually through ifconfig and it will maintain that IP address indefinitely.
This is a problem with BAMT, not with the router. It's possible it's a hardware issue, but since the machine is able to keep the IP address when configured manually and works fine outside of BAMT, I'm going with Occams razor. Since my last attempts at trying to get BAMT improved met with a brick wall, vitrol and insults, I have elected to just try to solve the problem through statically assigning the IP address, but since BAMT does not maintain the /etc/networking directory (or /etc/resolv.conf) through reboots natively, I'm asking if that can be done.
Router is fine. DHCP is fine. Everything but this one BAMT machine works as far as routing and IP assignments go.
I have 1 machine that is having problems. It has an IP assigned in the router, and it gets assigned that IP when it first boots. After an indeterminate amount of time, its IP address and routing information will simply cease to exist. I can then assign an IP address manually through ifconfig and it will maintain that IP address indefinitely.
This is a problem with BAMT, not with the router. It's possible it's a hardware issue, but since the machine is able to keep the IP address when configured manually and works fine outside of BAMT, I'm going with Occams razor. Since my last attempts at trying to get BAMT improved met with a brick wall, vitrol and insults, I have elected to just try to solve the problem through statically assigning the IP address, but since BAMT does not maintain the /etc/networking directory (or /etc/resolv.conf) through reboots natively, I'm asking if that can be done.
Router is fine. DHCP is fine. Everything but this one BAMT machine works as far as routing and IP assignments go.
Could your USB possibly be corrupted somehow. I understand these types of issues can be frustrating, but lets try a couple other things before deciding that it's all BAMTs fault.
If you have another USB key, try loading BAMT up on it and see what happens.
I have never had an issue like this before. I have 18 machines running BAMT.
Tried a different (and new) USB key as the first thing. It's the only machine that does this (ASRock Deluxe 5), the other 3 machines I am testing BAMT on hold their IP just fine. I'm not saying it's a problem with BAMT, but with BAMT and this particular machine. I also tried removing and reassociating the MAC with the IP (and changing the IP) and it all yields the same results. Routing works perfectly fine if I statically assign the IP though.
Quote
bitminerN8 has provided a good answer. there may be other ways, but this works.
This sticks through a reboot? I'll hit that up when I get home, but it was my understanding that was stored on the ROFS and not copied over when it was changed.
March 19, 2012, 01:38:34 PM
One of my machines keeps losing it's IP address. It's like the lease expires, but never renews. Only happens on one machine... is there a way to assign a static IP permanently to the machine that will survive a reboot?
I believe from the desktop, not SSHed in, you can right click on the network plug icon near the clock and edit the network config. But a reservation via DHCP would be best.
bitminerN8 has provided a good answer. there may be other ways, but this works.
March 19, 2012, 01:35:03 PM
Oy...
I have 1 machine that is having problems. It has an IP assigned in the router, and it gets assigned that IP when it first boots. After an indeterminate amount of time, its IP address and routing information will simply cease to exist. I can then assign an IP address manually through ifconfig and it will maintain that IP address indefinitely.
This is a problem with BAMT, not with the router. It's possible it's a hardware issue, but since the machine is able to keep the IP address when configured manually and works fine outside of BAMT, I'm going with Occams razor. Since my last attempts at trying to get BAMT improved met with a brick wall, vitrol and insults, I have elected to just try to solve the problem through statically assigning the IP address, but since BAMT does not maintain the /etc/networking directory (or /etc/resolv.conf) through reboots natively, I'm asking if that can be done.
Router is fine. DHCP is fine. Everything but this one BAMT machine works as far as routing and IP assignments go.
I have 1 machine that is having problems. It has an IP assigned in the router, and it gets assigned that IP when it first boots. After an indeterminate amount of time, its IP address and routing information will simply cease to exist. I can then assign an IP address manually through ifconfig and it will maintain that IP address indefinitely.
This is a problem with BAMT, not with the router. It's possible it's a hardware issue, but since the machine is able to keep the IP address when configured manually and works fine outside of BAMT, I'm going with Occams razor. Since my last attempts at trying to get BAMT improved met with a brick wall, vitrol and insults, I have elected to just try to solve the problem through statically assigning the IP address, but since BAMT does not maintain the /etc/networking directory (or /etc/resolv.conf) through reboots natively, I'm asking if that can be done.
Router is fine. DHCP is fine. Everything but this one BAMT machine works as far as routing and IP assignments go.
Could your USB possibly be corrupted somehow. I understand these types of issues can be frustrating, but lets try a couple other things before deciding that it's all BAMTs fault.
If you have another USB key, try loading BAMT up on it and see what happens.
I have never had an issue like this before. I have 18 machines running BAMT.
March 19, 2012, 01:27:45 PM
Oy...
I have 1 machine that is having problems. It has an IP assigned in the router, and it gets assigned that IP when it first boots. After an indeterminate amount of time, its IP address and routing information will simply cease to exist. I can then assign an IP address manually through ifconfig and it will maintain that IP address indefinitely.
This is a problem with BAMT, not with the router. It's possible it's a hardware issue, but since the machine is able to keep the IP address when configured manually and works fine outside of BAMT, I'm going with Occams razor. Since my last attempts at trying to get BAMT improved met with a brick wall, vitrol and insults, I have elected to just try to solve the problem through statically assigning the IP address, but since BAMT does not maintain the /etc/networking directory (or /etc/resolv.conf) through reboots natively, I'm asking if that can be done.
Router is fine. DHCP is fine. Everything but this one BAMT machine works as far as routing and IP assignments go.
I have 1 machine that is having problems. It has an IP assigned in the router, and it gets assigned that IP when it first boots. After an indeterminate amount of time, its IP address and routing information will simply cease to exist. I can then assign an IP address manually through ifconfig and it will maintain that IP address indefinitely.
This is a problem with BAMT, not with the router. It's possible it's a hardware issue, but since the machine is able to keep the IP address when configured manually and works fine outside of BAMT, I'm going with Occams razor. Since my last attempts at trying to get BAMT improved met with a brick wall, vitrol and insults, I have elected to just try to solve the problem through statically assigning the IP address, but since BAMT does not maintain the /etc/networking directory (or /etc/resolv.conf) through reboots natively, I'm asking if that can be done.
Router is fine. DHCP is fine. Everything but this one BAMT machine works as far as routing and IP assignments go.
March 19, 2012, 01:16:47 PM
You can use ifconfig or iproute (not sure which one if both are enabled on BAMT because I never use it) to assign a static IP address but honestly if you got more than 1 or 2 rigs it is going to be a complete nightmare to maintain, upgrade, and troubleshoot. If your router is fucking up DHCP reservations honestly a new router seems to be a better option.
March 19, 2012, 01:16:21 PM
Let me requote the relevant bit:
So again, is there any way to have it maintain it's IP information through a reboot?
Quote
One of my machines keeps losing it's IP address. It's like the lease expires, but never renews.
So again, is there any way to have it maintain it's IP information through a reboot?
So are you saying you have already set it up static and it's not saving that info after a reboot? Sorry for the confusion, you said lease expire so I assumed DHCP with no lease.
March 19, 2012, 01:08:29 PM
Let me requote the relevant bit:
So again, is there any way to have it maintain it's IP information through a reboot?
Quote
One of my machines keeps losing it's IP address. It's like the lease expires, but never renews.
So again, is there any way to have it maintain it's IP information through a reboot?
March 19, 2012, 12:58:35 PM
One of my machines keeps losing it's IP address. It's like the lease expires, but never renews. Only happens on one machine... is there a way to assign a static IP permanently to the machine that will survive a reboot?
I believe from the desktop, not SSHed in, you can right click on the network plug icon near the clock and edit the network config. But a reservation via DHCP would be best.
March 19, 2012, 12:46:46 PM
how do i get this page, the top left image http://i.imgur.com/VoEQF.jpg to show if i am at work? i use windows.
An easy way, if your router/firewall supports it, is to port forward in on a non-standard port for example port 10001 forwarding to port 80 of the rig. Then just hit you home IP on that port. http://homeip:10001
Eagerly awaiting BAMT Pro though.
yeah, i was tired when i tried to do it and after sleeping, i realized i had the ports backwards in the forwarding boxes setup page lol. thanks.
March 19, 2012, 12:18:39 PM
One of my machines keeps losing it's IP address. It's like the lease expires, but never renews. Only happens on one machine... is there a way to assign a static IP permanently to the machine that will survive a reboot?
Assign it an IP in your router.
March 19, 2012, 11:45:52 AM
One of my machines keeps losing it's IP address. It's like the lease expires, but never renews. Only happens on one machine... is there a way to assign a static IP permanently to the machine that will survive a reboot?
March 19, 2012, 09:26:07 AM
Same way you make any web page on any private network available to the public internet.
Another option is to subscribe to BAMT Pro.
Another option is to subscribe to BAMT Pro.
Is BAMT Pro now available? Where do I sign up?
BAMT pro is available and kicks ass! Its sweet to see status of everything on my phone. Just PM lodcrappo and he'll get ya setup.
Jump to: