Network setup - Revision history

Jca: /* Alternative */

2026-07-13T07:24:43Z

Alternative

← Older revision		Revision as of 09:24, 13 July 2026
Line 73:		Line 73:
	ping 192.168.7.7		ping 192.168.7.7

	==== ~~Alternative~~ ====		==== DHCP with static IP fallback ====

	I found this method (Google AI) to use DHCP with higher priority, and then static IP if DHCP fails		I found this method (Google AI) to use DHCP with higher priority, and then a static IP if DHCP fails

	sudo nmcli connection add type ethernet con-name "Wired-DHCP" ifname eth0 ipv4.method auto autoconnect yes connect.autoconnect-priority 1		sudo nmcli connection add type ethernet con-name "Wired-DHCP" ifname eth0 ipv4.method auto autoconnect yes connect.autoconnect-priority 1
Line 116:		Line 116:

	[ipv4]		[ipv4]
	address1=192.168.7.7/24,192.168.7.1		address1=192.168.7.7/24,192.168.7.6
	dns=8.8.8.8;		dns=192.168.7.6;
	method=manual		method=manual

Jca: /* Install DNS server on Raspberry */

2026-07-13T07:22:03Z

Install DNS server on Raspberry

← Older revision		Revision as of 09:22, 13 July 2026
Line 143:		Line 143:
	==== Install DNS server on Raspberry ====		==== Install DNS server on Raspberry ====

	~~This section may~~ be deprecated; use the alternative method above with fallback to a static IP.		May be deprecated; use the alternative method above with fallback to a static IP.

	Allow the connected PC to get an IP automatically; install DNSMASQ		Allow the connected PC to get an IP automatically; install DNSMASQ

Jca: /* Install DNS server on Raspberry */

2026-07-13T07:21:24Z

Install DNS server on Raspberry

← Older revision		Revision as of 09:21, 13 July 2026
Line 143:		Line 143:
	==== Install DNS server on Raspberry ====		==== Install DNS server on Raspberry ====

	This section may be deprecated, use the alternative method above with fallback to static IP.		This section may be deprecated; use the alternative method above with fallback to a static IP.

	Allow the connected PC to get an IP automatically; install DNSMASQ		Allow the connected PC to get an IP automatically; install DNSMASQ
Line 149:		Line 149:
	sudo apt install dnsmasq		sudo apt install dnsmasq

	Configure ~~the~~ use by editing /etc/dnsmasq.conf		Configure its use by editing /etc/dnsmasq.conf

	sudo nano /etc/dnsmasq.conf		sudo nano /etc/dnsmasq.conf

	Uncomment and change two lines. It is to be used on ETH0 only and in the IP range 192.168.7.50 to 192.168.7.99.		Uncomment and change two lines. It is to be used on ETH0 only and in the IP range 192.168.7.60 to 192.168.7.70.

	# DNS requests only on		# DNS requests only on
Line 160:		Line 160:
	# range of addresses available for lease and optionally		# range of addresses available for lease and optionally
	# a lease time		# a lease time
	dhcp-range=192.168.7.50,192.168.7.~~99,255.255.255.0~~,12h		dhcp-range=192.168.7.60,192.168.7.70,12h

	Restart ~~the~~ dnsmasq		Restart dnsmasq

	sudo service dnsmasq restart		sudo service dnsmasq restart

	To see the status of the dnsmasq service use:		To see the status of the dnsmasq service, use:

	journalctl -b0 -u dnsmasq.service		journalctl -b0 -u dnsmasq.service

	After this, when you plug in a cable to a PC~~, then, after some seconds~~, both the robot and the PC should have an IP in the ~~range~~ 192.168.7.x. And the robot should display the new IP 192.168.7.7.		After this, when you plug a cable into a PC, both the robot and the PC should have IP addresses in the 192.168.7. range within a minute or so. And the robot should display the new IP 192.168.7.7.

	You can now access the robot using		You can now access the robot using

Jca: /* Home network connection */

2026-04-28T07:24:16Z

Home network connection

← Older revision		Revision as of 09:24, 28 April 2026
Line 50:		Line 50:

	sudo nmcli device wifi connect <SSID> password <password> ifname wlan0		sudo nmcli device wifi connect <SSID> password <password> ifname wlan0

	~~If you have no network contact, then use a local link (cable) or attach a screen and keyboard.~~

	==== As its own hotspot ====		==== As its own hotspot ====

Jca: /* As its own hotspot */

2026-04-28T07:23:40Z

As its own hotspot

← Older revision		Revision as of 09:23, 28 April 2026
Line 55:		Line 55:
	==== As its own hotspot ====		==== As its own hotspot ====

	See [[RICbot Hotspot \| hotspot]]		See [[RICbot Hotspot \| hotspot]].

	== Cable connection ==		== Cable connection ==

Jca: /* As its own hotspot */

2026-04-28T07:23:29Z

As its own hotspot

← Older revision		Revision as of 09:23, 28 April 2026
Line 55:		Line 55:
	==== As its own hotspot ====		==== As its own hotspot ====

	See [[~~Ricbot hotspot~~ \| hotspot]]		See [[RICbot Hotspot \| hotspot]]

	== Cable connection ==		== Cable connection ==

Jca: /* Network Manager */

2026-04-28T07:20:08Z

Network Manager

← Older revision		Revision as of 09:20, 28 April 2026
Line 18:		Line 18:
	nmcli connection		nmcli connection
	List available wifi access points		List available wifi access points
	nmcli ~~dev~~ wifi		nmcli device wifi list

	==== Connect to DTUdevice net ====		==== Connect to DTUdevice net ====

Jca: /* Home network connection */

2026-04-28T07:12:32Z

Home network connection

