https://elvis.hcw.ac.at/wiki/api.php?action=feedcontributions&feedformat=atom&user=StSchmitzhofer 2026-09-10T20:18:01Z User contributions MediaWiki 1.41.5 https://elvis.hcw.ac.at/wiki/index.php?title=Buffer_Overflows&diff=2629 2020-01-28T23:53:17Z

<p>StSchmitzhofer: Countermeasures and References Update</p> <hr /> <div>== Summary == <br /> <br /> Since the rise of C in the early 1970s, buffer overflows have become a serious security vulnerability. Even though high-level programming languages are typically not affected, the number of vulnerable systems is actually rising.<br /> <br /> At the same time, a wide array of countermeasures are also increasingly adopted and applied. Features like executable space protection (e.g. Data Execution Prevention under Windows) already deployed since the mid 2000s, and on the compiler side, technologies like Stackguard support several detection and prevention mechanisms (e.g. different types of Canaries). Furthermore, almost every wider used operation system supports Address Space Layout Randomization, in order to minimize the attack surface for buffer overflow attacks. For example, at the beginning of 2020 most of the bigger operating systems (Linux, Windows, macOS, iOS, Android, Solaris, OpenBSD, etc.) offer support for ASLR.<br /> <br /> == Requirements ==<br /> <br /> * Operating system: not limited<br /> * A vulnerable library (or function), within any attacked binary<br /> <br /> == Description ==<br /> <br /> A buffer overflow occurs when there is more information written to a data region, than it can hold. For example in C, allowing user input directly to be written to a character array with a size of ten bytes. If in this case, the user enters more than ten characters, and furthermore the program attempts to insert said data into the smaller array, an overflow occurs.<br /> <br /> === Basic Vulnerability ===<br /> <br /> #include &lt;string.h&gt;<br /> <br /> int main(int argc, char *argv[]) {<br /> char buffer[6];<br /> strcpy(buffer, argv[1]); <br /> return 0;<br /> }<br /> <br /> In this example an argument passed to this executable (e.g. the binary compiled from this source), with more than 6 characters, will typically overflow the buffer. However, the exact input size necessary to affect the program flow might be different (bigger), and will be a multiple of 4 characters (for 32 bit binaries).<br /> <br /> These types of vulnerabilities can be taken advantage of in several different ways. For example most prominently, ROP attacks (return-oriented programming), targets the return address of a binary. By rewriting the return address, it aims at influencing the control flow of a program. Which can still be viable, when controlling security features, like executable-space protection, are inplace. Therefore, the attacker uses gadgets (small instruction sequences) which are already available within the binary, and manipulates their return location, and theirby does not directly need to inject executable instructions (which might be thwarted by the OS), but rather use these compiled resources (gadgets).<br /> <br /> == Countermeasures ==<br /> <br /> === Canaries ===<br /> Canaries can be employed, in order to recognize whether a buffer overflow occurred. Therefore, in the simplest cases, Canaries are specific values in memory, which are located right after the thereby protected buffer. If their values are changed at any point, it is safe to assume that a buffer overflow occurred and countermeasures (e.g. termination) can be taken. Typical types of Canaries, which are supported by security hardening technologies like ProPolice or Stackguard (GCC), are Terminator Canaries, Random Canaries, and Random XOR Canaries.<br /> <br /> === Data Execution Prevention (DEP) ===<br /> Data Execution Prevention (DEP) is a security feature, originally developed by MicrosoftR© for Windows XP SP2. There are two basic variants, hardware-based DEP and software-based DEP. If supported by the CPU as well as process, hardware DEP will be employed, otherwise DEP has to be carried out in software, which is part of the Windows operating system. The basic functionality of DEP is to prevent applications from executing code in a non-executable area of the memory.<br /> <br /> === Address Space Layout Randomization (ASLR) ===<br /> Since code reuse attacks (e.g. ROP attack) require the memory addresses of gadgets to be known to an attacker, techniques to randomize their entry points have become increasingly popular. ASLR randomizes the location of data and code regions offers a plausible defensive strategy, (since) code region layout randomization hinders code reuse in exploits and data randomization impedes the redirection of control-flow by making it difficult to guess the location of injected code (partly paraphrased from the 2013 paper by Snow et al.).<br /> <br /> == Courses ==<br /> <br /> * [[Ausgewählte Kapitel der IT-Security SE]] (2019, 2020)<br /> <br /> == References ==<br /> <br /> * [http://phrack.org/issues/49/14.html Smashing the stack for fun and profit (1996, Aleph One)]<br /> * [https://doi.org/10.1109/SP.2013.45 Just-In-Time Code Reuse: On the Effectiveness of Fine-Grained Address Space Layout Randomization (2013, Snow et al.)]<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=Buffer_Overflows&diff=2628 2020-01-28T23:32:26Z

<p>StSchmitzhofer: Description and Example</p> <hr /> <div>== Summary == <br /> <br /> Since the rise of C in the early 1970s, buffer overflows have become a serious security vulnerability. Even though high-level programming languages are typically not affected, the number of vulnerable systems is actually rising.<br /> <br /> At the same time, a wide array of countermeasures are also increasingly adopted and applied. Features like executable space protection (e.g. Data Execution Prevention under Windows) already deployed since the mid 2000s, and on the compiler side, technologies like Stackguard support several detection and prevention mechanisms (e.g. different types of Canaries). Furthermore, almost every wider used operation system supports Address Space Layout Randomization, in order to minimize the attack surface for buffer overflow attacks. For example, at the beginning of 2020 most of the bigger operating systems (Linux, Windows, macOS, iOS, Android, Solaris, OpenBSD, etc.) offer support for ASLR.<br /> <br /> == Requirements ==<br /> <br /> * Operating system: not limited<br /> * A vulnerable library (or function), within any attacked binary<br /> <br /> == Description ==<br /> <br /> A buffer overflow occurs when there is more information written to a data region, than it can hold. For example in C, allowing user input directly to be written to a character array with a size of ten bytes. If in this case, the user enters more than ten characters, and furthermore the program attempts to insert said data into the smaller array, an overflow occurs.<br /> <br /> === Basic Vulnerability ===<br /> <br /> #include &lt;string.h&gt;<br /> <br /> int main(int argc, char *argv[]) {<br /> char buffer[6];<br /> strcpy(buffer, argv[1]); <br /> return 0;<br /> }<br /> <br /> In this example an argument passed to this executable (e.g. the binary compiled from this source), with more than 6 characters, will typically overflow the buffer. However, the exact input size necessary to affect the program flow might be different (bigger), and will be a multiple of 4 characters (for 32 bit binaries).<br /> <br /> These types of vulnerabilities can be taken advantage of in several different ways. For example most prominently, ROP attacks (return-oriented programming), targets the return address of a binary. By rewriting the return address, it aims at influencing the control flow of a program. Which can still be viable, when controlling security features, like executable-space protection, are inplace. Therefore, the attacker uses gadgets (small instruction sequences) which are already available within the binary, and manipulates their return location, and theirby does not directly need to inject executable instructions (which might be thwarted by the OS), but rather use these compiled resources (gadgets).<br /> <br /> == Courses ==<br /> <br /> * [[Ausgewählte Kapitel der IT-Security SE]] (2019, 2020)<br /> <br /> == References ==<br /> <br /> * http://phrack.org/issues/49/14.html<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=Buffer_Overflows&diff=2511 2020-01-21T22:01:42Z

<p>StSchmitzhofer: Summary improveed</p> <hr /> <div>== Summary == <br /> <br /> Since the rise of C in the early 1970s, buffer overflows have become a serious security vulnerability. Even though high-level programming languages are typically not affected, the number of vulnerable systems is actually rising.<br /> <br /> On the other hand, a wide array of countermeasures are also increasingly adopted and applied. Features like executable space protection (e.g. Data Execution Prevention under Windows) already deployed since the mid 2000s, and on the compiler side, technologies like Stackguard support several detection and prevention mechanisms (e.g. different types of Canaries). Furthermore, almost every wider used operation system supports Address Space Layout Randomization, in order to minimize the attack surface for buffer overflow attacks. For example, at the beginning of 2020 from all the bigger names (Linux, Windows, macOS, iOS, Android, Solaris, OpenBSD, etc.), only FreeBSD does not offer support for ASLR. Nonetheless, it is announced to be supported in version 13.0, which is currently in development.<br /> <br /> == Requirements ==<br /> <br /> * Operating system: not limited<br /> * One vulnerable library (or function), available within the attacked binary<br /> <br /> <br /> <br /> == Description ==<br /> <br /> === Step 1 ===<br /> <br /> (Enter these commands in the shell)<br /> <br /> echo foo<br /> echo bar<br /> <br /> === Step 2 ===<br /> <br /> Make sure to read<br /> <br /> * War and Peace<br /> * Lord of the Rings<br /> * The Baroque Cycle<br /> <br /> == Courses ==<br /> <br /> * [[Ausgewählte Kapitel der IT-Security SE]] (2019, 2020)<br /> <br /> == References ==<br /> <br /> * https://wikipedia.org<br /> * https://google.com<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=Buffer_Overflows&diff=2510 2020-01-21T20:05:04Z

<p>StSchmitzhofer: Summary and basic headings</p> <hr /> <div>== Summary == <br /> <br /> Since the rise of C in the early 1970s, buffer overflows have become a serious security vulnerability. Even though high-level programming languages are typically not affected, especially with the increasing significance and use of IoT devices, the number vulnerable systems is actually on the rise.<br /> <br /> On the other hand, a wide array of countermeasures are also increasingly adopted and applied. Features like executable space protection (e.g. Data Execution Prevention under Windows) already deployed since the mid 2000s, and on the compiler side, technologies like Stackguard support several detection and prevention mechanisms (e.g. different types of Canaries). Furthermore, almost every wider used operation system supports Address Space Layout Randomization, in order to minimize the attack surface for buffer overflow attacks. For example, at the beginning of 2020 from all the bigger names (Linux, Windows, macOS, iOS, Android, Solaris, OpenBSD, etc.), only FreeBSD does not offer support for ASLR. Nonetheless, it is announced to be supported in version 13.0, which is currently in development.<br /> <br /> == Requirements ==<br /> <br /> * Operating system: not limited<br /> * One vulnerable library (or function), available within the attacked binary<br /> <br /> <br /> <br /> == Description ==<br /> <br /> === Step 1 ===<br /> <br /> (Enter these commands in the shell)<br /> <br /> echo foo<br /> echo bar<br /> <br /> === Step 2 ===<br /> <br /> Make sure to read<br /> <br /> * War and Peace<br /> * Lord of the Rings<br /> * The Baroque Cycle<br /> <br /> == Courses ==<br /> <br /> * [[Ausgewählte Kapitel der IT-Security SE]] (2019, 2020)<br /> <br /> == References ==<br /> <br /> * https://wikipedia.org<br /> * https://google.com<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=R2D2_Bluetooth_Robot:_Basic_Setup&diff=2098 2019-09-27T21:52:14Z

<p>StSchmitzhofer: Additional setup picture</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to connect to the [[R2D2 Bluetooth Robot|R2D2 Robot]]<br /> <br /> == Requirements ==<br /> <br /> * Operating system: Android 5.0 or later / iOS 9.0 or later<br /> * Hardware: [[R2D2 Bluetooth Robot|R2D2 Robot]], Micro USB Charger<br /> <br /> == Description ==<br /> [[File:R2d2robotAppPreconnect.png|200px|thumb|Connecting]]<br /> [[File:R2d2robot app connect.png|200px|thumb|Bluetooth scan results]]<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> Plug the micro usb cable into the [[R2D2 Bluetooth Robot|robot]] to charge it, and awaken it's bluetooth force.<br /> <br /> === Step 2: App Setup ===<br /> <br /> Install the ''Star Wars Droid App'', depending on your device choose:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars (Android) Star Wars Droids App]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 (iOS) Star Wars Droids App]<br /> <br /> === Step 3: Connecting ===<br /> <br /> * Enable bluetooth on your phone<br /> * Launch the ''Star Wars Droids App''<br /> * After the intro clip, click on &quot;connect&quot;<br /> * Once the scan is complete, click on the R2-D2, and confirm it<br /> <br /> The droid is now controllable via your smartphone.<br /> <br /> == Used Hardware ==<br /> <br /> [[R2D2 Bluetooth Robot]]<br /> <br /> == References ==<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars https://play.google.com/store/apps/details?id=com.sphero.starwars]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524]<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:R2d2robotAppPreconnect.png&diff=2097 2019-09-27T21:50:10Z

