I have an AWS IOT button that i'm trying to connect to the open wifi at my office. The problem is, our open "no-auth" wifi has one of those "terms of use" buttons you have to click in a browser before you are connected. Can the AWS IOT button get passed that?
Seems like it only works on wifi that is locked down vie SSA.
Anyone know a workaround?
Unfortunately the button doesn't support captive portal networks.
Normally we advise the network operator to whitelist the button's MAC
address, but I see you've already ruled that out.
One option you have is to use a travel router to bridge the captive
portal network to a non-captive portal network. These travel routers
are typically designed for hotel use, and so handle captive portal
networks well. You'll probably have to first connect to the
non-captive network with a phone or laptop to click agree, but then
all other devices on the network shouldn't see the login page
afterwards.
Note that this may be seen as circumventing the captive portal
network's usage or security policies, so please check with the network
operator.
https://forums.aws.amazon.com/thread.jspa?threadID=244348
discover the device's mac address
remove the device's power source
configure your laptop's wifi card to override its built-in MAC address and instead assume the IoT device's MAC address
sign on to the wireless network and accept terms with your laptop, spoofing the device's hardware address
return the laptop to normal configuration
power up the IoT device
PROFIT! :) ...at least until the portal's login timeout window expires.
Related
We have a fluid monitoring physical device(hardware with camera, PCB board, LED lights etc). This hardware is connected to computer via USB cable. It captures images and these images are processed in C++ software on PC. As a security feature, we have already implemented node authentication using cryptoauthentication chips like ATECC608A. More information below.
I wanted to know if there were some other methods which I can use to improve the security further.
I want to make sure that the device will only work with the laptop/PC which we provide.
Already implemented: The PCB board has ATECCX608a cryptoauthentication chip. we store our ssl certificate and verify the certificate chain
and also do random nonce challenge for device authentication. More on this please refer to the link below
https://www.digikey.com/eewiki/display/Motley/ATECC508A+Node+Authentication+Example+Walk-through
This sounds to me like you want mutual authentication. You want the PC to authenticate the USB device, but you want the USB device to authenticate the PC as well. So construct the SSL handshake you are already using to perform a mutual (client) authentication and make sure everyone has certs from the same CA (likely you)
I am setting up my AWS DeepLens and all the steps have been successful until I try to connect to my home WiFi. How do I fix this issue?
I created a hotspot on my phone to test against a different network and this connection was successful. Then, I switched back to my home WiFi and it connected successfully.
This section of the troubleshooting guide will also fix the problem.
We found that the AWS DeepLens only has one network adapter which it uses both for its own hotspot and connecting to the network. If you are connected to it via any other means (e.g. via a phone) it will throw a hissy and start dropping the connection, repeatedly and seemingly randomly.
When we connected a monitor directly we then found it was stuck on a viewable password prompt, hence why it was not connecting to our network.
Best method by far (and from our experience, only usable option) is to connect directly to the device so you can see what it is doing. To do this you need USB keyboard and mouse, and a mini-HDMI to HDMI cable to hook up a monitor. This will free up the network card to do only one thing.
When connecting please note that the default admin password on ours was "aws_cam". This does not seem to be noted anywhere in the documentation. This will change when you go through the setup process and sync it with your AWS account.
Repeat the process by inserting a pin in the hole at the back of DeepLens. Wait for a few seconds, the wifi indicator (the middle light) would blink and then you can connect with Deeplens wireless network. Then you can open http://deeplens.config where you can configure your home wifi and complete the setup.
I am trying to find out the amazon IoT button's mac address to connect it with my working place network. But I do not know the process about how to get it. Could somebody give me the instruction or any helpful link about this matter? Thanks in advance.
Okay, it was actually not a difficult task. At first, I need to connect to a network. When it will be connected, my Netgear wifi router is showing me that it is connected to the network. And from the router, it is easy to get the mac address for my button.
Does anyone know how to remove a WiFi network from Google Glass? My WiFi at work wants you to consent to a privacy policy which Glass can not accept so I don't get a data connection. When I tether it to my phone, it keeps reverting back to the work WiFi network. Any suggestions?
There's a few things you can try.
1) Go to Glass ->> Settings -> Wifi -> Forget.
2) In the My Glass app, pair your device, select Wi-Fi, select the network you want to use.
3) Good Old Factory reset.
Also, as per a commenter above - this Doesn't belong here at all.
For questions such as this, your best bet is to contact one of the Glass Guides, either by email or phone. They can talk you through the process or help with any other problems you may have. Make sure you have your ID ready (the one they sent you as part of the invite).
I want to access Internet from my BB10 simulator.
I have changed the setting of the virtual machine and changed the Network Connection type from NAT to Bridged.
But after this when I restarted the simulator, it is unable to get the IP address. Thus QNX IDE is unable to discover it.
Please suggest how can I resolve this issue ?
According to an administrator on the blackberry forums you can do the following:
http://supportforums.blackberry.com/t5/Cascades-Development/BB10-Dev-Alpha-Simulator-not-connecting-to-WiFi/td-p/1842579
1) Power down your VM
2) In VMWare select your VM and then click "Edit Virtual Machine Settings"
3) Select Network Adapter
4) Change from NAT to Bridge mode, which will allow the simulator to have direct access your physical network card.
5) Start the simulator again.
In case this is still an issue for you or anyone else; If I understand correctly, when you switch to bridged connection, you do have internet access on your simulator, but the QNX IDE does not find it via device discovery.
I just had the same problem, it can be solved by typing the simulator IP in by hand. Note that you have to use the address that VMWare displays at the very bottom of the content window, not the IP that is set in Development Settings.
I suspect the QNX IDE of only scanning a certain IP range for target devices. Thus, when you switch to bridged mode and your device obtains an arbitrary address in your LAN, it does not (necessarily) fall in that range.