Getting Started - Revision history

Dvdakker: /* Configuration of Access Point */

2025-07-28T09:49:48Z

Configuration of Access Point

← Older revision		Revision as of 09:49, 28 July 2025
Line 33:		Line 33:

	=== Configuration of Access Point ===		=== Configuration of Access Point ===
	SSH to your AP node (double click it in jFed). Become root:		SSH to your AP node (double click it in jFed). '''Important''': For security purposes, the Citylab nodes are '''only''' accessible via the SSH proxy. Make sure it is enabled before you try to login to them !!

			Become root:

	<code>sudo su</code>		<code>sudo su</code>

Dvdakker at 12:53, 5 April 2023

2023-04-05T12:53:59Z

← Older revision		Revision as of 12:53, 5 April 2023
Line 98:		Line 98:
	The overlay consists of colour-coded lines that give a visual clue of how good or bad a certain wireless link is. The lines themselves are also clickable, showing you the details of the link conditions. Do note that these figures come from a specially designed experiment to measure the link conditions. As these link conditions are also affected by external factors, they might change. You may also notice that some nodes appear not to have any links to any other nodes. This simply means that the link conditions have not been measured since this node was added. We do occasionally re-measure the link conditions but since we have to reserve ''all'' the nodes in the testbed for an entire weekend to do so, we don't want to do this too often. In essence: You can use this node map as a guide, but do not consider it to be absolute reality...		The overlay consists of colour-coded lines that give a visual clue of how good or bad a certain wireless link is. The lines themselves are also clickable, showing you the details of the link conditions. Do note that these figures come from a specially designed experiment to measure the link conditions. As these link conditions are also affected by external factors, they might change. You may also notice that some nodes appear not to have any links to any other nodes. This simply means that the link conditions have not been measured since this node was added. We do occasionally re-measure the link conditions but since we have to reserve ''all'' the nodes in the testbed for an entire weekend to do so, we don't want to do this too often. In essence: You can use this node map as a guide, but do not consider it to be absolute reality...
	<iframe key="docs" path="nodemap/?embed=1" width="100%" height="800" />		<iframe key="docs" path="nodemap/?embed=1" width="100%" height="800" />

			== Embedded Radios ==

			Once you've managed to start your first experiment, check out the [[Embedded Radios Quick Start Guide]] for more information on how to start using those.

	== Troubleshooting ==		== Troubleshooting ==

Dvdakker: /* JFed Account */

2021-04-08T08:43:54Z

JFed Account

← Older revision		Revision as of 08:43, 8 April 2021
Line 8:		Line 8:
	If you join a JFed-project that has already been authorised, you will automatically also be granted access to the Citylab testbed. If you create a new JFed-project for your experiments, you can request for it to be authorised by sending an e-mail to {{SafeMailTo\|admin\|lab.cityofthings.eu}}, explaining why your projects need access to the testbed. Once your project has been authorised, any new members you add to your project will automatically also be granted access.		If you join a JFed-project that has already been authorised, you will automatically also be granted access to the Citylab testbed. If you create a new JFed-project for your experiments, you can request for it to be authorised by sending an e-mail to {{SafeMailTo\|admin\|lab.cityofthings.eu}}, explaining why your projects need access to the testbed. Once your project has been authorised, any new members you add to your project will automatically also be granted access.

	Please note that if you create a new JFed-project during signup both the application for a jFed account as well as the authorisation of your JFed-project must be approved. The Citylab administrators are not automatically notified of the fact that you created a new project. You have to ask for it to be authorised yourself by sending an e-mail to {{SafeMailTo\|admin\|lab.cityofthings.eu}}. As long as you did not receive confirmation of both approvals, you are not ready to start using the testbed.		Please note that if you create a new JFed-project during signup both the application for a jFed account as well as the authorisation of your JFed-project must be approved. The Citylab administrators are '''not''' automatically notified of the fact that you created a new project. You have to ask for it to be authorised yourself by sending an e-mail to {{SafeMailTo\|admin\|lab.cityofthings.eu}}. As long as you did not receive confirmation of both approvals, you are not ready to start using the testbed.

	=== JFed Software ===		=== JFed Software ===

Dvdakker: /* Prerequisites */

2021-01-22T09:25:54Z

Prerequisites