<p>StSchmitzhofer: </p> <hr /> <div></div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=R2D2_Bluetooth_Robot:_Basic_Setup&diff=2096 2019-09-27T21:09:47Z

<p>StSchmitzhofer: (Formatting) Moved screenshot up</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to connect to the [[R2D2 Bluetooth Robot|R2D2 Robot]]<br /> <br /> == Requirements ==<br /> <br /> * Operating system: Android 5.0 or later / iOS 9.0 or later<br /> * Hardware: [[R2D2 Bluetooth Robot|R2D2 Robot]], Micro USB Charger<br /> <br /> == Description ==<br /> [[File:R2d2robot app connect.png|200px|thumb|Bluetooth scan results]]<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> Plug the micro usb cable into the [[R2D2 Bluetooth Robot|robot]] to charge it, and awaken it's bluetooth force.<br /> <br /> === Step 2: App Setup ===<br /> <br /> Install the ''Star Wars Droid App'', depending on your device choose:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars (Android) Star Wars Droids App]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 (iOS) Star Wars Droids App]<br /> <br /> === Step 3: Connecting ===<br /> <br /> * Enable bluetooth on your phone<br /> * Launch the ''Star Wars Droids App''<br /> * After the intro clip, click on &quot;connect&quot;<br /> * Once the scan is complete, click on the R2-D2, and confirm it<br /> <br /> The droid is now controllable via your smartphone.<br /> <br /> == Used Hardware ==<br /> <br /> [[R2D2 Bluetooth Robot]]<br /> <br /> == References ==<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars https://play.google.com/store/apps/details?id=com.sphero.starwars]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524]<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=R2D2_Bluetooth_Robot:_Basic_Setup&diff=2095 2019-09-27T21:08:42Z

<p>StSchmitzhofer: Added &quot;References&quot; link text</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to connect to the [[R2D2 Bluetooth Robot|R2D2 Robot]]<br /> <br /> == Requirements ==<br /> <br /> * Operating system: Android 5.0 or later / iOS 9.0 or later<br /> * Hardware: [[R2D2 Bluetooth Robot|R2D2 Robot]], Micro USB Charger<br /> <br /> == Description ==<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> Plug the micro usb cable into the [[R2D2 Bluetooth Robot|robot]] to charge it, and awaken it's bluetooth force.<br /> <br /> [[File:R2d2robot app connect.png|200px|thumb|Bluetooth scan results]]<br /> === Step 2: App Setup ===<br /> <br /> Install the ''Star Wars Droid App'', depending on your device choose:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars (Android) Star Wars Droids App]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 (iOS) Star Wars Droids App]<br /> <br /> === Step 3: Connecting ===<br /> <br /> * Enable bluetooth on your phone<br /> * Launch the ''Star Wars Droids App''<br /> * After the intro clip, click on &quot;connect&quot;<br /> * Once the scan is complete, click on the R2-D2, and confirm it<br /> <br /> The droid is now controllable via your smartphone.<br /> <br /> <br /> == Used Hardware ==<br /> <br /> [[R2D2 Bluetooth Robot]]<br /> <br /> == References ==<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars https://play.google.com/store/apps/details?id=com.sphero.starwars]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524]<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=R2D2_Bluetooth_Robot:_Basic_Setup&diff=2094 2019-09-27T21:07:37Z

<p>StSchmitzhofer: Corrected heading level</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to connect to the [[R2D2 Bluetooth Robot|R2D2 Robot]]<br /> <br /> == Requirements ==<br /> <br /> * Operating system: Android 5.0 or later / iOS 9.0 or later<br /> * Hardware: [[R2D2 Bluetooth Robot|R2D2 Robot]], Micro USB Charger<br /> <br /> == Description ==<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> Plug the micro usb cable into the [[R2D2 Bluetooth Robot|robot]] to charge it, and awaken it's bluetooth force.<br /> <br /> [[File:R2d2robot app connect.png|200px|thumb|Bluetooth scan results]]<br /> === Step 2: App Setup ===<br /> <br /> Install the ''Star Wars Droid App'', depending on your device choose:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars (Android) Star Wars Droids App]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 (iOS) Star Wars Droids App]<br /> <br /> === Step 3: Connecting ===<br /> <br /> * Enable bluetooth on your phone<br /> * Launch the ''Star Wars Droids App''<br /> * After the intro clip, click on &quot;connect&quot;<br /> * Once the scan is complete, click on the R2-D2, and confirm it<br /> <br /> The droid is now controllable via your smartphone.<br /> <br /> <br /> == Used Hardware ==<br /> <br /> [[R2D2 Bluetooth Robot]]<br /> <br /> == References ==<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524]<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=R2D2_Bluetooth_Robot:_Basic_Setup&diff=2093 2019-09-27T21:07:06Z

<p>StSchmitzhofer: Created this setup documentation</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to connect to the [[R2D2 Bluetooth Robot|R2D2 Robot]]<br /> <br /> == Requirements ==<br /> <br /> * Operating system: Android 5.0 or later / iOS 9.0 or later<br /> * Hardware: [[R2D2 Bluetooth Robot|R2D2 Robot]], Micro USB Charger<br /> <br /> == Description ==<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> Plug the micro usb cable into the [[R2D2 Bluetooth Robot|robot]] to charge it, and awaken it's bluetooth force.<br /> <br /> [[File:R2d2robot app connect.png|200px|thumb|Bluetooth scan results]]<br /> === Step 2: App Setup ===<br /> <br /> Install the ''Star Wars Droid App'', depending on your device choose:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars (Android) Star Wars Droids App]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524 (iOS) Star Wars Droids App]<br /> <br /> == Step 3: Connecting ==<br /> <br /> * Enable bluetooth on your phone<br /> * Launch the ''Star Wars Droids App''<br /> * After the intro clip, click on &quot;connect&quot;<br /> * Once the scan is complete, click on the R2-D2, and confirm it<br /> <br /> The droid is now controllable via your smartphone.<br /> <br /> <br /> == Used Hardware ==<br /> <br /> [[R2D2 Bluetooth Robot]]<br /> <br /> == References ==<br /> <br /> * [https://play.google.com/store/apps/details?id=com.sphero.starwars]<br /> * [https://apps.apple.com/us/app/star-wars-droids-app-by-sphero/id1243140524]<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:R2d2robot_app_connect.png&diff=2092 2019-09-27T20:22:10Z

<p>StSchmitzhofer: </p> <hr /> <div></div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=Proxmark3:_Installation&diff=2091 2019-09-27T19:18:34Z

