Hello !
Trace: • Challenges of Autonomous Cars • Tarkvara allalaadimine

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:iot-open:remotelab:sut:generalpurpose2:u2 [2019/08/08 18:36] – gdrabiken:iot-open:remotelab:sut:generalpurpose2:u2 [2020/07/20 09:00] (current) – external edit 127.0.0.1
Line 5: Line 5:
  
 === Prerequisites === === Prerequisites ===
-You need to know how to handle 4×20 characters LCD screen. In case of doubt re-work on scenarios B1 and B2.\\ <fc #ff0000>Warning: In no case should you give your AP the internal.IOT SSID name! You will mess up the laboratory environment and block other users from accessing network infrastructure. We consider this behaviour as hacking and it will be penalized under legal jurisdiction!</fc> +You need to know how to handle 4×20 characters LCD screen. In case of doubt re-work on scenarios B1 and B2.\\ <fc #ff0000>Warning: In no case should you give your AP the ''internal.IOT'' SSID name! You will mess up the laboratory environment and block other users from accessing network infrastructure. We consider this behaviour as hacking and it will be penalized under legal jurisdiction!</fc> 
-<note warning>In no case give your AP the internal.IOT SSID! You will mess up the laboratory environment and block other users from accessing network infrastructure. We consider this behaviour as hacking and it will be penalized under legal jurisdiction!</note>+<note warning>In no case give your AP the ''internal.IOT'' SSID! You will mess up the laboratory environment and block other users from accessing network infrastructure. We consider this behaviour as hacking and it will be penalized under legal jurisdiction!</note>
 To fully experience this scenario, you need to book another node (one of 1,2,3 or 4), to let the other node act as your networking client. You can use scenario U1 for this purpose but mind to update network SSID and passphrase in your code, to let it connect to your server. <note tip>Students physically present in the SUT IoT laboratory room 320 may use their own devices like laptops or mobile phones to connect to your AP.</note> To fully experience this scenario, you need to book another node (one of 1,2,3 or 4), to let the other node act as your networking client. You can use scenario U1 for this purpose but mind to update network SSID and passphrase in your code, to let it connect to your server. <note tip>Students physically present in the SUT IoT laboratory room 320 may use their own devices like laptops or mobile phones to connect to your AP.</note>
  
Line 31: Line 31:
 Give it some definitions as identifiers for cleaner code, remember to change ssid name to yours! Give it some definitions as identifiers for cleaner code, remember to change ssid name to yours!
 <code c> <code c>
-#define wifi_ssid_ap put_your_unique_id_here //give it some unique name - change here!!+#define wifi_ssid_ap put_your_unique_id_here //give it some unique name-change here
 #define wifi_password_ap "1234567890" #define wifi_password_ap "1234567890"
 </code> </code>
-<note warning>Never use ''internal.IOT'' as your SSID name ''wifi_ssid_ap '' - you will overlap existing network infrastructure and we consider it as hacking that is subject to jurisdiction! Your account will be imediatelly banned!</note>+<note warning>Never use ''internal.IOT'' as your SSID name ''wifi_ssid_ap'' - you will overlap existing network infrastructure and we consider it as hacking that is subject to jurisdiction! Your account will be imediatelly banned!</note>
  
 == Step 3 == == Step 3 ==
en/iot-open/remotelab/sut/generalpurpose2/u2.1565289409.txt.gz · Last modified: 2020/07/20 09:00 (external edit)
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0