← Older revision		Revision as of 09:25, 22 January 2021
Line 1:		Line 1:
	== Prerequisites ==		== Prerequisites ==

			=== JFed Account ===
	To access the CityLab testbed you need:		To access the CityLab testbed you need:
	* A ~~JFed account from the~~ [https://~~authority~~.~~ilabt~~.~~iminds.be Legacy iMinds User Authority~~]. If you do not have one, you ~~can~~ request one [https://~~authority~~.~~ilabt~~.~~iminds.be~~/~~signup~~.~~php~~ here] ~~(make sure the fill in '<i>CityOfThings</i>' as the project name)~~.		* A [https://portal.fed4fire.eu JFed account]. If you do not have one already, you will have to request one. How this is done is explained [https://doc.fed4fire.eu/getanaccount.html here].
	* You must be a member of the ~~'CityOfThings' project~~.		* You must be a member of a JFed-project that is authorised to run experiments on the Citylab testbed.

	~~Both the application for~~ a ~~jFed account as the membership request for the CityOfThings~~ project ~~must~~ be ~~approved~~. ~~As longs as~~ you ~~did not get~~ a ~~confirmation email of both approvals~~, you ~~are not ready~~ to ~~start using~~ the testbed!		If you join a JFed-project that has already been authorised, you will automatically also be granted access to the Citylab testbed. If you create a new JFed-project for your experiments, you can request for it to be authorised by sending an e-mail to {{SafeMailTo\|admin\|lab.cityofthings.eu}}, explaining why your projects need access to the testbed. Once your project has been authorised, any new members you add to your project will automatically also be granted access.

	~~=== Get~~ a JFed account ~~===~~		Please note that if you create a new JFed-project during signup both the application for a jFed account as well as the authorisation of your JFed-project must be approved. The Citylab administrators are not automatically notified of the fact that you created a new project. You have to ask for it to be authorised yourself by sending an e-mail to {{SafeMailTo\|admin\|lab.cityofthings.eu}}. As long as you did not receive confirmation of both approvals, you are not ready to start using the testbed.
	~~You~~ must ~~have an account at~~ the ~~legacy iMinds user authority~~. ~~If you do not~~ have ~~one, go~~ to ~~the [https://authority~~.~~ilabt~~.~~iminds~~.~~be IMEC User Authority] website and sign up for one. While signing up~~, you ~~can immediately also request~~ to ~~be a member of~~ the ~~''CityOfThings'' project (written exactly like this)~~.

	=== ~~Get the~~ JFed ~~software~~ ===		=== JFed Software ===
	You also need to have the JFed software installed on your computer. You can do this before or after you create your JFed account. Go to [https://jfed.ilabt.imec.be https://jfed.ilabt.imec.be] and download the appropriate installer for your operating system. On that website, you can also find some documentation on how to use this software (e.g. regarding certificates).		You also need to have the JFed software installed on your computer. You can do this before or after you create your JFed account. Go to [https://jfed.ilabt.imec.be/downloads/ https://jfed.ilabt.imec.be/downloads/] and download the appropriate installer for your operating system. On that website, you can also find some documentation on how to use this software (e.g. regarding certificates).

	== Using the testbed for the first time ==		== Using the testbed for the first time ==

Dvdakker: /* Prerequisites */

2020-11-03T09:47:26Z

Prerequisites

← Older revision		Revision as of 09:47, 3 November 2020
Line 2:		Line 2:

	To access the CityLab testbed you need:		To access the CityLab testbed you need:
	* A JFed account from the [https://authority.ilabt.iminds.be ~~IMEC~~ User Authority]. If you do not have one, you can request one [https://authority.ilabt.iminds.be/signup.php here] (make sure the fill in '<i>CityOfThings</i>' as the project name).		* A JFed account from the [https://authority.ilabt.iminds.be Legacy iMinds User Authority]. If you do not have one, you can request one [https://authority.ilabt.iminds.be/signup.php here] (make sure the fill in '<i>CityOfThings</i>' as the project name).
	* You must be a member of the 'CityOfThings' project.		* You must be a member of the 'CityOfThings' project.

Line 8:		Line 8:

	=== Get a JFed account ===		=== Get a JFed account ===
	You must have an account at the ~~IMEC~~ user authority. If you do not have one, go to the [https://authority.ilabt.iminds.be IMEC User Authority] website and sign up for one. While signing up, you can immediately also request to be a member of the ''CityOfThings'' project (written exactly like this).		You must have an account at the legacy iMinds user authority. If you do not have one, go to the [https://authority.ilabt.iminds.be IMEC User Authority] website and sign up for one. While signing up, you can immediately also request to be a member of the ''CityOfThings'' project (written exactly like this).

	=== Get the JFed software ===		=== Get the JFed software ===

Bbraem: /* Create and activate your experiment using jFed */

2019-08-14T07:32:39Z

Create and activate your experiment using jFed

← Older revision		Revision as of 07:32, 14 August 2019
Line 22:		Line 22:
	[[File:jfed_experiment.png\|Drag in 3 wireless nodes\|480px]]		[[File:jfed_experiment.png\|Drag in 3 wireless nodes\|480px]]
	* Configure which nodes you want to use:		* Configure which nodes you want to use:
	** Click the node, and select ''~~City of Things~~ Antwerp''. By default, WiLab2 is selected.		** Click the node, and select ''imec CityLab Antwerp''. By default, WiLab2 is selected.
	** Click on ''specific node''and select a node there. '''Make sure you check on the map to select nodes that are in reach of each other!''' The CityLab nodes can be far away from each other, so if you don't pay attention, you will end up with an experiment that does not support wireless communication between the selected nodes! See [[#Using the node map\|using the node map]] for more information.		** Click on ''specific node''and select a node there. '''Make sure you check on the map to select nodes that are in reach of each other!''' The CityLab nodes can be far away from each other, so if you don't pay attention, you will end up with an experiment that does not support wireless communication between the selected nodes! See [[#Using the node map\|using the node map]] for more information.
	[[File:jfed_select_nodes.png\|Select the appropriate nodes\|480px]]		[[File:jfed_select_nodes.png\|Select the appropriate nodes\|480px]]

Dvdakker: /* The City of Things testbed does not appear in the list of testbeds */

2018-05-03T08:04:06Z

The City of Things testbed does not appear in the list of testbeds

← Older revision		Revision as of 08:04, 3 May 2018
Line 100:		Line 100:

	== Troubleshooting ==		== Troubleshooting ==
	~~=== The ''City of Things'' testbed does not appear in the list of testbeds ===~~

	You probably forgot to enable the 'dev-testbeds' GUI option. See the [[#Create and activate your experiment using jFed\|Create and activate your experiment using jFed]] section for information on how to enable this option.

	=== Working around connectivity issues ===		=== Working around connectivity issues ===

Dvdakker: /* Create and activate your experiment using jFed */

2018-05-03T08:03:49Z

Create and activate your experiment using jFed

← Older revision		Revision as of 08:03, 3 May 2018
Line 18:		Line 18:
	* Fire up jFed. If all goes well, you should be prompted to provide your User certificate and Password. Browse to the location where you stored the .pem-file (see jFed documentation regarding certificates), provide your password and click Login.		* Fire up jFed. If all goes well, you should be prompted to provide your User certificate and Password. Browse to the location where you stored the .pem-file (see jFed documentation regarding certificates), provide your password and click Login.
	[[File:jfed_login.png\|Log in\|480px]]		[[File:jfed_login.png\|Log in\|480px]]
	* If this is the first time you are using jFed to activate nodes in the CityLab testbed, the 'dev-testbeds' GUI-option needs to be enabled. Click on ''Preferences'', select the ''GUI Editor'' tab and enter <code>dev-testbeds</code> in the ''Extra Flags'' field. Click ''Save'' and then restart JFed, so this setting can take effect.
	~~[[File:Jfed_GUI_settings.png]]~~
	* Click on New		* Click on New
	* Drag in 3 wireless nodes.		* Drag in 3 wireless nodes.

Dvdakker: /* Configuration of stations */

2018-03-14T14:07:05Z

Configuration of stations

← Older revision		Revision as of 14:07, 14 March 2018
Line 79:		Line 79:

	Put the wireless interface into managed mode and start the wpa_supplicant tool to connect to the AP.		Put the wireless interface into managed mode and start the wpa_supplicant tool to connect to the AP.
	<~~pre~~>iwconfig wlp1s0 mode managed
	wpa_supplicant -iwlp1s0 -c/root/wpa_supplicant.conf</~~pre~~>		<code>iwconfig wlp1s0 mode managed</code>

			<code>wpa_supplicant -iwlp1s0 -c/root/wpa_supplicant.conf</code>

	Open a second ssh terminal and specify an IP address for the wlp1s0 interface:		Open a second ssh terminal and specify an IP address for the wlp1s0 interface:
	~~Specify an IP address and bring up the interface:~~
	<code>ifconfig wlan0 192.168.X.Z/24 up</code>		<code>sudo su; ifconfig wlan0 192.168.X.Z/24</code>

	make sure Z is not 1 and is different on both stations. Now, check if you can ping from one station to the other.		make sure Z is not 1 and is different on both stations. Now, check if you can ping from one station to the other.

Dvdakker: /* Configuration of stations */

2018-03-14T14:05:07Z

Configuration of stations

← Older revision		Revision as of 14:05, 14 March 2018
Line 72:		Line 72:
	<code>sudo su</code>		<code>sudo su</code>

	~~Put~~ the ~~wireless interface into managed mode and specify the SSID so it knows to which AP it should connect~~		Create a config file for the wpa_supplicant program:

			<code>wpa_passphrase demoX PWD >/root/wpa_supplicant.conf</code>

			In the above command replace demoX and PWD with the SSID and WPA2 password you configured in the hostapd.conf file on the access point.

			Put the wireless interface into managed mode and start the wpa_supplicant tool to connect to the AP.
	<pre>iwconfig wlp1s0 mode managed		<pre>iwconfig wlp1s0 mode managed
	~~iwconfig wlp1s0 essid demoX~~</pre>		wpa_supplicant -iwlp1s0 -c/root/wpa_supplicant.conf</pre>

			Open a second ssh terminal and specify an IP address for the wlp1s0 interface:
	Specify an IP address and bring up the interface:		Specify an IP address and bring up the interface:

	<code>ifconfig wlan0 192.168.X.Z/24 up</code>		<code>ifconfig wlan0 192.168.X.Z/24 up</code>

	make sure Z is not 1 and is different on both stations. Now, check if you can ping from one station to the other.		make sure Z is not 1 and is different on both stations. Now, check if you can ping from one station to the other.



	== Using the node map ==		== Using the node map ==