<p>StSchmitzhofer: Added Proxmark Kit Link (to also auto-link this documentation there)</p> <hr /> <div>== Summary == <br /> <br /> Installation of [[Proxmark3 RDV2 Kit|Proxmark3]] on macOS, Linux and Windows for RFID and NFC sniffing.<br /> <br /> == MacOS installation ==<br /> <br /> === Requirements ===<br /> <br /> Xcode (AppStore) is a must.<br /> <br /> In addition to make the installation easier have either HomeBrew or MacPorts ready.<br /> A Tutorial for installing:<br /> A) HomeBrew: https://docs.brew.sh/Installation<br /> B) MacPorts: https://www.macports.org/install.php<br /> <br /> Because of their different architecture (HomeBrew/MacPorts), some parts of this tutorial are split into:<br /> A) Installation with HomeBrew<br /> B) Installation with MacPorts<br /> Just choose the tutorial that suits your current setup.<br /> <br /> === Installation with HomeBrew ===<br /> <br /> 1. Download (&quot;tap&quot;) the proxmark repository:<br /> <br /> brew tap proxmark/proxmark3<br /> <br /> 2. Install proxmark3:<br /> <br /> brew install proxmark3<br /> <br /> === Manual Installation ===<br /> <br /> Download the drivers and install them.<br /> If you have MacPorts:<br /> <br /> sudo port install p7zip readline libusb libusb-compat perl5 wget qt5\\ arm-none-eabi-gcc pkgconfig<br /> <br /> If you have HomeBrew:<br /> <br /> brew tap nitsky/stm32<br /> brew install readline libusb p7zip libusb-compat wget qt5 pkgconfig\\ arm-none-eabi-gcc<br /> <br /> Now you will need to add QT to the PKG_CONFIG_PATH so it find QT5 (replace YOUR_VERSION with your version number:<br /> <br /> export\\ PKG_CONFIG_PATH=/usr/local/Cellar/qt5/&lt;&lt;YOUR_VERSION&gt;&gt;/lib/pkgconfig/<br /> <br /> 3. And add moc_location in Qt5Core.pc file:<br /> <br /> export QT_PKG_CONFIG_QT5CORE=$(find /usr -name Qt5Core.pc 2&gt;/dev/null)<br /> chmod 666 $QT_PKG_CONFIG_QT5CORE<br /> echo &quot;moc_location=\${prefix}/bin/moc&quot; &gt;&gt; $QT_PKG_CONFIG_QT5CORE<br /> chmod 444 $QT_PKG_CONFIG_QT5CORE<br /> <br /> 4. For link creation to avoid any errors of &quot;readline&quot; (may happen):<br /> <br /> brew link --force readline<br /> <br /> 5. Now either git clone or manually download the Proxmark project. Git clone:<br /> <br /> git clone https://github.com/Proxmark/proxmark3.git<br /> <br /> 6. &quot;cd&quot; to the proxmark3 folder<br /> <br /> 7. Now jump to the section &quot;Connecting your Proxmark&quot;<br /> <br /> === Connecting your Proxmark ===<br /> <br /> 1. Insert your Proxmark and run<br /> <br /> system_profiler SPUSBDataType<br /> <br /> 2.a) If your Proxmark is CDC you should somewhere see in the output:<br /> <br /> Product ID: 0x504d<br /> Vendor ID: 0x2d2d<br /> <br /> 2.b) If your Proxmark is an HID device you should see:<br /> <br /> Product ID: 0x4b8f<br /> Vendor ID: 0x9ac4<br /> <br /> If it is an HID Device you will need to upgrade it, then go to &quot;Upgrading my Proxmark HID-&gt;CDC&quot;<br /> If you have an CDC Proxmark you can jump to &quot;Finish Line&quot;<br /> <br /> === Upgrading my Proxmark HID-&gt;CDC ===<br /> <br /> 1. Compile the bootrom, OS and software:<br /> <br /> make clean; make<br /> <br /> 2. Also compile the HID compatible flash program:<br /> <br /> cd client/hid-flasher;make<br /> <br /> 3. Disconnect Apple's HID driver, by installing a dummy kernel driver:<br /> <br /> sudo make install_kext<br /> sudo kextcache -system-caches<br /> <br /> 4. Keep the Proxmark button pressed while reconnecting it to USB. Its yellow and red lights should light up (you can release the button after 5-ish seconds).<br /> <br /> 5. Now upgrade the bootrom:<br /> <br /> ./flasher -b ../../bootrom/obj/bootrom.elf<br /> <br /> 6. cd ../..<br /> <br /> 7. Disconnect your proxmark and keep the button pressed while reconnecting to USB.<br /> <br /> 8. While keeping the button pressed run to get the device name:<br /> <br /> ls /dev/cu*<br /> <br /> You should find a name like &quot;/dev/cu.usbmodem####&quot; (#### represents a number).<br /> <br /> 9. While still KEEPING PRESSED the button update the FPGA and its OS:<br /> <br /> ./client/flasher /dev/cu.usbmodem#### armsrc/obj/fullimage.elf<br /> <br /> 10. Disconnect the proxmark and release the button.<br /> <br /> 11. Now reconnect your proxmark to USB and run it:<br /> <br /> cd proxmark3/client<br /> ./proxmark3 /dev/cu.usbmodem####<br /> <br /> No need to go to &quot;Finish Line&quot;, you are already finished with setting up the Proxmark Environment<br /> <br /> === Finish Line ===<br /> <br /> 1. Compile the bootrom and OS:<br /> <br /> make clean; make<br /> <br /> 2. Disconnect your Proxmark from USB. Then keep the button pressed while reconnecting it back to USB. You can release the button when you see yellow/orange and red lights on your proxmark. (If you have an Elechouse v2 Proxmark3 or Elechouse v3 Proxmark3 Easy you do not need to press the button)<br /> <br /> 3. Figure out your device name:<br /> <br /> ls /dev/cu*<br /> <br /> It should be something with /dev/cu.usbmodem#### (#### represents a number).<br /> <br /> 4. After you have found your device run the program:<br /> <br /> cd proxmark3/client<br /> ./proxmark3 /dev/cu.usbmodem####<br /> <br /> == Linux installation ==<br /> <br /> === Requirements ===<br /> <br /> * Operating system: Ubuntu 16.04 trusty amd64<br /> <br /> === Step 1 Compile resources:===<br /> <br /> 1. download and install some needed packages and libs<br /> <br /> sudo apt-get install p7zip git build-essential libreadline5 libreadline-dev libusb-0.1-4 libusb-dev libqt4-dev perl pkg-config wget libncurses5-dev gcc-arm-none-eabi libstdc++-arm-none-eabi-newlib<br /> <br /> 2. clone proxmark3 git repository<br /> <br /> git clone https://github.com/proxmark/proxmark3.git<br /> <br /> 3. enter repo<br /> <br /> cd proxmark3<br /> <br /> 4. get newest version<br /> <br /> git pull<br /> git checkout v3.1.0 # important git checkout latest stable version!! <br /> <br /> 5. Install the blacklist rules<br /> <br /> sudo cp -rf driver/77-mm-usb-device-blacklist.rules /etc/udev/rules.d/77-mm-usb-device-blacklist.rules<br /> sudo udevadm control --reload-rules<br /> <br /> 6. add current user to group<br /> <br /> sudo adduser $USER dialout<br /> <br /> 7. compile proxmark3<br /> <br /> make clean &amp;&amp; make all<br /> <br /> <br /> === Step 2 Identify proxmark3 device ===<br /> <br /> dmesg | grep -i usb<br /> [ 9704.503904] usb 1-3: Manufacturer: proxmark.org<br /> [ 9704.539638] cdc_acm 1-3:1.0: ttyACM0: USB ACM device<br /> <br /> === Step 3 Flash the firmware of the proxmark ===<br /> <br /> client/flasher /dev/ttyACM0 -b bootrom/obj/bootrom.elf armsrc/obj/fullimage.elf<br /> <br /> if it does not succeed at first glance log out your user and log in again, this worked for me!!<br /> <br /> == Windows installation ==<br /> <br /> === Requirements ===<br /> The tested Version for Windows was Windows 10, therefore the requirements for successfully completing our installation guide are:<br /> * Windows 10<br /> * [https://git-scm.com/download/win Git for Windows]<br /> <br /> === Installation ===<br /> In order to be able to connect to your Proxmark3 under Windows you need to emulate a Linux environment which is done through a tool called ProxSpace.<br /> <br /> 1. First you need to download the download the ProxSpace Repository through git.<br /> <br /> '''Caution!''' Your current working directory should contain no whitespaces!<br /> <br /> git clone https://github.com/Gator96100/ProxSpace.git<br /> <br /> 2. Inside your ProxSpace Folder you should find &quot;runme.bat&quot;. Start it.<br /> <br /> 3. This will create and install all necessary packets and folders. After you should see the pm3-console.<br /> <br /> 4. From this console you should change the directory to ProxSpace and download the Proxmark3 Repository:<br /> <br /> git clone https://github.com/Proxmark/proxmark3.git<br /> <br /> 5. After this process is complete, cd to the proxmark3 directory:<br /> <br /> cd proxmark3<br /> <br /> 6. Compile the proxmark3 project:<br /> <br /> make clean &amp;&amp; make all<br /> <br /> 7. Install the proxmark3 driver<br /> <br /> ==== Windows 10 ====<br /> Since this driver is not officially signed by a trusted authority the installation is a bit tricky. You first have to start Windows in save-mode. This is done easiest, when pressing the shift-key while restarting your PC. On reboot you choose Startup-Settings followed by #7 Disable driver signature enforcement.<br /> After the computer restarted you connect the proxmark3 and go to the device manager, right click on the non-identified device (which is the proxmark3) and go to the settings. Click on update driver and search locally for the proxmark3.inf. If you have trouble getting the proxmark3 driver to work, please visit this [[https://store.ryscc.com/blogs/news/how-to-install-a-proxmark3-driver-on-windows-10 picture-guided tutorial]]<br /> <br /> <br /> After, the installation should be complete and you can safely restart your PC to normal mode again. From there start the runme.bat and the pm3-console should appear.<br /> <br /> ==== Windows 7 ====<br /> [[File:Win7-disable-driversignature.png|520px|right]]<br /> <br /> * Start command prompt (cmd.exe) as '''administrator''' and execute:<br /> <br /> bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS<br /> bcdedit.exe -set TESTSIGNING ON<br /> <br /> * Open the device manager, right-click on the unknow device &quot;proxmark3&quot; and select &quot;update&quot;<br /> * Select the manual driver selection, and within your ''ProxSpace'' folder select the ''msys2\proxmark3\driver'' subfolder<br /> <br /> After the successful driver setup you may want to disable testsigning again, and restart windows<br /> <br /> bcdedit.exe -set TESTSIGNING OFF<br /> <br /> === Update your Proxmark3 ===<br /> <br /> To update the firmware of your Proxmark3 to the latest version, open cmd and type in (with x standing for the right number of your COM port, e.g. COM2):<br /> <br /> ./proxmark/client/flasher COMx -b /bootrom/obj/bootrom.elf<br /> ./proxmark/client/flasher COMX ./armsrc/obj/fullimage.elf<br /> <br /> === Connecting to your Proxmark3 ===<br /> <br /> After having done all the steps above you can safely connect to your Proxmark3 through (where x again stands for the right number of your COM port, e.g. COM2):<br /> <br /> ./client/proxmark3.exe COMx<br /> <br /> == Usage ==<br /> <br /> For using the Proxmark3 please visit our second documentation [[Proxmark3: Useful commands]] and feel free to have a look at the [https://github.com/Proxmark/proxmark3 Proxmark Repository!]<br /> <br /> == Resources and Tutorials ==<br /> <br /> * Client commands: https://github.com/Proxmark/proxmark3/wiki/commands<br /> * Usage example: https://www.youtube.com/watch?v=FODGYfhqb4Q<br /> * Basic tutorial for RFID usage: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br /> * Advanced tutorial: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br /> * Capture NFC traffic of apple pay transaction: https://salmg.net/2017/12/29/analyzing-an-apple-pay-transaction-with-proxmark3/<br /> <br /> == Used Hardware ==<br /> <br /> [[Proxmark 3]]<br /> <br /> == References ==<br /> * Product page and infos: https://www.elechouse.com/elechouse/index.php?main_page=product_info&amp;cPath=90_93&amp;products_id=2264&amp;zenid=kmvhiob7nq1orc4pfjtf53sbr7<br /> * Manual: https://www.elechouse.com/elechouse/images/product/proxmark3_V2/Proxmark3%20V2%20User%20Guid.pdf<br /> * MacOS 10.x client installation: https://github.com/Proxmark/proxmark3/wiki/MacOS<br /> * Linux 16.04 client installation: https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux<br /> * Windows 10 client installation: https://github.com/Proxmark/proxmark3/wiki/Windows<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=Proxmark3:_Installation&diff=2045 2019-09-20T14:34:55Z

