IP Connection - Revision history

Beroset: add Custom Address section

2026-03-09T17:40:14Z

add Custom Address section

← Older revision		Revision as of 17:40, 9 March 2026
Line 83:		Line 83:

	In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.		In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.

			== Custom Address ==
			The watch defaults to the address 192.168.2.15, but this can be changed. If, for example, you want to change the address to 10.0.0.2, the recommended way to change it is to do this:

			# temporarily changing the USB mode on the watch to "ADB mode"
			# issue the command <pre>adb dbus-send --system --type=method_call --print-reply --dest=com.meego.usb_moded /com/meego/usb_moded com.meego.usb_moded.net_config string:'ip' string:'10.0.0.2'</pre>
			# change USB mode to "SSH mode"

			Note that if you have more than one ADB device attached to your computer, you might have to give it the transport ID in step 2. This change persists across boots.

			An alternative approach for developers building their own image using bitbake, is to edit the file https://github.com/AsteroidOS/meta-asteroid/blob/master/recipes-nemomobile/usb-moded/usb-moded/usb-moded/usb-moded.ini. And add:

			<pre>
			[network]
			ip=10.0.0.2
			</pre>

	= Paranoid Kernels=		= Paranoid Kernels=

Mosen: /* IP over WLAN (WiFi) */ Add note to connect

2026-03-05T00:58:22Z

IP over WLAN (WiFi): Add note to connect

← Older revision		Revision as of 00:58, 5 March 2026
Line 34:		Line 34:

	Output: Connected to wifi_1234567890_1234567890_managed_psk		Output: Connected to wifi_1234567890_1234567890_managed_psk

			Note: If the connection fails with an error (e.g., "Invalid key" or no connection), try connecting to the other service identifier listed for the same SSID name, as it may correspond to the 2.4 GHz band that your watch supports more reliably (while the other is likely 5 GHz).
	<pre>quit</pre>		<pre>quit</pre>
	Leaves the connmanctl interactive mode.		Leaves the connmanctl interactive mode.

Mosen: /* IP over WLAN (WiFi) */

2026-03-05T00:39:50Z

IP over WLAN (WiFi)

← Older revision		Revision as of 00:39, 5 March 2026
Line 6:		Line 6:
	Connect to your watch using <code>ssh root@192.168.2.15</code> or <code>adb shell</code>.		Connect to your watch using <code>ssh root@192.168.2.15</code> or <code>adb shell</code>.

			<pre>connmanctl</pre>
			Starts the connmanctl interactive mode. The prompt indicator will change to <code>connmanctl></code>
			<pre>enable wifi</pre>
			Output: Enabled wifi
			<pre>scan wifi</pre>
			Output: Scan completed for wifi
			<pre>agent on</pre>
			Output: Agent registered

	<pre>		The Agent will handle automatic reconnect to the network.
	~~# connmanctl~~		<pre>services</pre>
	~~connmanctl> enable wifi~~		Shows the discovered SSIDs and their service identifier.
	~~Enabled wifi~~
	~~connmanctl~~> ~~scan wifi~~		Output example:
	~~Scan completed for wifi~~
	~~connmanctl~~> ~~services~~		<code>YourNetwork wifi_1234567890_1234567890_managed_psk</code>
	~~SomeNetwork wifi_1234567890_1234567890_managed_psk~~
	OtherLAN wifi_0987654321_123456789_managed_psk		<code>OtherLAN wifi_0987654321_123456789_managed_psk</code>
	~~connmanctl~~> ~~agent on~~		<pre>connect <ServiceIdentifierOfYourSSID></pre>
	~~Agent registered~~		Example:
	~~connmanctl~~> connect wifi_1234567890_1234567890_managed_psk
	~~[...]~~		<code>connect wifi_1234567890_1234567890_managed_psk</code>
	Passphrase ? ~~YouTypeYouPassPhraseThenEnter~~
	~~connmanctl~~> quit		Prompt changes to <code>Passphrase?</code> and asks for the password to the SSID.
	</pre>
			<code>TypeYourPassPhraseAndPressEnter</code>

			Output: Connected to wifi_1234567890_1234567890_managed_psk
			<pre>quit</pre>
			Leaves the connmanctl interactive mode.

	Check whether an IP address has been assigned to the watch using <code>ip a show dev wlan0</code> or <code>ifconfig wlan0</code>.		Check whether an IP address has been assigned to the watch using <code>ip a show dev wlan0</code> or <code>ifconfig wlan0</code> or by trying to <code>ping 8.8.8.8</code>.

	Note that activated WLAN consumes additional power. Currently, it is recommended to disable the function after use. <code>connmanctl disable wifi</code> is used to disable Wi-Fi and power off WLAN temporarily. <code>connmanctl enable wifi</code> activates WLAN again and connects to the last used Wi-Fi network.		Note that activated WLAN consumes additional power. Currently, it is recommended to disable the function after use. <code>connmanctl disable wifi</code> is used to disable Wi-Fi and power off WLAN temporarily. <code>connmanctl enable wifi</code> activates WLAN again and connects to the last used Wi-Fi network.