← Older revision		Revision as of 09:12, 28 April 2026
Line 52:		Line 52:

	If you have no network contact, then use a local link (cable) or attach a screen and keyboard.		If you have no network contact, then use a local link (cable) or attach a screen and keyboard.

			==== As its own hotspot ====

			See [[Ricbot hotspot \| hotspot]]

	== Cable connection ==		== Cable connection ==

Jca: /* NTP */

2026-04-20T12:34:22Z

NTP

← Older revision		Revision as of 14:34, 20 April 2026
Line 226:		Line 226:

	'''Depreciated'''. The Raspberry default time sync now works, also at DTU.		'''Depreciated'''. The Raspberry default time sync now works, also at DTU.
			=== PTP ===
	For PTP, see [[Ricbot PTP]].		For PTP, see [[Ricbot PTP]].

			=== NTP (depricated) ===
	Network Time Protocol is used to keep clocks in sync.		Network Time Protocol is used to keep clocks in sync.
	Raspberry Pi will start with the date and time of the last proper shutdown, and a few seconds after the network is up, it will sync the clock using NTP.		Raspberry Pi will start with the date and time of the last proper shutdown, and a few seconds after the network is up, it will sync the clock using NTP.

Jca: /* PTP */

2026-04-20T12:33:39Z

PTP

← Older revision		Revision as of 14:33, 20 April 2026
Line 222:		Line 222:

	The robot's name should be included in the list, but the network may take a while to detect it.		The robot's name should be included in the list, but the network may take a while to detect it.

	~~== PTP ==~~

	~~Precise Time Protocol (on Raspberry Pi 5)~~

	~~Assuming 2 Raspberry Pis are connected with an Ethernet cable, and both have an IP on eth0.~~

	~~==== Install ====~~

	~~Install on both master and slave:~~
	~~sudo apt install linuxptp~~

	~~Verify that there is support on 'eth0'.~~
	~~Should have hardware capabilities:~~

	~~$ ethtool -T eth0~~
	~~Time stamping parameters for eth0:~~
	~~Capabilities:~~
	~~hardware-transmit~~
	~~software-transmit~~
	~~hardware-receive~~
	~~software-receive~~
	~~software-system-clock~~
	~~hardware-raw-clock~~

	~~==== Test time master ====~~

	~~Start connection to eth0 hardware (as a process in the background)~~

	~~sudo phc2sys -s CLOCK_REALTIME -c eth0 -w &~~

	~~Start clock master service on eth0~~

	~~sudo ptp4l -i eth0 -m -2 -s~~

	~~It should be activated as a grand master soon.~~

	~~==== Test time client ====~~

	~~Run a PTP test slave (-s) with output to console (-m).~~

	~~sudo ptp4l -i eth0 -m -2 -s~~

	~~After a few minutes, this should yield a time offset on the order of 100 ns.~~

	~~Kill the phc2sys on the time server after the client test:~~
	~~sudo pkill phc2sys~~

	~~==== Install as a service on Master ====~~

	~~Most is copied from https://austinsnerdythings.com/2025/02/18/nanosecond-accurate-ptp-server-grandmaster-and-client-tutorial-for-raspberry-pi/.~~

	~~Create a service file for the connection to eth0:~~

	~~sudo nano /etc/systemd/system/phc2sys-grandmaster.service~~

	~~With:~~
	~~[Unit]~~
	~~Description=sync PHC with system clock (grandmaster)~~
	~~After=network-online.target~~
	~~Wants=network-online.target~~

	~~[Service]~~
	~~Type=simple~~
	~~ExecStart=/usr/sbin/phc2sys -s CLOCK_REALTIME -c eth0 -w~~
	~~Restart=always~~
	~~RestartSec=3~~

	~~[Install]~~
	~~WantedBy=multi-user.target~~

	~~Create a service file for the ptp server:~~

	~~sudo nano /etc/systemd/system/ptp4l-grandmaster.service~~

	~~With:~~
	~~[Unit]~~
	~~Description=Precision Time Protocol (PTP) service (Grandmaster)~~
	~~After=network-online.target~~
	~~Wants=network-online.target~~

	~~[Service]~~
	~~Type=simple~~
	~~ExecStart=/usr/sbin/ptp4l -i eth0 -2~~
	~~Restart=always~~
	~~RestartSec=3~~

	~~[Install]~~
	~~WantedBy=multi-user.target~~

	~~Enable and start these services~~

	~~sudo systemctl daemon-reload~~
	~~sudo systemctl enable phc2sys-grandmaster.service~~
	~~sudo systemctl enable ptp4l-grandmaster.service~~
	~~sudo systemctl start phc2sys-grandmaster.service~~
	~~sudo systemctl start ptp4l-grandmaster.service~~

	~~==== Install as a service on the client ====~~

	~~Make a new service file~~
	~~sudo nano /etc/systemd/system/ptp4l-client.service~~
	~~With:~~
	~~[Unit]~~
	~~Description=Precision Time Protocol (PTP) service (Client)~~
	~~After=network-online.target~~
	~~Wants=network-online.target~~

	~~[Service]~~
	~~Type=simple~~
	~~ExecStart=/usr/sbin/ptp4l -i eth0 -2 -m --summary_interval 3~~
	~~Restart=always~~
	~~RestartSec=3~~

	~~[Install]~~
	~~WantedBy=multi-user.target~~

	~~Also, enable and start this service:~~

	~~sudo systemctl daemon-reload~~
	~~sudo systemctl enable ptp4l-client.service~~
	~~sudo systemctl start ptp4l-client.service~~

	~~Check the status of the client when all is in place~~
	~~sudo systemctl status ptp4l-client~~

	== NTP ==		== NTP ==