<p>StSchmitzhofer: /* Installation */ Updated for Windows7 setup</p> <hr /> <div>== Summary == <br /> <br /> Installation of Proxmark3 on macOS, Linux and Windows for RFID and NFC sniffing.<br /> <br /> == MacOS installation ==<br /> <br /> === Requirements ===<br /> <br /> Xcode (AppStore) is a must.<br /> <br /> In addition to make the installation easier have either HomeBrew or MacPorts ready.<br /> A Tutorial for installing:<br /> A) HomeBrew: https://docs.brew.sh/Installation<br /> B) MacPorts: https://www.macports.org/install.php<br /> <br /> Because of their different architecture (HomeBrew/MacPorts), some parts of this tutorial are split into:<br /> A) Installation with HomeBrew<br /> B) Installation with MacPorts<br /> Just choose the tutorial that suits your current setup.<br /> <br /> === Installation with HomeBrew ===<br /> <br /> 1. Download (&quot;tap&quot;) the proxmark repository:<br /> <br /> brew tap proxmark/proxmark3<br /> <br /> 2. Install proxmark3:<br /> <br /> brew install proxmark3<br /> <br /> === Manual Installation ===<br /> <br /> Download the drivers and install them.<br /> If you have MacPorts:<br /> <br /> sudo port install p7zip readline libusb libusb-compat perl5 wget qt5\\ arm-none-eabi-gcc pkgconfig<br /> <br /> If you have HomeBrew:<br /> <br /> brew tap nitsky/stm32<br /> brew install readline libusb p7zip libusb-compat wget qt5 pkgconfig\\ arm-none-eabi-gcc<br /> <br /> Now you will need to add QT to the PKG_CONFIG_PATH so it find QT5 (replace YOUR_VERSION with your version number:<br /> <br /> export\\ PKG_CONFIG_PATH=/usr/local/Cellar/qt5/&lt;&lt;YOUR_VERSION&gt;&gt;/lib/pkgconfig/<br /> <br /> 3. And add moc_location in Qt5Core.pc file:<br /> <br /> export QT_PKG_CONFIG_QT5CORE=$(find /usr -name Qt5Core.pc 2&gt;/dev/null)<br /> chmod 666 $QT_PKG_CONFIG_QT5CORE<br /> echo &quot;moc_location=\${prefix}/bin/moc&quot; &gt;&gt; $QT_PKG_CONFIG_QT5CORE<br /> chmod 444 $QT_PKG_CONFIG_QT5CORE<br /> <br /> 4. For link creation to avoid any errors of &quot;readline&quot; (may happen):<br /> <br /> brew link --force readline<br /> <br /> 5. Now either git clone or manually download the Proxmark project. Git clone:<br /> <br /> git clone https://github.com/Proxmark/proxmark3.git<br /> <br /> 6. &quot;cd&quot; to the proxmark3 folder<br /> <br /> 7. Now jump to the section &quot;Connecting your Proxmark&quot;<br /> <br /> === Connecting your Proxmark ===<br /> <br /> 1. Insert your Proxmark and run<br /> <br /> system_profiler SPUSBDataType<br /> <br /> 2.a) If your Proxmark is CDC you should somewhere see in the output:<br /> <br /> Product ID: 0x504d<br /> Vendor ID: 0x2d2d<br /> <br /> 2.b) If your Proxmark is an HID device you should see:<br /> <br /> Product ID: 0x4b8f<br /> Vendor ID: 0x9ac4<br /> <br /> If it is an HID Device you will need to upgrade it, then go to &quot;Upgrading my Proxmark HID-&gt;CDC&quot;<br /> If you have an CDC Proxmark you can jump to &quot;Finish Line&quot;<br /> <br /> === Upgrading my Proxmark HID-&gt;CDC ===<br /> <br /> 1. Compile the bootrom, OS and software:<br /> <br /> make clean; make<br /> <br /> 2. Also compile the HID compatible flash program:<br /> <br /> cd client/hid-flasher;make<br /> <br /> 3. Disconnect Apple's HID driver, by installing a dummy kernel driver:<br /> <br /> sudo make install_kext<br /> sudo kextcache -system-caches<br /> <br /> 4. Keep the Proxmark button pressed while reconnecting it to USB. Its yellow and red lights should light up (you can release the button after 5-ish seconds).<br /> <br /> 5. Now upgrade the bootrom:<br /> <br /> ./flasher -b ../../bootrom/obj/bootrom.elf<br /> <br /> 6. cd ../..<br /> <br /> 7. Disconnect your proxmark and keep the button pressed while reconnecting to USB.<br /> <br /> 8. While keeping the button pressed run to get the device name:<br /> <br /> ls /dev/cu*<br /> <br /> You should find a name like &quot;/dev/cu.usbmodem####&quot; (#### represents a number).<br /> <br /> 9. While still KEEPING PRESSED the button update the FPGA and its OS:<br /> <br /> ./client/flasher /dev/cu.usbmodem#### armsrc/obj/fullimage.elf<br /> <br /> 10. Disconnect the proxmark and release the button.<br /> <br /> 11. Now reconnect your proxmark to USB and run it:<br /> <br /> cd proxmark3/client<br /> ./proxmark3 /dev/cu.usbmodem####<br /> <br /> No need to go to &quot;Finish Line&quot;, you are already finished with setting up the Proxmark Environment<br /> <br /> === Finish Line ===<br /> <br /> 1. Compile the bootrom and OS:<br /> <br /> make clean; make<br /> <br /> 2. Disconnect your Proxmark from USB. Then keep the button pressed while reconnecting it back to USB. You can release the button when you see yellow/orange and red lights on your proxmark. (If you have an Elechouse v2 Proxmark3 or Elechouse v3 Proxmark3 Easy you do not need to press the button)<br /> <br /> 3. Figure out your device name:<br /> <br /> ls /dev/cu*<br /> <br /> It should be something with /dev/cu.usbmodem#### (#### represents a number).<br /> <br /> 4. After you have found your device run the program:<br /> <br /> cd proxmark3/client<br /> ./proxmark3 /dev/cu.usbmodem####<br /> <br /> == Linux installation ==<br /> <br /> === Requirements ===<br /> <br /> * Operating system: Ubuntu 16.04 trusty amd64<br /> <br /> === Step 1 Compile resources:===<br /> <br /> 1. download and install some needed packages and libs<br /> <br /> sudo apt-get install p7zip git build-essential libreadline5 libreadline-dev libusb-0.1-4 libusb-dev libqt4-dev perl pkg-config wget libncurses5-dev gcc-arm-none-eabi libstdc++-arm-none-eabi-newlib<br /> <br /> 2. clone proxmark3 git repository<br /> <br /> git clone https://github.com/proxmark/proxmark3.git<br /> <br /> 3. enter repo<br /> <br /> cd proxmark3<br /> <br /> 4. get newest version<br /> <br /> git pull<br /> git checkout v3.1.0 # important git checkout latest stable version!! <br /> <br /> 5. Install the blacklist rules<br /> <br /> sudo cp -rf driver/77-mm-usb-device-blacklist.rules /etc/udev/rules.d/77-mm-usb-device-blacklist.rules<br /> sudo udevadm control --reload-rules<br /> <br /> 6. add current user to group<br /> <br /> sudo adduser $USER dialout<br /> <br /> 7. compile proxmark3<br /> <br /> make clean &amp;&amp; make all<br /> <br /> <br /> === Step 2 Identify proxmark3 device ===<br /> <br /> dmesg | grep -i usb<br /> [ 9704.503904] usb 1-3: Manufacturer: proxmark.org<br /> [ 9704.539638] cdc_acm 1-3:1.0: ttyACM0: USB ACM device<br /> <br /> === Step 3 Flash the firmware of the proxmark ===<br /> <br /> client/flasher /dev/ttyACM0 -b bootrom/obj/bootrom.elf armsrc/obj/fullimage.elf<br /> <br /> if it does not succeed at first glance log out your user and log in again, this worked for me!!<br /> <br /> == Windows installation ==<br /> <br /> === Requirements ===<br /> The tested Version for Windows was Windows 10, therefore the requirements for successfully completing our installation guide are:<br /> * Windows 10<br /> * [https://git-scm.com/download/win Git for Windows]<br /> <br /> === Installation ===<br /> In order to be able to connect to your Proxmark3 under Windows you need to emulate a Linux environment which is done through a tool called ProxSpace.<br /> <br /> 1. First you need to download the download the ProxSpace Repository through git.<br /> <br /> '''Caution!''' Your current working directory should contain no whitespaces!<br /> <br /> git clone https://github.com/Gator96100/ProxSpace.git<br /> <br /> 2. Inside your ProxSpace Folder you should find &quot;runme.bat&quot;. Start it.<br /> <br /> 3. This will create and install all necessary packets and folders. After you should see the pm3-console.<br /> <br /> 4. From this console you should change the directory to ProxSpace and download the Proxmark3 Repository:<br /> <br /> git clone https://github.com/Proxmark/proxmark3.git<br /> <br /> 5. After this process is complete, cd to the proxmark3 directory:<br /> <br /> cd proxmark3<br /> <br /> 6. Compile the proxmark3 project:<br /> <br /> make clean &amp;&amp; make all<br /> <br /> 7. Install the proxmark3 driver<br /> <br /> ==== Windows 10 ====<br /> Since this driver is not officially signed by a trusted authority the installation is a bit tricky. You first must start Windows in save-mode. This is done easiest, when the sift-key is pressed while restarting your PC. On reboot you choose Startup-Settings followed by #7 Disable driver signature enforcement.<br /> After the computer started up you connect the proxmark3 and go to the device manager, right click on the non-identified device (which is the proxmark3) and go to the settings. Click on update driver and search locally for the proxmark3.inf. If you have trouble getting the proxmark3 driver to work, please visit this [[https://store.ryscc.com/blogs/news/how-to-install-a-proxmark3-driver-on-windows-10 picture-guided tutorial]]<br /> <br /> <br /> After, the installation should be complete and you can safely restart your PC to normal mode again. From there start the runme.bat and the pm3-console should appear.<br /> <br /> ==== Windows 7 ====<br /> [[File:Win7-disable-driversignature.png|520px|right]]<br /> <br /> * Start command prompt (cmd.exe) as '''administrator''' and execute:<br /> <br /> bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS<br /> bcdedit.exe -set TESTSIGNING ON<br /> <br /> * Open the device manager, right-click on the unknow device &quot;proxmark3&quot; and select &quot;update&quot;<br /> * Select the manual driver selection, and within your ''ProxSpace'' folder select the ''msys2\proxmark3\driver'' subfolder<br /> <br /> After the successful driver setup you may want to disable testsigning again, and restart windows<br /> <br /> bcdedit.exe -set TESTSIGNING OFF<br /> <br /> === Update your Proxmark3 ===<br /> <br /> To update the firmware of your Proxmark3 to the latest version, open cmd and type in (with x standing for the right number of your COM port, e.g. COM2):<br /> <br /> ./proxmark/client/flasher COMx -b /bootrom/obj/bootrom.elf<br /> ./proxmark/client/flasher COMX ./armsrc/obj/fullimage.elf<br /> <br /> === Connecting to your Proxmark3 ===<br /> <br /> After having done all the steps above you can safely connect to your Proxmark3 through (where x again stands for the right number of your COM port, e.g. COM2):<br /> <br /> ./client/proxmark3.exe COMx<br /> <br /> == Usage ==<br /> <br /> For using the Proxmark3 please visit our second documentation [[Proxmark3: Useful commands]] and feel free to have a look at the [https://github.com/Proxmark/proxmark3 Proxmark Repository!]<br /> <br /> == Resources and Tutorials ==<br /> <br /> * Client commands: https://github.com/Proxmark/proxmark3/wiki/commands<br /> * Usage example: https://www.youtube.com/watch?v=FODGYfhqb4Q<br /> * Basic tutorial for RFID usage: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br /> * Advanced tutorial: https://blog.kchung.co/rfid-hacking-with-the-proxmark-3/<br /> * Capture NFC traffic of apple pay transaction: https://salmg.net/2017/12/29/analyzing-an-apple-pay-transaction-with-proxmark3/<br /> <br /> == Used Hardware ==<br /> <br /> [[Proxmark 3]]<br /> <br /> == References ==<br /> * Product page and infos: https://www.elechouse.com/elechouse/index.php?main_page=product_info&amp;cPath=90_93&amp;products_id=2264&amp;zenid=kmvhiob7nq1orc4pfjtf53sbr7<br /> * Manual: https://www.elechouse.com/elechouse/images/product/proxmark3_V2/Proxmark3%20V2%20User%20Guid.pdf<br /> * MacOS 10.x client installation: https://github.com/Proxmark/proxmark3/wiki/MacOS<br /> * Linux 16.04 client installation: https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux<br /> * Windows 10 client installation: https://github.com/Proxmark/proxmark3/wiki/Windows<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:Win7-disable-driversignature.png&diff=2044 2019-09-20T14:26:46Z

<p>StSchmitzhofer: </p> <hr /> <div></div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2025 2019-09-16T00:02:34Z

