Open bruvv opened 2 years ago
you could get another device in the middle of them... how that will effect the NAT for p2p ... I dont know but... I have Nebra.. miner they just use those little thumb size usb dongles... you could just swap the dongle out for one that is only 2.4 ghz with no 5 ghz radio... that might work IF sense cap uses the same type of USB dongle...
Good option but again helium is for noobs and people that just buy these things and do not look back at it. So we should make it noob proof as much as possible. Explaining to everyone who want to use wifi to extra wifi stuff to it is not really a good solution in my eyes.
If you would do something like you suggest, how will the MNTD or sensecap (raspberry pi v4 based) know what hardware to use? Us the internal WIFI or the external dongle? no option to select the wifi card as far as I know.
well it seems like the ISP is your issue.. that you cant name the diffrent radios... not so much the hotspot itself..
you def will void your warranty and what not if you open the thing so I mean... Id contact sense-cap about that
I am talking about the miner/hotspot (raspberry pi based) how is THAT going to know what radio to use? (wlan0 vs WLAN1)
well you could force it to do 2.4 ghz Id look that up somewhere online or youtube on one of them maker channels... there is tons of info on the subject... I have never looked into it myself but I would look to force the 2.4 ghz radio and shut down the 5ghz radio but that will open up a can of worms. Nebra uses an OS called balena... which is a one way street... they got access to your settings but you don't got access to those settings... as you can see I went down that road... I would try and middle man it some how if you cant get your ISP to give different names for the different radios... on your router modem
*** most routers / modems have a 2 names for the diffrent radios... In the settings as you mentioned. One will be called home 2.4 and home 5 or EXT or some random name but if they named them the same like you mentioned you cant really pick cus the radio will swap from 5 to 2.4... depending on which way the wind blows... but 5 ghz typiclly less range so the further you get the more likely youll be using the 2.4 radio
I had an issue with my concentrator and the replacement didnt work with the pinout or PCB design so I had to jumper wire some things around... that was my issue... but again, the USB dongle if its a specific driver that's embedded in the sense cap firmware... aka if you swap it out it wont " plug and play" or update the firmware to the new USB dongle... then it wont work either way.. you need to put something in the middle between the router and the device that you have control of the radios... Like you said... that will get fishy with the NAT but... if you have access to that bridge device... you can then open the ports that are necessary and it should work... SHOULD ... but this p2p thing is finicky
That way you dont have to touch your miner and mess with your warranty and what not.. I think what your looking for is like in DD-WRT or openWRT might be called a repeater bridge on say the 5ghz radio ,, and an access point on the 2.ghz radio that way the 5ghz radio will be your bridge to the router... and the 2.4 ghz will have a unique name like " HM-2.4ghz" ( I would suggest keeping the network SSID = hidden) but you could leave it open at first to provision it then change it to hidden once youve established the connection... since you may not have the ability in the settings to find hidden networks..
Like I have an OLD router like super old but I flashed it with the DD-wrt and I have my IOT devices that only have 2.4 ghz radios on them connected to it like this... I get no NAT issues... ( I have other issues ) with the miner pluged into main router over ethernet..But my isp routermodem is in my room and I when im testing debuging stuff I plug it to this.. but either way the nat says none when on my debug work station...
you dont have to put it onto the channel 11 you can put it to whatever channel... or leave it auto ... just in the USA channell 11 and 12 is for long distance stuff... like if your broadcasting or chirping far away... I do alot of ESP32 IOT projects... and I have them similar to LoRa that they " Chirp" on 2.4ghz... but legally Its on channel 11 but those esp32s radios ... they got issues beyond the scope of this that they need a specific channel set to them in station mode, which then affects the AP or esp-now modes... so you could probably just leave it on auto so it picks the less noisy channel
you could also just throw it into the bridges DMZ option which is what I do for the miner hotspot when I plug it into this thing to debug.. that way all the ports are open and the only thing thats restricting your NAT is the main modem/router..
Like I mentioned in my firrst post this will not work on my ISP router and a lot of people will overlook this. This simple fix in the miner can help the network. We should not focus on how to fix it at the router end but at the miners end. please
Im still confused ... how you cant add a bridge.... if you clone the MAC address in the bridge of your ISP router... and put the SSID and PW of your ISP router... into the bridge... its going to act like your ISP router... I dont have access to a sense cap so I cant tell you how it is inside of there... or what OS its running, and what access you have to the hotspot miner itself... my nebra uses balenaOS and it works over A Bluetooth setup GUI which Scans the wifi networks and you can pick it like on your phone or whatever and type your password in over the bluetooth connection. I personally took the wifi usb dongle out first thing I did... just cus I dont need anyone that has access to the miner ( bad actors) to have that available to them. everything worked fine without it plugged in, and with ethernet plugged into the main router. Now can a " bad actor" still do things well yes... but atleast I can blame it on Comcast and not nebra or helium... but as far as what sort of access sense cap gives you to your hotspot miner. is what youll be able to do. The balenaOS on nebra automaticlly cleans out all the config files everytime it loads and puts it back to " stock" so even if you make a change in the config.txt it resets it to " stock " there are other files which can be modified within the balenaOS which is a json,config file which doesnt change on every reload, but most probably does on every firmware upgrade... that being said you got to figure out what OS that thing is using..BalenaOS is just running the debian arm64 linux kernel.. So the config.txt is the same as the raspiOS config.txt... So you would probably need to change some sort of DTOVERLAY or DTPARAM for the WIFI... OR figure out the EBUS... but now your getting into some stuff that is beyond clicking a drop down menu and selecting 2.4 or 5ghz...and alot of this miners manufacturers arent going to implment a fleet wide change for 1 hotspot... like I say maybe if you talk to the people at sense cap themselves... maybe they can change that setting for you remotely... IF they have the time...
Like vanjulio said its just better to leave it alone and not mess with the miner what so ever. that way you have a unmodified miner, that will cause you a slew of headaches.. then when you go to ask sense cap for help on another issue.. they going to blame it on that modification and not warranty or help you. leave the miner alone, and figure out how to get a secondary bridge to work.. Like I said for my IOT projects not concerning Helum... I use an OLD router that you can probably find in your attic somewhere or just buy one from where ever for less then 20 bucks... flash it with an openWRT or DD-WRT style firmware so that you can have full control of the bridge and its settings... That way you can do things that the " stock firmware" on the bridge router doesnt allow you to. the ISP unless your ISP is like one of those " Captive Portal" hotspot kind of things... then your going to need to " hack" that captive portal with some sort of scripting that puts your user name and password everytime it boots you off automatically
like if it is a captive portal kind of ISP that you have to log into the web browser everytime you connect to it with user name and password... the easiest route for that is to have something with a web browser on it like your Phone or a spare phone tablet .. that you can type your credientials in and then on the phone device etc... youd have to set up " network sharing " or set the phone tablet as a " hotspot" but I read some other posts that say those captive portal style ISP like say in a DORM room or something like that... probably wont have that port 44158 open anyways... so youll be in that "relayed " state
Again I am not going to change anything on my side. it is a temporary house and nothing in this house is mine. I am not going to add anything to the network since it isn't mine. I want to change just a simple setting in the bare bones of the miner. And yes using a hotspot from my phone can be an option. But again a lot of people might not be awair that their miner is doing this. So it should be fixed. And this is the bug report for it. Stop asking about my situation and start thinking about all the miners out there in this situation where you will never be able to tell the owner what you are telling me here.
Of course you should not leave the miner alone, if there is room for improvement on the miner it should be improved. this is an improvement in my eyes. So I would say we should change it....
I don't think that's " sense cap" specific. Most wireless devices that have the dual radios will do that automatically. but that's because the device is in a " zone" of the house that the 5ghz barely reaches and the device is looking for the available signal based on its signal strength. my Laptop , my raspberry pis , even my TV does that automatically. There are settings for that ... I have had this issue on other devices. But besides the settings that you cant change from the ISP end like setting up the radios with different names. Or on the miner that you cant " forget this network" type of option so it doesn't keep swapping out. I had a buddy with an android phone that would do that non stop and he couldn't figure it out . let me see if he figured that out, maybe hes got a " name" for the issue...
random, but maybe an option.. Does the ISP have 2 different MAC addresses for the different radios? cus that might be a way to set the miners wifi settings to that specific radio, if there is an " advanced network" setting in the miners wifi settings... you might be able to specify which MAC it connects to...
Please stop posting double and use the edit button. Again it is a rental house I am not going to do anything to the wifi. All the miners that are helium approved and have wifi on board should use 2.4 ghz this will fix stuff out of the box for the millions of people that have helium enabled wifi hotspots.
Please stop asking stuff about my ISP. That is not what this is about.
well like the people at nebra told me... your on your own.
"You're" And thanks for helping
https://pimylifeup.com/raspberry-pi-mac-address-spoofing/ ** https://forums.balena.io/t/restrict-rpi-4-to-2-4ghz/65300/20
The MAC clone if your going to do it on your miner, DO NOT DO IT ON THE ETH0 WHICH IS TIED TO YOUR MINERS ON BOARDING KEY (might cause issues) make sure its just on the w0 address... but the clone thing is to use another raspberry pi as a brdige... if you want to make yourself a personal router hotspot for your devices in the rental property or on trips etc.. https://www.youtube.com/watch?v=jlHWnKVpygw ... as far as VPN helium and Deeper Network have a partnership, SO you might want to look into that for extra earnings..
This is a manufacturer specific issue, not an issue with Helium or Helium manufactured/supported hardware, please take it elsewhere.
So you're saying RAK miners are not "Helium manufactured/supported hardware" ??? I"m confused. It is a HUGE F*N issue. We are writing all these problems and telling you we wasted HOURS and DAYS of our time troubleshooting black box failures. My recommendation remains to remove the wifi capability from these because it does not work sufficiently. I am fine with closing the issue but I think it is not so fair to dismiss and say "not our problem".
This is a network device and completely fails on the common network interface most people use (WIFI). Is that not important? This is adding instability to 1000s of devices. I think the dream is that you get so much redundancy from many units. but for optimal behavior you will have to do another HIP to force people to stop using WIFI some day.
Im just trying to help someone out I have no affiliation with anyone or anything, In hopes not to waste the DEVS TIME so they can actually focus on fixing thier network issues.
If there's a problem with Helium supported hardware, sure we can look into that, the problem is when other manufacturers, with very different system images, get into the mix it confuses the issue and helps nobody.
Indeed this whole ticket went south quickly. This is about the miner software provided by helium where it should lock all the wifi miners to 2.4 ghz. Is that doable? thanks @vanjulio you just perfectly explainted what I wanted to say.
Turn off wifi steering on the router and it will stay on the 2.4GHz that you connected it to.
@just-jase if you did not read the ticket then please do not comment something that's been said and answered already.
I have been struggling with sensecap and MNTD miners (both raspberry pi v4 based) at my home. After A LOT of debugging (and that is hard when you cannot access the miner in anyway to know what is going on :( ) after moving it to a friends house I found out that it is switching between 5ghz and 2.4 ghz every few minutes:
Yes I know what can be done to overcome this:
In my opinion 5GHz will not improve anything for the miner. Since the miners that I know do not have an external antenna having a very stable connection with internet is very important for the whole blockchain. So locking it to 2.4 GHz will be very smart thing to do.
My solution:
Using a raspberry pi doing this will do just that: Modify
/mnt/boot/system-connections
to:band=bg