diff --git a/projects/swiot1l/Makefile b/projects/swiot1l/Makefile
index 15b8b6d6445..384a05d1f5f 100644
--- a/projects/swiot1l/Makefile
+++ b/projects/swiot1l/Makefile
@@ -6,8 +6,8 @@ SWIOT1L_STATIC_IP = n
 endif
 
 ifeq (y,$(strip $(SWIOT1L_STATIC_IP)))
-NO_OS_IP=169.254.97.40
-NO_OS_NETMASK=255.255.255.0
+NO_OS_IP=192.168.97.40
+NO_OS_NETMASK=255.255.0.0
 NO_OS_GATEWAY=0.0.0.0
 endif
 
diff --git a/projects/swiot1l/README.md b/projects/swiot1l/README.md
index c996d6b4615..3778b996c05 100644
--- a/projects/swiot1l/README.md
+++ b/projects/swiot1l/README.md
@@ -47,10 +47,10 @@ In order to configure and sample data from the SWIOT1L board, you'll have to con
 
 1. Using a T1L -> Ethernet media converter:
 - Direct connection to PC:
-Build the firmware with the `SWIOT1L_STATIC_IP=y` flag, will result in using `169.254.97.40` as an IP address. This is the fastest way of testing the platform, since it doesn't require the DHCP configuration or DHCP timeout (in case of AutoIP).
+Build the firmware with the `SWIOT1L_STATIC_IP=y` flag, will result in using `192.168.97.40` as an IP address. This is the fastest way of testing the platform, since it doesn't require the DHCP configuration or DHCP timeout (in case of AutoIP).
 Alternatively, you may omit `SWIOT1L_STATIC_IP=y` (or set it to `n`), in which case, the board will send a DHCP request and try to get an IP that way. If you don't have a DHCP server listening on the PC's network interface (to which SWIOT1L is connected), a link local address (in the 169.254.x.x\16 range) will be used. This may take a while (~10s) the first time you power the board, since there have to be 2 failed DHCP requests.
 
-	In case a link local address is used, the user may need to add a static route if the PC has multiple network interfaces up. If using Linux, this can be done by running the following in a terminal:
+	In case a link local or static IP address is used, the user may need to add a static route if the PC has multiple network interfaces up. If using Linux, this can be done by running the following in a terminal:
 	
 	`sudo ip route add 169.254.97.40/32 dev if_name`
 	`if_name` should be replaced with the name of the network interface the SWIOT1L board is connected on.