<p>StSchmitzhofer: </p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: [[Tradfri_Gateway|IKEA TRÅDFRI Typ E1526 (Gateway)]], WiFi router <br /> <br /> == Description ==<br /> <br /> [[File:TRADFRI Gateway Opened.jpg|200px|thumb|Gateway opened up and plugged in]]<br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> <br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting (Android) IKEA Home Smart]<br /> * [https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071 (iOS) IKEA Home Smart]<br /> <br /> Follow the instructions within the app, to finish the process.<br /> <br /> <br /> [[File:Ikea tradfri gateway plugin.png|320px]]<br /> [[File:Ikea tradfri gateway codescan.png|320px]]<br /> [[File:Ikea tradfri gateway finished.png|320px]]<br /> <br /> <br /> == Used Hardware ==<br /> <br /> Mandadory:<br /> <br /> * [[Tradfri_Gateway]]<br /> <br /> Optional:<br /> <br /> * [[Tradfri_dimmer]]<br /> * [[Tradfri_smart_plug]]<br /> * [[Tradfri_smart_plug_with_button]]<br /> * [[Tradfri_signal_repeater]]<br /> * [[Tradfri_remote_control]]<br /> * [[Tradfri_motion_sensor]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_10_W]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_30_W]]<br /> * [[Tradfri_LED_with_motion_sensor_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_dimmer]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_remote_control]]<br /> * [[Tradfri_LED_400_lm_5.3_W_E14]]<br /> * [[Tradfri_LED_400_lm_5.3_W_GU10]]<br /> * [[Tradfri_LED_950_lm_12_W_E27]]<br /> <br /> <br /> == Alternatives &amp; Tests ==<br /> <br /> As of today, there is no official alternative to a setup via mobile app, albeit ...<br /> * A simple nmap scan reveales a suspicious (unencrypted) open '''port 80''', which requires authentication ('''status code 470''', while no entity body is sent).<br /> * However listening into a live connection (Wireshark and an Android Emulator) reveals that actually a secure '''DTLS''' connection (port 5684) is used to set up the gateway.<br /> <br /> Basic scan results:<br /> <br /> [[File:Ikea tradfri gateway wiresharklog.png|right]]<br /> <br /> Starting Nmap 7.80 ( https://nmap.org ) at 2019-09-14 02:35 Mitteleuropäische Sommerzeit<br /> NSE: Loaded 151 scripts for scanning.<br /> NSE: Script Pre-scanning.<br /> ...<br /> Initiating ARP Ping Scan at 02:35<br /> Scanning 10.77.77.6 [1 port]<br /> Completed ARP Ping Scan at 02:35, 0.19s elapsed (1 total hosts)<br /> Initiating Parallel DNS resolution of 1 host. at 02:35<br /> Completed Parallel DNS resolution of 1 host. at 02:35, 11.04s elapsed<br /> Initiating SYN Stealth Scan at 02:35<br /> Scanning 10.77.77.6 [1000 ports]<br /> Discovered open port 80/tcp on 10.77.77.6<br /> Completed SYN Stealth Scan at 02:35, 0.81s elapsed (1000 total ports)<br /> Initiating Service scan at 02:35<br /> Scanning 1 service on 10.77.77.6<br /> Completed Service scan at 02:36, 38.22s elapsed (1 service on 1 host)<br /> ...<br /> Nmap scan report for 10.77.77.6<br /> Host is up (0.00051s latency).<br /> Not shown: 999 closed ports<br /> PORT STATE SERVICE VERSION<br /> 80/tcp open http<br /> | fingerprint-strings: <br /> | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LANDesk-RC, LDAPBindReq, LDAPSearchReq, LPDString, NCP, NotesRPC, RPCCheck, RTSPRequest, SIPOptions, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServer, TerminalServerCookie, X11Probe: <br /> |_ HTTP/1.1 470 Connection Authorization Required<br /> |_http-title: Site doesn't have a title.<br /> 1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :<br /> SF-Port80-TCP:V=7.80%I=7%D=9/14%Time=5D7C35ED%P=i686-pc-windows-windows%r(<br /> SF:GetRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(HTTPOptions,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Autho<br /> SF:rization\x20Required\r\n\r\n&quot;)%r(RTSPRequest,32,&quot;HTTP/1\.1\x20470\x20Co<br /> SF:nnection\x20Authorization\x20Required\r\n\r\n&quot;)%r(X11Probe,32,&quot;HTTP/1\.<br /> SF:1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(FourOhF<br /> SF:ourRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(GenericLines,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Auth<br /> SF:orization\x20Required\r\n\r\n&quot;)%r(RPCCheck,32,&quot;HTTP/1\.1\x20470\x20Conn<br /> SF:ection\x20Authorization\x20Required\r\n\r\n&quot;)%r(DNSVersionBindReqTCP,32<br /> SF:,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)<br /> SF:%r(DNSStatusRequestTCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorizat<br /> SF:ion\x20Required\r\n\r\n&quot;)%r(Help,32,&quot;HTTP/1\.1\x20470\x20Connection\x20<br /> SF:Authorization\x20Required\r\n\r\n&quot;)%r(SSLSessionReq,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(TerminalServer<br /> SF:Cookie,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\<br /> SF:r\n\r\n&quot;)%r(TLSSessionReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(Kerberos,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;)%r(SMBProgNeg,32,&quot;HTTP/1\.1\x<br /> SF:20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LPDString,<br /> SF:32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n<br /> SF:&quot;)%r(LDAPSearchReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\<br /> SF:x20Required\r\n\r\n&quot;)%r(LDAPBindReq,32,&quot;HTTP/1\.1\x20470\x20Connection\<br /> SF:x20Authorization\x20Required\r\n\r\n&quot;)%r(SIPOptions,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LANDesk-RC,32,<br /> SF:&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%<br /> SF:r(TerminalServer,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x2<br /> SF:0Required\r\n\r\n&quot;)%r(NCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(NotesRPC,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;);<br /> MAC Address: 44:91:60:25:F5:CB (Murata Manufacturing)<br /> No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).<br /> TCP/IP fingerprint:<br /> OS:SCAN(V=7.80%E=4%D=9/14%OT=80%CT=1%CU=39904%PV=Y%DS=1%DC=D%G=Y%M=449160%T<br /> OS:M=5D7C362E%P=i686-pc-windows-windows)SEQ(CI=I%II=I%TS=U)ECN(R=N)T1(R=Y%D<br /> OS:F=N%T=80%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=80%W=0<br /> OS:%S=A%A=Z%F=R%O=%RD=0%Q=)T5(R=Y%DF=N%T=80%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6<br /> OS:(R=Y%DF=N%T=80%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=N%T=80%W=0%S=Z%A=S+%<br /> OS:F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G<br /> OS:%RUD=G)IE(R=Y%DFI=N%T=80%CD=S)<br /> <br /> Network Distance: 1 hop<br /> <br /> TRACEROUTE<br /> HOP RTT ADDRESS<br /> 1 0.51 ms 10.77.77.6<br /> <br /> NSE: Script Post-scanning.<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Read data files from: C:\Program Files (x86)\Nmap<br /> OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .<br /> Nmap done: 1 IP address (1 host up) scanned in 89.06 seconds<br /> Raw packets sent: 1215 (58.910KB) | Rcvd: 1089 (45.266KB)<br /> <br /> <br /> <br /> <br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2024 2019-09-15T23:49:00Z

<p>StSchmitzhofer: Added test results (AndroidEmulator &amp; Wireshark)</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: [[Tradfri_Gateway|IKEA TRÅDFRI Typ E1526 (Gateway)]], WiFi router <br /> <br /> == Description ==<br /> <br /> [[File:TRADFRI Gateway Opened.jpg|200px|thumb|Gateway opened up and plugged in]]<br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> <br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting (Android) IKEA Home Smart]<br /> * [https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071 (iOS) IKEA Home Smart]<br /> <br /> Follow the instructions within the app, to finish the process.<br /> <br /> <br /> [[File:Ikea tradfri gateway plugin.png|320px]]<br /> [[File:Ikea tradfri gateway codescan.png|320px]]<br /> [[File:Ikea tradfri gateway finished.png|320px]]<br /> <br /> <br /> == Used Hardware ==<br /> <br /> Mandadory:<br /> <br /> * [[Tradfri_Gateway]]<br /> <br /> Optional:<br /> <br /> * [[Tradfri_dimmer]]<br /> * [[Tradfri_smart_plug]]<br /> * [[Tradfri_smart_plug_with_button]]<br /> * [[Tradfri_signal_repeater]]<br /> * [[Tradfri_remote_control]]<br /> * [[Tradfri_motion_sensor]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_10_W]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_30_W]]<br /> * [[Tradfri_LED_with_motion_sensor_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_dimmer]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_remote_control]]<br /> * [[Tradfri_LED_400_lm_5.3_W_E14]]<br /> * [[Tradfri_LED_400_lm_5.3_W_GU10]]<br /> * [[Tradfri_LED_950_lm_12_W_E27]]<br /> <br /> <br /> == Alternatives &amp; Tests ==<br /> <br /> As of today, there is no official alternative to a setup via mobile app, even though a simple nmap scan reveales an (unencrypted) open '''port 80''', which requires '''authentication''' (status code 470, no entity body).<br /> <br /> → Listening into a live connection (Wireshark and an Android Emulator) however reveal that actually a secure DTLS connection on port 5684 is used to set up the gateway.<br /> <br /> Scan results:<br /> <br /> [[File:Ikea tradfri gateway wiresharklog.png|right]]<br /> <br /> Starting Nmap 7.80 ( https://nmap.org ) at 2019-09-14 02:35 Mitteleuropäische Sommerzeit<br /> NSE: Loaded 151 scripts for scanning.<br /> NSE: Script Pre-scanning.<br /> ...<br /> Initiating ARP Ping Scan at 02:35<br /> Scanning 10.77.77.6 [1 port]<br /> Completed ARP Ping Scan at 02:35, 0.19s elapsed (1 total hosts)<br /> Initiating Parallel DNS resolution of 1 host. at 02:35<br /> Completed Parallel DNS resolution of 1 host. at 02:35, 11.04s elapsed<br /> Initiating SYN Stealth Scan at 02:35<br /> Scanning 10.77.77.6 [1000 ports]<br /> Discovered open port 80/tcp on 10.77.77.6<br /> Completed SYN Stealth Scan at 02:35, 0.81s elapsed (1000 total ports)<br /> Initiating Service scan at 02:35<br /> Scanning 1 service on 10.77.77.6<br /> Completed Service scan at 02:36, 38.22s elapsed (1 service on 1 host)<br /> ...<br /> Nmap scan report for 10.77.77.6<br /> Host is up (0.00051s latency).<br /> Not shown: 999 closed ports<br /> PORT STATE SERVICE VERSION<br /> 80/tcp open http<br /> | fingerprint-strings: <br /> | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LANDesk-RC, LDAPBindReq, LDAPSearchReq, LPDString, NCP, NotesRPC, RPCCheck, RTSPRequest, SIPOptions, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServer, TerminalServerCookie, X11Probe: <br /> |_ HTTP/1.1 470 Connection Authorization Required<br /> |_http-title: Site doesn't have a title.<br /> 1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :<br /> SF-Port80-TCP:V=7.80%I=7%D=9/14%Time=5D7C35ED%P=i686-pc-windows-windows%r(<br /> SF:GetRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(HTTPOptions,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Autho<br /> SF:rization\x20Required\r\n\r\n&quot;)%r(RTSPRequest,32,&quot;HTTP/1\.1\x20470\x20Co<br /> SF:nnection\x20Authorization\x20Required\r\n\r\n&quot;)%r(X11Probe,32,&quot;HTTP/1\.<br /> SF:1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(FourOhF<br /> SF:ourRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(GenericLines,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Auth<br /> SF:orization\x20Required\r\n\r\n&quot;)%r(RPCCheck,32,&quot;HTTP/1\.1\x20470\x20Conn<br /> SF:ection\x20Authorization\x20Required\r\n\r\n&quot;)%r(DNSVersionBindReqTCP,32<br /> SF:,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)<br /> SF:%r(DNSStatusRequestTCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorizat<br /> SF:ion\x20Required\r\n\r\n&quot;)%r(Help,32,&quot;HTTP/1\.1\x20470\x20Connection\x20<br /> SF:Authorization\x20Required\r\n\r\n&quot;)%r(SSLSessionReq,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(TerminalServer<br /> SF:Cookie,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\<br /> SF:r\n\r\n&quot;)%r(TLSSessionReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(Kerberos,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;)%r(SMBProgNeg,32,&quot;HTTP/1\.1\x<br /> SF:20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LPDString,<br /> SF:32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n<br /> SF:&quot;)%r(LDAPSearchReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\<br /> SF:x20Required\r\n\r\n&quot;)%r(LDAPBindReq,32,&quot;HTTP/1\.1\x20470\x20Connection\<br /> SF:x20Authorization\x20Required\r\n\r\n&quot;)%r(SIPOptions,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LANDesk-RC,32,<br /> SF:&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%<br /> SF:r(TerminalServer,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x2<br /> SF:0Required\r\n\r\n&quot;)%r(NCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(NotesRPC,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;);<br /> MAC Address: 44:91:60:25:F5:CB (Murata Manufacturing)<br /> No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).<br /> TCP/IP fingerprint:<br /> OS:SCAN(V=7.80%E=4%D=9/14%OT=80%CT=1%CU=39904%PV=Y%DS=1%DC=D%G=Y%M=449160%T<br /> OS:M=5D7C362E%P=i686-pc-windows-windows)SEQ(CI=I%II=I%TS=U)ECN(R=N)T1(R=Y%D<br /> OS:F=N%T=80%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=80%W=0<br /> OS:%S=A%A=Z%F=R%O=%RD=0%Q=)T5(R=Y%DF=N%T=80%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6<br /> OS:(R=Y%DF=N%T=80%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=N%T=80%W=0%S=Z%A=S+%<br /> OS:F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G<br /> OS:%RUD=G)IE(R=Y%DFI=N%T=80%CD=S)<br /> <br /> Network Distance: 1 hop<br /> <br /> TRACEROUTE<br /> HOP RTT ADDRESS<br /> 1 0.51 ms 10.77.77.6<br /> <br /> NSE: Script Post-scanning.<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Read data files from: C:\Program Files (x86)\Nmap<br /> OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .<br /> Nmap done: 1 IP address (1 host up) scanned in 89.06 seconds<br /> Raw packets sent: 1215 (58.910KB) | Rcvd: 1089 (45.266KB)<br /> <br /> <br /> <br /> <br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:Ikea_tradfri_gateway_wiresharklog.png&diff=2023 2019-09-15T23:22:50Z

<p>StSchmitzhofer: </p> <hr /> <div></div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2022 2019-09-15T22:48:36Z

<p>StSchmitzhofer: Simplified steps a little bit, and formatted pictures</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: [[Tradfri_Gateway|IKEA TRÅDFRI Typ E1526 (Gateway)]], WiFi router <br /> <br /> == Description ==<br /> <br /> [[File:TRADFRI Gateway Opened.jpg|200px|thumb|Gateway opened up and plugged in]]<br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> <br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting (Android) IKEA Home Smart]<br /> * [https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071 (iOS) IKEA Home Smart]<br /> <br /> Follow the instructions within the app, to finish the process.<br /> <br /> <br /> [[File:Ikea tradfri gateway plugin.png|320px]]<br /> [[File:Ikea tradfri gateway codescan.png|320px]]<br /> [[File:Ikea tradfri gateway finished.png|320px]]<br /> <br /> <br /> == Used Hardware ==<br /> <br /> Mandadory:<br /> <br /> * [[Tradfri_Gateway]]<br /> <br /> Optional:<br /> <br /> * [[Tradfri_dimmer]]<br /> * [[Tradfri_smart_plug]]<br /> * [[Tradfri_smart_plug_with_button]]<br /> * [[Tradfri_signal_repeater]]<br /> * [[Tradfri_remote_control]]<br /> * [[Tradfri_motion_sensor]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_10_W]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_30_W]]<br /> * [[Tradfri_LED_with_motion_sensor_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_dimmer]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_remote_control]]<br /> * [[Tradfri_LED_400_lm_5.3_W_E14]]<br /> * [[Tradfri_LED_400_lm_5.3_W_GU10]]<br /> * [[Tradfri_LED_950_lm_12_W_E27]]<br /> <br /> <br /> == Alternatives ==<br /> <br /> As of today, there is no '''official''' alternative to the suggested setup via app. A simple nmap scan however reveales an (unencrypted) open '''port 80''' which requires '''authentication''' (HTTP status code 470, no form, nor any HTML).<br /> <br /> → Listening into a live connection (e.g. Wireshark &amp; Android Emulator), might give further insight into other possibilities.<br /> <br /> Nmap scan results:<br /> Starting Nmap 7.80 ( https://nmap.org ) at 2019-09-14 02:35 Mitteleuropäische Sommerzeit<br /> NSE: Loaded 151 scripts for scanning.<br /> NSE: Script Pre-scanning.<br /> ...<br /> Initiating ARP Ping Scan at 02:35<br /> Scanning 10.77.77.6 [1 port]<br /> Completed ARP Ping Scan at 02:35, 0.19s elapsed (1 total hosts)<br /> Initiating Parallel DNS resolution of 1 host. at 02:35<br /> Completed Parallel DNS resolution of 1 host. at 02:35, 11.04s elapsed<br /> Initiating SYN Stealth Scan at 02:35<br /> Scanning 10.77.77.6 [1000 ports]<br /> Discovered open port 80/tcp on 10.77.77.6<br /> Completed SYN Stealth Scan at 02:35, 0.81s elapsed (1000 total ports)<br /> Initiating Service scan at 02:35<br /> Scanning 1 service on 10.77.77.6<br /> Completed Service scan at 02:36, 38.22s elapsed (1 service on 1 host)<br /> ...<br /> Nmap scan report for 10.77.77.6<br /> Host is up (0.00051s latency).<br /> Not shown: 999 closed ports<br /> PORT STATE SERVICE VERSION<br /> 80/tcp open http<br /> | fingerprint-strings: <br /> | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LANDesk-RC, LDAPBindReq, LDAPSearchReq, LPDString, NCP, NotesRPC, RPCCheck, RTSPRequest, SIPOptions, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServer, TerminalServerCookie, X11Probe: <br /> |_ HTTP/1.1 470 Connection Authorization Required<br /> |_http-title: Site doesn't have a title.<br /> 1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :<br /> SF-Port80-TCP:V=7.80%I=7%D=9/14%Time=5D7C35ED%P=i686-pc-windows-windows%r(<br /> SF:GetRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(HTTPOptions,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Autho<br /> SF:rization\x20Required\r\n\r\n&quot;)%r(RTSPRequest,32,&quot;HTTP/1\.1\x20470\x20Co<br /> SF:nnection\x20Authorization\x20Required\r\n\r\n&quot;)%r(X11Probe,32,&quot;HTTP/1\.<br /> SF:1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(FourOhF<br /> SF:ourRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(GenericLines,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Auth<br /> SF:orization\x20Required\r\n\r\n&quot;)%r(RPCCheck,32,&quot;HTTP/1\.1\x20470\x20Conn<br /> SF:ection\x20Authorization\x20Required\r\n\r\n&quot;)%r(DNSVersionBindReqTCP,32<br /> SF:,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)<br /> SF:%r(DNSStatusRequestTCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorizat<br /> SF:ion\x20Required\r\n\r\n&quot;)%r(Help,32,&quot;HTTP/1\.1\x20470\x20Connection\x20<br /> SF:Authorization\x20Required\r\n\r\n&quot;)%r(SSLSessionReq,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(TerminalServer<br /> SF:Cookie,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\<br /> SF:r\n\r\n&quot;)%r(TLSSessionReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(Kerberos,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;)%r(SMBProgNeg,32,&quot;HTTP/1\.1\x<br /> SF:20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LPDString,<br /> SF:32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n<br /> SF:&quot;)%r(LDAPSearchReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\<br /> SF:x20Required\r\n\r\n&quot;)%r(LDAPBindReq,32,&quot;HTTP/1\.1\x20470\x20Connection\<br /> SF:x20Authorization\x20Required\r\n\r\n&quot;)%r(SIPOptions,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LANDesk-RC,32,<br /> SF:&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%<br /> SF:r(TerminalServer,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x2<br /> SF:0Required\r\n\r\n&quot;)%r(NCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(NotesRPC,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;);<br /> MAC Address: 44:91:60:25:F5:CB (Murata Manufacturing)<br /> No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).<br /> TCP/IP fingerprint:<br /> OS:SCAN(V=7.80%E=4%D=9/14%OT=80%CT=1%CU=39904%PV=Y%DS=1%DC=D%G=Y%M=449160%T<br /> OS:M=5D7C362E%P=i686-pc-windows-windows)SEQ(CI=I%II=I%TS=U)ECN(R=N)T1(R=Y%D<br /> OS:F=N%T=80%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=80%W=0<br /> OS:%S=A%A=Z%F=R%O=%RD=0%Q=)T5(R=Y%DF=N%T=80%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6<br /> OS:(R=Y%DF=N%T=80%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=N%T=80%W=0%S=Z%A=S+%<br /> OS:F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G<br /> OS:%RUD=G)IE(R=Y%DFI=N%T=80%CD=S)<br /> <br /> Network Distance: 1 hop<br /> <br /> TRACEROUTE<br /> HOP RTT ADDRESS<br /> 1 0.51 ms 10.77.77.6<br /> <br /> NSE: Script Post-scanning.<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Read data files from: C:\Program Files (x86)\Nmap<br /> OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .<br /> Nmap done: 1 IP address (1 host up) scanned in 89.06 seconds<br /> Raw packets sent: 1215 (58.910KB) | Rcvd: 1089 (45.266KB)<br /> <br /> <br /> <br /> <br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2021 2019-09-15T22:39:24Z

<p>StSchmitzhofer: Added pictures from the app setup process</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: [[Tradfri_Gateway|IKEA TRÅDFRI Typ E1526 (Gateway)]], WiFi router <br /> <br /> == Description ==<br /> <br /> [[File:TRADFRI Gateway Opened.jpg|200px|thumb|Gateway opened up and plugged in]]<br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> <br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting IKEA Home Smart (Android App Store)]<br /> * [https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071 IKEA Home Smart (Apple App Store)]<br /> <br /> [[File:Ikea tradfri gateway plugin.png|200px|thumb]]<br /> [[File:Ikea tradfri gateway codescan.png|200px|thumb]]<br /> [[File:Ikea tradfri gateway finished.png|200px|thumb]]<br /> === Step 2: Sync Gateway ===<br /> <br /> Follow the instructions within the app, to finish the process.<br /> <br /> == Used Hardware ==<br /> <br /> Mandadory:<br /> <br /> * [[Tradfri_Gateway]]<br /> <br /> Optional:<br /> <br /> * [[Tradfri_dimmer]]<br /> * [[Tradfri_smart_plug]]<br /> * [[Tradfri_smart_plug_with_button]]<br /> * [[Tradfri_signal_repeater]]<br /> * [[Tradfri_remote_control]]<br /> * [[Tradfri_motion_sensor]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_10_W]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_30_W]]<br /> * [[Tradfri_LED_with_motion_sensor_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_dimmer]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_remote_control]]<br /> * [[Tradfri_LED_400_lm_5.3_W_E14]]<br /> * [[Tradfri_LED_400_lm_5.3_W_GU10]]<br /> * [[Tradfri_LED_950_lm_12_W_E27]]<br /> <br /> <br /> == Alternatives ==<br /> <br /> As of today, there is no '''official''' alternative to the suggested setup via app. A simple nmap scan however reveales an (unencrypted) open '''port 80''' which requires '''authentication''' (HTTP status code 470, no form, nor any HTML).<br /> <br /> → Listening into a live connection (e.g. Wireshark &amp; Android Emulator), might give further insight into other possibilities.<br /> <br /> Nmap scan results:<br /> Starting Nmap 7.80 ( https://nmap.org ) at 2019-09-14 02:35 Mitteleuropäische Sommerzeit<br /> NSE: Loaded 151 scripts for scanning.<br /> NSE: Script Pre-scanning.<br /> ...<br /> Initiating ARP Ping Scan at 02:35<br /> Scanning 10.77.77.6 [1 port]<br /> Completed ARP Ping Scan at 02:35, 0.19s elapsed (1 total hosts)<br /> Initiating Parallel DNS resolution of 1 host. at 02:35<br /> Completed Parallel DNS resolution of 1 host. at 02:35, 11.04s elapsed<br /> Initiating SYN Stealth Scan at 02:35<br /> Scanning 10.77.77.6 [1000 ports]<br /> Discovered open port 80/tcp on 10.77.77.6<br /> Completed SYN Stealth Scan at 02:35, 0.81s elapsed (1000 total ports)<br /> Initiating Service scan at 02:35<br /> Scanning 1 service on 10.77.77.6<br /> Completed Service scan at 02:36, 38.22s elapsed (1 service on 1 host)<br /> ...<br /> Nmap scan report for 10.77.77.6<br /> Host is up (0.00051s latency).<br /> Not shown: 999 closed ports<br /> PORT STATE SERVICE VERSION<br /> 80/tcp open http<br /> | fingerprint-strings: <br /> | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LANDesk-RC, LDAPBindReq, LDAPSearchReq, LPDString, NCP, NotesRPC, RPCCheck, RTSPRequest, SIPOptions, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServer, TerminalServerCookie, X11Probe: <br /> |_ HTTP/1.1 470 Connection Authorization Required<br /> |_http-title: Site doesn't have a title.<br /> 1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :<br /> SF-Port80-TCP:V=7.80%I=7%D=9/14%Time=5D7C35ED%P=i686-pc-windows-windows%r(<br /> SF:GetRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(HTTPOptions,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Autho<br /> SF:rization\x20Required\r\n\r\n&quot;)%r(RTSPRequest,32,&quot;HTTP/1\.1\x20470\x20Co<br /> SF:nnection\x20Authorization\x20Required\r\n\r\n&quot;)%r(X11Probe,32,&quot;HTTP/1\.<br /> SF:1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(FourOhF<br /> SF:ourRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(GenericLines,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Auth<br /> SF:orization\x20Required\r\n\r\n&quot;)%r(RPCCheck,32,&quot;HTTP/1\.1\x20470\x20Conn<br /> SF:ection\x20Authorization\x20Required\r\n\r\n&quot;)%r(DNSVersionBindReqTCP,32<br /> SF:,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)<br /> SF:%r(DNSStatusRequestTCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorizat<br /> SF:ion\x20Required\r\n\r\n&quot;)%r(Help,32,&quot;HTTP/1\.1\x20470\x20Connection\x20<br /> SF:Authorization\x20Required\r\n\r\n&quot;)%r(SSLSessionReq,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(TerminalServer<br /> SF:Cookie,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\<br /> SF:r\n\r\n&quot;)%r(TLSSessionReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(Kerberos,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;)%r(SMBProgNeg,32,&quot;HTTP/1\.1\x<br /> SF:20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LPDString,<br /> SF:32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n<br /> SF:&quot;)%r(LDAPSearchReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\<br /> SF:x20Required\r\n\r\n&quot;)%r(LDAPBindReq,32,&quot;HTTP/1\.1\x20470\x20Connection\<br /> SF:x20Authorization\x20Required\r\n\r\n&quot;)%r(SIPOptions,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LANDesk-RC,32,<br /> SF:&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%<br /> SF:r(TerminalServer,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x2<br /> SF:0Required\r\n\r\n&quot;)%r(NCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(NotesRPC,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;);<br /> MAC Address: 44:91:60:25:F5:CB (Murata Manufacturing)<br /> No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).<br /> TCP/IP fingerprint:<br /> OS:SCAN(V=7.80%E=4%D=9/14%OT=80%CT=1%CU=39904%PV=Y%DS=1%DC=D%G=Y%M=449160%T<br /> OS:M=5D7C362E%P=i686-pc-windows-windows)SEQ(CI=I%II=I%TS=U)ECN(R=N)T1(R=Y%D<br /> OS:F=N%T=80%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=80%W=0<br /> OS:%S=A%A=Z%F=R%O=%RD=0%Q=)T5(R=Y%DF=N%T=80%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6<br /> OS:(R=Y%DF=N%T=80%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=N%T=80%W=0%S=Z%A=S+%<br /> OS:F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G<br /> OS:%RUD=G)IE(R=Y%DFI=N%T=80%CD=S)<br /> <br /> Network Distance: 1 hop<br /> <br /> TRACEROUTE<br /> HOP RTT ADDRESS<br /> 1 0.51 ms 10.77.77.6<br /> <br /> NSE: Script Post-scanning.<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Read data files from: C:\Program Files (x86)\Nmap<br /> OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .<br /> Nmap done: 1 IP address (1 host up) scanned in 89.06 seconds<br /> Raw packets sent: 1215 (58.910KB) | Rcvd: 1089 (45.266KB)<br /> <br /> <br /> <br /> <br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:Ikea_tradfri_gateway_plugin.png&diff=2020 2019-09-15T22:32:21Z

<p>StSchmitzhofer: </p> <hr /> <div></div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:Ikea_tradfri_gateway_codescan.png&diff=2019 2019-09-15T22:31:25Z

<p>StSchmitzhofer: </p> <hr /> <div></div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:Ikea_tradfri_gateway_finished.png&diff=2018 2019-09-15T22:30:56Z

<p>StSchmitzhofer: </p> <hr /> <div></div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2017 2019-09-14T01:31:40Z

<p>StSchmitzhofer: </p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: [[Tradfri_Gateway|IKEA TRÅDFRI Typ E1526 (Gateway)]], WiFi router <br /> <br /> == Description ==<br /> <br /> [[File:TRADFRI Gateway Opened.jpg|200px|thumb|Gateway opened up and plugged in]]<br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> <br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting IKEA Home Smart (Android App Store)]<br /> * [https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071 IKEA Home Smart (Apple App Store)]<br /> <br /> Follow the instructions within the app.<br /> <br /> == Used Hardware ==<br /> <br /> Mandadory:<br /> <br /> * [[Tradfri_Gateway]]<br /> <br /> Optional:<br /> <br /> * [[Tradfri_dimmer]]<br /> * [[Tradfri_smart_plug]]<br /> * [[Tradfri_smart_plug_with_button]]<br /> * [[Tradfri_signal_repeater]]<br /> * [[Tradfri_remote_control]]<br /> * [[Tradfri_motion_sensor]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_10_W]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_30_W]]<br /> * [[Tradfri_LED_with_motion_sensor_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_dimmer]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_remote_control]]<br /> * [[Tradfri_LED_400_lm_5.3_W_E14]]<br /> * [[Tradfri_LED_400_lm_5.3_W_GU10]]<br /> * [[Tradfri_LED_950_lm_12_W_E27]]<br /> <br /> <br /> == Alternatives ==<br /> <br /> As of today, there is no '''official''' alternative to the suggested setup via app. A simple nmap scan however reveales an (unencrypted) open '''port 80''' which requires '''authentication''' (HTTP status code 470, no form, nor any HTML).<br /> <br /> → Listening into a live connection (e.g. Wireshark &amp; Android Emulator), might give further insight into other possibilities.<br /> <br /> Nmap scan results:<br /> Starting Nmap 7.80 ( https://nmap.org ) at 2019-09-14 02:35 Mitteleuropäische Sommerzeit<br /> NSE: Loaded 151 scripts for scanning.<br /> NSE: Script Pre-scanning.<br /> ...<br /> Initiating ARP Ping Scan at 02:35<br /> Scanning 10.77.77.6 [1 port]<br /> Completed ARP Ping Scan at 02:35, 0.19s elapsed (1 total hosts)<br /> Initiating Parallel DNS resolution of 1 host. at 02:35<br /> Completed Parallel DNS resolution of 1 host. at 02:35, 11.04s elapsed<br /> Initiating SYN Stealth Scan at 02:35<br /> Scanning 10.77.77.6 [1000 ports]<br /> Discovered open port 80/tcp on 10.77.77.6<br /> Completed SYN Stealth Scan at 02:35, 0.81s elapsed (1000 total ports)<br /> Initiating Service scan at 02:35<br /> Scanning 1 service on 10.77.77.6<br /> Completed Service scan at 02:36, 38.22s elapsed (1 service on 1 host)<br /> ...<br /> Nmap scan report for 10.77.77.6<br /> Host is up (0.00051s latency).<br /> Not shown: 999 closed ports<br /> PORT STATE SERVICE VERSION<br /> 80/tcp open http<br /> | fingerprint-strings: <br /> | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LANDesk-RC, LDAPBindReq, LDAPSearchReq, LPDString, NCP, NotesRPC, RPCCheck, RTSPRequest, SIPOptions, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServer, TerminalServerCookie, X11Probe: <br /> |_ HTTP/1.1 470 Connection Authorization Required<br /> |_http-title: Site doesn't have a title.<br /> 1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :<br /> SF-Port80-TCP:V=7.80%I=7%D=9/14%Time=5D7C35ED%P=i686-pc-windows-windows%r(<br /> SF:GetRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(HTTPOptions,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Autho<br /> SF:rization\x20Required\r\n\r\n&quot;)%r(RTSPRequest,32,&quot;HTTP/1\.1\x20470\x20Co<br /> SF:nnection\x20Authorization\x20Required\r\n\r\n&quot;)%r(X11Probe,32,&quot;HTTP/1\.<br /> SF:1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(FourOhF<br /> SF:ourRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(GenericLines,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Auth<br /> SF:orization\x20Required\r\n\r\n&quot;)%r(RPCCheck,32,&quot;HTTP/1\.1\x20470\x20Conn<br /> SF:ection\x20Authorization\x20Required\r\n\r\n&quot;)%r(DNSVersionBindReqTCP,32<br /> SF:,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)<br /> SF:%r(DNSStatusRequestTCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorizat<br /> SF:ion\x20Required\r\n\r\n&quot;)%r(Help,32,&quot;HTTP/1\.1\x20470\x20Connection\x20<br /> SF:Authorization\x20Required\r\n\r\n&quot;)%r(SSLSessionReq,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(TerminalServer<br /> SF:Cookie,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\<br /> SF:r\n\r\n&quot;)%r(TLSSessionReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(Kerberos,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;)%r(SMBProgNeg,32,&quot;HTTP/1\.1\x<br /> SF:20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LPDString,<br /> SF:32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n<br /> SF:&quot;)%r(LDAPSearchReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\<br /> SF:x20Required\r\n\r\n&quot;)%r(LDAPBindReq,32,&quot;HTTP/1\.1\x20470\x20Connection\<br /> SF:x20Authorization\x20Required\r\n\r\n&quot;)%r(SIPOptions,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LANDesk-RC,32,<br /> SF:&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%<br /> SF:r(TerminalServer,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x2<br /> SF:0Required\r\n\r\n&quot;)%r(NCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(NotesRPC,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;);<br /> MAC Address: 44:91:60:25:F5:CB (Murata Manufacturing)<br /> No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).<br /> TCP/IP fingerprint:<br /> OS:SCAN(V=7.80%E=4%D=9/14%OT=80%CT=1%CU=39904%PV=Y%DS=1%DC=D%G=Y%M=449160%T<br /> OS:M=5D7C362E%P=i686-pc-windows-windows)SEQ(CI=I%II=I%TS=U)ECN(R=N)T1(R=Y%D<br /> OS:F=N%T=80%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=80%W=0<br /> OS:%S=A%A=Z%F=R%O=%RD=0%Q=)T5(R=Y%DF=N%T=80%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6<br /> OS:(R=Y%DF=N%T=80%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=N%T=80%W=0%S=Z%A=S+%<br /> OS:F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G<br /> OS:%RUD=G)IE(R=Y%DFI=N%T=80%CD=S)<br /> <br /> Network Distance: 1 hop<br /> <br /> TRACEROUTE<br /> HOP RTT ADDRESS<br /> 1 0.51 ms 10.77.77.6<br /> <br /> NSE: Script Post-scanning.<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Read data files from: C:\Program Files (x86)\Nmap<br /> OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .<br /> Nmap done: 1 IP address (1 host up) scanned in 89.06 seconds<br /> Raw packets sent: 1215 (58.910KB) | Rcvd: 1089 (45.266KB)<br /> <br /> <br /> <br /> <br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2016 2019-09-14T01:27:35Z

<p>StSchmitzhofer: Added NMAP scan, as well as results of checking for setup alternatives</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: [[Tradfri_Gateway|IKEA TRÅDFRI Typ E1526 (Gateway)]], WiFi router <br /> <br /> == Description ==<br /> <br /> [[File:TRADFRI Gateway Opened.jpg|200px|thumb|Gateway opened up and plugged in]]<br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> <br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting IKEA Home Smart (Android App Store)]<br /> * [https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071 IKEA Home Smart (Apple App Store)]<br /> <br /> Follow the instructions within the app.<br /> <br /> == Used Hardware ==<br /> <br /> Mandadory:<br /> <br /> * [[Tradfri_Gateway]]<br /> <br /> Optional:<br /> <br /> * [[Tradfri_dimmer]]<br /> * [[Tradfri_smart_plug]]<br /> * [[Tradfri_smart_plug_with_button]]<br /> * [[Tradfri_signal_repeater]]<br /> * [[Tradfri_remote_control]]<br /> * [[Tradfri_motion_sensor]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_10_W]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_30_W]]<br /> * [[Tradfri_LED_with_motion_sensor_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_dimmer]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_remote_control]]<br /> * [[Tradfri_LED_400_lm_5.3_W_E14]]<br /> * [[Tradfri_LED_400_lm_5.3_W_GU10]]<br /> * [[Tradfri_LED_950_lm_12_W_E27]]<br /> <br /> <br /> == Possible Alternatvie Methods ==<br /> <br /> As of today, there is no '''official''' alternative to the suggested setup via app. A simple nmap scan however reveales an (unencrypted) open '''port 80''' which requires '''authentication''' (HTTP status code 470, no form, nor any HTML).<br /> <br /> → Listening into a live connection (e.g. Wireshark &amp; Android Emulator), might give further insight into other possibilities.<br /> <br /> Nmap scan results:<br /> Starting Nmap 7.80 ( https://nmap.org ) at 2019-09-14 02:35 Mitteleuropäische Sommerzeit<br /> NSE: Loaded 151 scripts for scanning.<br /> NSE: Script Pre-scanning.<br /> ...<br /> Initiating ARP Ping Scan at 02:35<br /> Scanning 10.77.77.6 [1 port]<br /> Completed ARP Ping Scan at 02:35, 0.19s elapsed (1 total hosts)<br /> Initiating Parallel DNS resolution of 1 host. at 02:35<br /> Completed Parallel DNS resolution of 1 host. at 02:35, 11.04s elapsed<br /> Initiating SYN Stealth Scan at 02:35<br /> Scanning 10.77.77.6 [1000 ports]<br /> Discovered open port 80/tcp on 10.77.77.6<br /> Completed SYN Stealth Scan at 02:35, 0.81s elapsed (1000 total ports)<br /> Initiating Service scan at 02:35<br /> Scanning 1 service on 10.77.77.6<br /> Completed Service scan at 02:36, 38.22s elapsed (1 service on 1 host)<br /> ...<br /> Nmap scan report for 10.77.77.6<br /> Host is up (0.00051s latency).<br /> Not shown: 999 closed ports<br /> PORT STATE SERVICE VERSION<br /> 80/tcp open http<br /> | fingerprint-strings: <br /> | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LANDesk-RC, LDAPBindReq, LDAPSearchReq, LPDString, NCP, NotesRPC, RPCCheck, RTSPRequest, SIPOptions, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServer, TerminalServerCookie, X11Probe: <br /> |_ HTTP/1.1 470 Connection Authorization Required<br /> |_http-title: Site doesn't have a title.<br /> 1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :<br /> SF-Port80-TCP:V=7.80%I=7%D=9/14%Time=5D7C35ED%P=i686-pc-windows-windows%r(<br /> SF:GetRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(HTTPOptions,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Autho<br /> SF:rization\x20Required\r\n\r\n&quot;)%r(RTSPRequest,32,&quot;HTTP/1\.1\x20470\x20Co<br /> SF:nnection\x20Authorization\x20Required\r\n\r\n&quot;)%r(X11Probe,32,&quot;HTTP/1\.<br /> SF:1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(FourOhF<br /> SF:ourRequest,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Requi<br /> SF:red\r\n\r\n&quot;)%r(GenericLines,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Auth<br /> SF:orization\x20Required\r\n\r\n&quot;)%r(RPCCheck,32,&quot;HTTP/1\.1\x20470\x20Conn<br /> SF:ection\x20Authorization\x20Required\r\n\r\n&quot;)%r(DNSVersionBindReqTCP,32<br /> SF:,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)<br /> SF:%r(DNSStatusRequestTCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorizat<br /> SF:ion\x20Required\r\n\r\n&quot;)%r(Help,32,&quot;HTTP/1\.1\x20470\x20Connection\x20<br /> SF:Authorization\x20Required\r\n\r\n&quot;)%r(SSLSessionReq,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(TerminalServer<br /> SF:Cookie,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\<br /> SF:r\n\r\n&quot;)%r(TLSSessionReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(Kerberos,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;)%r(SMBProgNeg,32,&quot;HTTP/1\.1\x<br /> SF:20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LPDString,<br /> SF:32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n<br /> SF:&quot;)%r(LDAPSearchReq,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\<br /> SF:x20Required\r\n\r\n&quot;)%r(LDAPBindReq,32,&quot;HTTP/1\.1\x20470\x20Connection\<br /> SF:x20Authorization\x20Required\r\n\r\n&quot;)%r(SIPOptions,32,&quot;HTTP/1\.1\x2047<br /> SF:0\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%r(LANDesk-RC,32,<br /> SF:&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x20Required\r\n\r\n&quot;)%<br /> SF:r(TerminalServer,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authorization\x2<br /> SF:0Required\r\n\r\n&quot;)%r(NCP,32,&quot;HTTP/1\.1\x20470\x20Connection\x20Authori<br /> SF:zation\x20Required\r\n\r\n&quot;)%r(NotesRPC,32,&quot;HTTP/1\.1\x20470\x20Connect<br /> SF:ion\x20Authorization\x20Required\r\n\r\n&quot;);<br /> MAC Address: 44:91:60:25:F5:CB (Murata Manufacturing)<br /> No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).<br /> TCP/IP fingerprint:<br /> OS:SCAN(V=7.80%E=4%D=9/14%OT=80%CT=1%CU=39904%PV=Y%DS=1%DC=D%G=Y%M=449160%T<br /> OS:M=5D7C362E%P=i686-pc-windows-windows)SEQ(CI=I%II=I%TS=U)ECN(R=N)T1(R=Y%D<br /> OS:F=N%T=80%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=80%W=0<br /> OS:%S=A%A=Z%F=R%O=%RD=0%Q=)T5(R=Y%DF=N%T=80%W=0%S=Z%A=S+%F=AR%O=%RD=0%Q=)T6<br /> OS:(R=Y%DF=N%T=80%W=0%S=A%A=Z%F=R%O=%RD=0%Q=)T7(R=Y%DF=N%T=80%W=0%S=Z%A=S+%<br /> OS:F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G<br /> OS:%RUD=G)IE(R=Y%DFI=N%T=80%CD=S)<br /> <br /> Network Distance: 1 hop<br /> <br /> TRACEROUTE<br /> HOP RTT ADDRESS<br /> 1 0.51 ms 10.77.77.6<br /> <br /> NSE: Script Post-scanning.<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Initiating NSE at 02:37<br /> Completed NSE at 02:37, 0.00s elapsed<br /> Read data files from: C:\Program Files (x86)\Nmap<br /> OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .<br /> Nmap done: 1 IP address (1 host up) scanned in 89.06 seconds<br /> Raw packets sent: 1215 (58.910KB) | Rcvd: 1089 (45.266KB)<br /> <br /> <br /> <br /> <br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2015 2019-09-14T00:29:51Z

<p>StSchmitzhofer: Added &quot;Used Hardware&quot;, picture showing the plugged in device, App links as text</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: [[Tradfri_Gateway|IKEA TRÅDFRI Typ E1526 (Gateway)]], WiFi router <br /> <br /> == Description ==<br /> <br /> [[File:TRADFRI Gateway Opened.jpg|200px|thumb|Gateway opened up and plugged in]]<br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> <br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * [https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting IKEA Home Smart (Android App Store)]<br /> * [https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071 IKEA Home Smart (Apple App Store)]<br /> <br /> Follow the instructions within the app.<br /> <br /> == Used Hardware ==<br /> <br /> Mandadory:<br /> <br /> * [[Tradfri_Gateway]]<br /> <br /> Optional:<br /> <br /> * [[Tradfri_dimmer]]<br /> * [[Tradfri_smart_plug]]<br /> * [[Tradfri_smart_plug_with_button]]<br /> * [[Tradfri_signal_repeater]]<br /> * [[Tradfri_remote_control]]<br /> * [[Tradfri_motion_sensor]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_10_W]]<br /> * [[Tradfri_Led_power_supply_with_wireless_receiver_30_W]]<br /> * [[Tradfri_LED_with_motion_sensor_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_dimmer]]<br /> * [[Tradfri_LED_1000_lm_12.5_W_E27_with_remote_control]]<br /> * [[Tradfri_LED_400_lm_5.3_W_E14]]<br /> * [[Tradfri_LED_400_lm_5.3_W_GU10]]<br /> * [[Tradfri_LED_950_lm_12_W_E27]]<br /> <br /> <br /> == Courses ==<br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=File:TRADFRI_Gateway_Opened.jpg&diff=2014 2019-09-14T00:06:27Z