Line 30:		Line 43:
	Some more documentation on connman can be found on [https://wiki.archlinux.org/index.php/ConnMan#Connecting_to_a_protected_access_point ArchWiki].		Some more documentation on connman can be found on [https://wiki.archlinux.org/index.php/ConnMan#Connecting_to_a_protected_access_point ArchWiki].

	~~= IP over USB =~~
	~~It is possible to allow your watch to be able to use your Linux computer's internet connection via a USB connection. You will need:~~

	# A Linux computer with RNDIS support loaded and enabled		=IP over USB=
	# The ability to change network configurations on that computer		It is possible to allow your watch to be able to use your Linux computer's internet connection via a USB connection. You will need:
	# A network connection
			#A Linux computer with RNDIS support loaded and enabled
			#The ability to change network configurations on that computer
			#A network connection

	This works by using the RNDIS driver to allow the USB device to appear to be a network interface. RNDIS stands for "Remote Network Driver Interface Specification" and was a proprietary protocol from Microsoft. It is supported in Linux by the <code>rndis_host</code> driver. This driver may either be compiled into the kernel, or more typically provided as an optional module. If you're not sure, you can try this <code>lsmod</code> to see if it's loaded on your computer.		This works by using the RNDIS driver to allow the USB device to appear to be a network interface. RNDIS stands for "Remote Network Driver Interface Specification" and was a proprietary protocol from Microsoft. It is supported in Linux by the <code>rndis_host</code> driver. This driver may either be compiled into the kernel, or more typically provided as an optional module. If you're not sure, you can try this <code>lsmod</code> to see if it's loaded on your computer.
Line 68:		Line 82:
	In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.		In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.

	= Paranoid Kernels =		= Paranoid Kernels=
	On some watch models (e.g., <code>lenok</code>), the kernel shipped with AsteroidOS is compiled with the Android-specific <code>CONFIG_ANDROID_PARANOID_NETWORK</code> kernel option enabled. That option enforces non-standard restrictions on networking, based on hardcoded group IDs (GIDs):		On some watch models (e.g., <code>lenok</code>), the kernel shipped with AsteroidOS is compiled with the Android-specific <code>CONFIG_ANDROID_PARANOID_NETWORK</code> kernel option enabled. That option enforces non-standard restrictions on networking, based on hardcoded group IDs (GIDs):
	* GID 3003 is the <code>inet</code> group, allowing to create <code>AF_INET</code> and <code>AF_INET6</code> sockets,		*GID 3003 is the <code>inet</code> group, allowing to create <code>AF_INET</code> and <code>AF_INET6</code> sockets,
	* GID 3004 is the <code>net_raw</code> group, allowing to create raw INET sockets.		* GID 3004 is the <code>net_raw</code> group, allowing to create raw INET sockets.

Nchauvat: /* IP over WLAN (WiFi) */

2026-03-03T21:59:30Z

IP over WLAN (WiFi)

← Older revision		Revision as of 21:59, 3 March 2026
Line 5:		Line 5:
	= IP over WLAN (WiFi) =		= IP over WLAN (WiFi) =
	Connect to your watch using <code>ssh root@192.168.2.15</code> or <code>adb shell</code>.		Connect to your watch using <code>ssh root@192.168.2.15</code> or <code>adb shell</code>.


	<pre>		<pre>
	# connmanctl		# connmanctl
	connmanctl> enable wifi		connmanctl> enable wifi
			Enabled wifi
	connmanctl> scan wifi		connmanctl> scan wifi
			Scan completed for wifi
	connmanctl> services		connmanctl> services
			SomeNetwork wifi_1234567890_1234567890_managed_psk
			OtherLAN wifi_0987654321_123456789_managed_psk
	connmanctl> agent on		connmanctl> agent on
	connmanctl> connect ~~wifi_CODE-FOR-YOUR-SSID~~		Agent registered
			connmanctl> connect wifi_1234567890_1234567890_managed_psk
			[...]
			Passphrase ? YouTypeYouPassPhraseThenEnter
	connmanctl> quit		connmanctl> quit
	</pre>		</pre>

Beroset: /* IP over USB */ Update routing command to use `ip` rather than `route`.

2025-11-18T13:21:02Z

IP over USB: Update routing command to use `ip` rather than `route`.

← Older revision		Revision as of 13:21, 18 November 2025
Line 49:		Line 49:
	Configure a default gateway and DNS '''on the watch''' with the following commands ran via [[SSH]] as the root user:		Configure a default gateway and DNS '''on the watch''' with the following commands ran via [[SSH]] as the root user:

	<pre>route add default gw 192.168.2.1</pre>		<pre>ip route add default via 192.168.2.1</pre>
	<pre>echo "nameserver 8.8.8.8" >> /etc/resolv.conf</pre>		<pre>echo "nameserver 8.8.8.8" >> /etc/resolv.conf</pre>

Kevin Kofler: /* Paranoid Kernels */ Fix a small grammar error / typo I made.

2025-08-10T18:33:09Z

Paranoid Kernels: Fix a small grammar error / typo I made.

← Older revision		Revision as of 18:33, 10 August 2025
Line 72:		Line 72:
	groupadd -g 3004 -U root,ceres net_raw		groupadd -g 3004 -U root,ceres net_raw
	</pre>		</pre>
	These create the two magic groups with the same name and GID as on Android and ~~adds~~ both <code>root</code> and <code>ceres</code> to them. Then reboot your watch, because only newly started sessions will pick up the new group memberships.		These create the two magic groups with the same name and GID as on Android and add both <code>root</code> and <code>ceres</code> to them. Then reboot your watch, because only newly started sessions will pick up the new group memberships.

Kevin Kofler: Document CONFIG_ANDROID_PARANOID_NETWORK restrictions.

2025-08-10T00:53:23Z

Document CONFIG_ANDROID_PARANOID_NETWORK restrictions.

@@ Line 1: / Line 1: @@
 Configuring an IP connection on your watch has to be done manually until a GUI settings option is available. On watches that support WLAN, you can enable Wi-Fi and configure the connection using <code>connmanctl</code> like described below. Forwarding IP requests to a connected PC via USB is another option, explained in the second paragraph.
-By default, there is no <code>root</code> or <code>ceres</code> password, and no firewall rules. A password can be set using the passwd command.
+By default, there is no <code>root</code> or <code>ceres</code> password, and no firewall rules. (However, on some watches, the kernel has the <code>CONFIG_ANDROID_PARANOID_NETWORK</code> kernel option enabled, see below.) A password can be set using the passwd command.
 = IP over WLAN (WiFi) =
@@ Line 59: / Line 59: @@
 In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.

Mosen at 21:57, 4 July 2023

2023-07-04T21:57:53Z

← Older revision		Revision as of 21:57, 4 July 2023
Line 42:		Line 42:
	Once the <code>rndis_host</code> is installed and running, you can enable Network Address Translation (NAT) to allow your Linux computer to share it's internet IP address with the watch. To configure a NAT '''on your computer''' (Note: Replace eth0 with the name of the interface that connects your computer to the Internet) with:		Once the <code>rndis_host</code> is installed and running, you can enable Network Address Translation (NAT) to allow your Linux computer to share it's internet IP address with the watch. To configure a NAT '''on your computer''' (Note: Replace eth0 with the name of the interface that connects your computer to the Internet) with:

	<pre>		<pre>echo 1 > /proc/sys/net/ipv4/ip_forward</pre>
	echo 1 > /proc/sys/net/ipv4/ip_forward		<pre>iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE</pre>
	iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
	</pre>

	Here again, you might need root privileges for those commands, depending on how your computer is configured.		Here again, you might need root privileges for those commands, depending on how your computer is configured.
Line 51:		Line 49:
	Configure a default gateway and DNS '''on the watch''' with the following commands ran via [[SSH]] as the root user:		Configure a default gateway and DNS '''on the watch''' with the following commands ran via [[SSH]] as the root user:

	<pre>		<pre>route add default gw 192.168.2.1</pre>
	route add default gw 192.168.2.1		<pre>echo "nameserver 8.8.8.8" >> /etc/resolv.conf</pre>
	echo "nameserver 8.8.8.8" >> /etc/resolv.conf
	</pre>

	Note that this assumes that your computer's IP address on RNDIS is 192.168.2.1, which is the default, but if you have multiple watches, or have plugged and unplugged the same watch a few times, it might be different. To make sure, on the watch, you can type <code>who</code> and it will reply with something like this:		Note that this assumes that your computer's IP address on RNDIS is 192.168.2.1, which is the default, but if you have multiple watches, or have plugged and unplugged the same watch a few times, it might be different. To make sure, on the watch, you can type <code>who</code> and it will reply with something like this:

Dodoradio: Copy 'IP connection' page from the current wiki

2023-06-17T11:49:04Z

Copy 'IP connection' page from the current wiki

New page

Configuring an IP connection on your watch has to be done manually until a GUI settings option is available. On watches that support WLAN, you can enable Wi-Fi and configure the connection using <code>connmanctl</code> like described below. Forwarding IP requests to a connected PC via USB is another option, explained in the second paragraph.

By default, there is no <code>root</code> or <code>ceres</code> password, and no firewall rules. A password can be set using the passwd command.

= IP over WLAN (WiFi) =
Connect to your watch using <code>ssh root@192.168.2.15</code> or <code>adb shell</code>.

<pre>
# connmanctl
connmanctl> enable wifi
connmanctl> scan wifi
connmanctl> services
connmanctl> agent on
connmanctl> connect wifi_CODE-FOR-YOUR-SSID
connmanctl> quit
</pre>

Check whether an IP address has been assigned to the watch using <code>ip a show dev wlan0</code> or <code>ifconfig wlan0</code>.

Note that activated WLAN consumes additional power. Currently, it is recommended to disable the function after use. <code>connmanctl disable wifi</code> is used to disable Wi-Fi and power off WLAN temporarily. <code>connmanctl enable wifi</code> activates WLAN again and connects to the last used Wi-Fi network.

Some more documentation on connman can be found on [https://wiki.archlinux.org/index.php/ConnMan#Connecting_to_a_protected_access_point ArchWiki].

= IP over USB =
It is possible to allow your watch to be able to use your Linux computer's internet connection via a USB connection. You will need:

# A Linux computer with RNDIS support loaded and enabled
# The ability to change network configurations on that computer
# A network connection

This works by using the RNDIS driver to allow the USB device to appear to be a network interface. RNDIS stands for "Remote Network Driver Interface Specification" and was a proprietary protocol from Microsoft. It is supported in Linux by the <code>rndis_host</code> driver. This driver may either be compiled into the kernel, or more typically provided as an optional module. If you're not sure, you can try this <code>lsmod</code> to see if it's loaded on your computer.

<pre>
lsmod | grep ndis
rndis_host 24576 0
cdc_ether 24576 1 rndis_host
usbnet 61440 2 rndis_host,cdc_ether
</pre>

If it isn't you might be able to use <code>modprobe rndis_host</code> (with root privileges) to install the module.

Once the <code>rndis_host</code> is installed and running, you can enable Network Address Translation (NAT) to allow your Linux computer to share it's internet IP address with the watch. To configure a NAT '''on your computer''' (Note: Replace eth0 with the name of the interface that connects your computer to the Internet) with:

<pre>
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
</pre>

Here again, you might need root privileges for those commands, depending on how your computer is configured.

Configure a default gateway and DNS '''on the watch''' with the following commands ran via [[SSH]] as the root user:

<pre>
route add default gw 192.168.2.1
echo "nameserver 8.8.8.8" >> /etc/resolv.conf
</pre>

Note that this assumes that your computer's IP address on RNDIS is 192.168.2.1, which is the default, but if you have multiple watches, or have plugged and unplugged the same watch a few times, it might be different. To make sure, on the watch, you can type <code>who</code> and it will reply with something like this:

<code>
root pts/0 00:01 Jun 9 08:06:24 192.168.2.2
</code>

In this particular case, the address shown is 192.168.2.2, so the first command listed above would be <code>route add default gw 192.168.2.2</code>.