<p>StSchmitzhofer: TRADFRI Gateway with network cable, as well as power supply plugged in</p> <hr /> <div>== Summary ==<br /> TRADFRI Gateway with network cable, as well as power supply plugged in</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Complete_Setup&diff=2013 2019-09-14T00:00:47Z

<p>StSchmitzhofer: StSchmitzhofer moved page IKEA TRÅDFRI: Complete Setup to IKEA TRÅDFRI: Basic Setup</p> <hr /> <div>#REDIRECT [[IKEA TRÅDFRI: Basic Setup]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2012 2019-09-14T00:00:47Z

<p>StSchmitzhofer: StSchmitzhofer moved page IKEA TRÅDFRI: Complete Setup to IKEA TRÅDFRI: Basic Setup</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: IKEA TRÅDFRI Typ E1526 (Gateway), WiFi router <br /> <br /> == Description ==<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * Android: https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * iOS: https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> Follow the instructions within the app.<br /> <br /> == Used Hardware ==<br /> <br /> [[Tradfri_Gateway]]<br /> <br /> == Courses ==<br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2011 2019-09-13T18:01:33Z

<p>StSchmitzhofer: </p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: IKEA TRÅDFRI Typ E1526 (Gateway), WiFi router <br /> <br /> == Description ==<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * Android: https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * iOS: https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> Follow the instructions within the app.<br /> <br /> == Used Hardware ==<br /> <br /> [[Tradfri_Gateway]]<br /> <br /> == Courses ==<br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer https://elvis.hcw.ac.at/wiki/index.php?title=IKEA_TR%C3%85DFRI:_Basic_Setup&diff=2010 2019-09-13T18:01:14Z

<p>StSchmitzhofer: Created Basic Setup Documentation</p> <hr /> <div>== Summary == <br /> <br /> This documentation describes how to set up IKEA TRÅDFRI<br /> <br /> == Requirements ==<br /> <br /> * A mobile device running either Android 4.1 or later, or iOS 9.0 or later<br /> * Hardware: IKEA TRÅDFRI Typ E1526 (Gateway), WiFi router <br /> <br /> == Description ==<br /> <br /> === Step 1: Hardware Setup ===<br /> <br /> * Connect the TRÅDFRI to your router, using a straight network cable<br /> * Connect the micro usb power cable into the TRÅDFRI, and plug it in<br /> <br /> echo foo<br /> echo bar<br /> <br /> === Step 2: Home Smart App ===<br /> <br /> In order to set up your TRÅDFRI, you are required to install the IKEA Home Smart App either for Android or iOS:<br /> <br /> * Android: https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * iOS: https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> Follow the instructions within the app.<br /> <br /> == Used Hardware ==<br /> <br /> [[Tradfri_Gateway]]<br /> <br /> == Courses ==<br /> <br /> == References ==<br /> <br /> * https://play.google.com/store/apps/details?id=com.ikea.tradfri.lighting<br /> * https://apps.apple.com/us/app/ikea-home-smart-trådfri/id1195836071<br /> <br /> [[Category:Documentation]]</div>

StSchmitzhofer