# RPI 4 can´t connect to network **URL:** \ **Category:** balenaOS\ **Tags:** network\ **Created:** [June 17, 2020, 6:30pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056 "2020-06-17T18:30:28Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Orsen](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@Orsen](https://forums.balena.io/u/Orsen)\ **Post date:** [June 17, 2020, 6:30pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/1 "2020-06-17T18:30:28Z")
Hello, I´m a first time user of Balena OS and Balena Cloud. I´m having problems with connection (4 short flashes) through ethernet. So I tried to open all required ports, multiple cables, redownload OS, but that didn´t work and I don´t see RPI on my network. ---
**Author:** ![jtonello](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jtonello/32/3246_2.png) [@jtonello](https://forums.balena.io/u/jtonello)\ **Post date:** [June 17, 2020, 7:00pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/3 "2020-06-17T19:00:17Z")
Hi @Orsen, Welcome to the forums! You shouldn’t have to open ports because all device network traffic passes through the built-in balena VPN using port 443. Did you set up “ethernet only” during the image download or did you also add wifi credentials? Adding wifi would be a good way to check if the RPi’s ethernet port has an issue. John ---
**Author:** ![Orsen](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@Orsen](https://forums.balena.io/u/Orsen)\ **Post date:** [June 18, 2020, 10:39am UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/6 "2020-06-18T10:39:48Z")
Thank you for the response, so I tried WI-FI and it worked! But I don´t know how to make it work with ethernet. I even tried the same cable as I’m using right now. ---
**Author:** ![CameronDiver](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@CameronDiver](https://forums.balena.io/u/CameronDiver)\ **Post date:** [June 18, 2020, 12:14pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/7 "2020-06-18T12:14:57Z")
Hey, that’s certainly strange! Let’s try to get to the bottom of these issues. Firstly if possible I’d like for you to install a `dev` version of balenaOS on your device. This will cause it to “broadcast” it’s hostname across the LAN. So to detect that “broadcast”, I would then ask you to install [balena-cli](https://github.com/balena-io/balena-cli) and run `balena scan` using `sudo` on OSX or linux and an administrator terminal on windows. What I’m looking for here is at least 1 entry from the `scan` command, which shows us the device is in fact connected to the LAN. If this shows up, we then want to ssh in using `balena ssh ` where `` is the address found in `balena scan`. From there, run `journalctl -f -u resin-supervisor -n 10000` and paste the results here please. If the device is not connected to the LAN, something seriously more weird is going on, so we can debug that then if necessary 🙂 ---
**Author:** ![Orsen](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@Orsen](https://forums.balena.io/u/Orsen)\ **Post date:** [June 18, 2020, 12:49pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/9 "2020-06-18T12:49:17Z")
I downloaded a new image of ethernet Balena OS, flashed with Etcher and I still didn´t see it through balena cli even when I switched cables. P.S. other distros work with ethernet. ---
**Author:** ![CameronDiver](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@CameronDiver](https://forums.balena.io/u/CameronDiver)\ **Post date:** [June 18, 2020, 12:51pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/10 "2020-06-18T12:51:55Z")
Did you definitely download a `dev` version of the OS? ---
**Author:** ![Orsen](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@Orsen](https://forums.balena.io/u/Orsen)\ **Post date:** [June 18, 2020, 12:57pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/11 "2020-06-18T12:57:14Z")
balena-cloud-RPI02-raspberrypi4-64-2.51.1+rev1-dev-v11.4.10.img ---
**Author:** ![odyslam](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/odyslam/32/1684_2.png) [@odyslam](https://forums.balena.io/u/odyslam)\ **Post date:** [June 18, 2020, 2:09pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/12 "2020-06-18T14:09:35Z")
Hey, Can you please connect the Raspberry pi though wifi and ethernet at the same time? In essence, repeat the steps that you followed to connect the device via wifi and then simply connect the ethernet cable. After you do this, can you find the device using `balena scan`? ---
**Author:** ![Orsen](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@Orsen](https://forums.balena.io/u/Orsen)\ **Post date:** [June 18, 2020, 2:26pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/13 "2020-06-18T14:26:51Z")
thank you for reply, [https://pastebin.com/xF31cawi](https://pastebin.com/xF31cawi) ---
**Author:** ![odyslam](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/odyslam/32/1684_2.png) [@odyslam](https://forums.balena.io/u/odyslam)\ **Post date:** [June 18, 2020, 2:47pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/14 "2020-06-18T14:47:04Z")
Thanks for the output. Can you please verify that the device is connected to the ethernet (as also the wifi) and run the command `ifconfig` inside the device, afterwards please copy the output here aswell. ---
**Author:** ![Orsen](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@Orsen](https://forums.balena.io/u/Orsen)\ **Post date:** [June 18, 2020, 3:10pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/15 "2020-06-18T15:10:32Z")
``` balena0 Link encap:Ethernet HWaddr 02:42:89:50:0D:EA inet addr:10.114.101.1 Bcast:10.114.101.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) br-37ee75c24d37 Link encap:Ethernet HWaddr 02:42:70:81:4B:5A inet addr:172.18.0.1 Bcast:172.18.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth0 Link encap:Ethernet HWaddr DC:A6:32:47:FC:F0 inet6 addr: fe80::f867:8c97:363c:9d53/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2163 errors:0 dropped:0 overruns:0 frame:0 TX packets:104 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:336414 (328.5 KiB) TX bytes:27879 (27.2 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1226 errors:0 dropped:0 overruns:0 frame:0 TX packets:1226 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:106592 (104.0 KiB) TX bytes:106592 (104.0 KiB) resin-dns Link encap:Ethernet HWaddr AA:90:3B:0B:55:44 inet addr:10.114.102.1 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::a890:3bff:fe0b:5544/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:68 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:12097 (11.8 KiB) resin-vpn Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.240.53.210 P-t-P:52.4.252.97 Mask:255.255.255.255 inet6 addr: fe80::a729:575a:4cc4:55f6/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:480 (480.0 B) supervisor0 Link encap:Ethernet HWaddr 02:42:CF:8B:46:FC inet addr:10.114.104.1 Bcast:10.114.104.127 Mask:255.255.255.128 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr DC:A6:32:47:FC:F1 inet addr:192.168.1.113 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::29ff:d733:de44:39ad/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4573 errors:0 dropped:0 overruns:0 frame:0 TX packets:2999 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:864941 (844.6 KiB) TX bytes:492376 (480.8 KiB) ``` ---
**Author:** ![odyslam](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/odyslam/32/1684_2.png) [@odyslam](https://forums.balena.io/u/odyslam)\ **Post date:** [June 18, 2020, 5:05pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/16 "2020-06-18T17:05:48Z")
From that output, we can see that the `eth0` interface (the ethernet) is indeed working and received a unique IP, but for some reason it only received an IPv6 and not an IPv4. This could be related to your router, as the `wlan0` interface (wifi) receives a proper IPv4 IP and thus you can connect, use balena scan, etc. Can you please share the router model/manufacturer? ---
**Author:** ![Orsen](https://avatars.discourse-cdn.com/v4/letter/o/f14d63/32.png) [@Orsen](https://forums.balena.io/u/Orsen)\ **Post date:** [June 18, 2020, 5:11pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/18 "2020-06-18T17:11:40Z")
The router is Asus ac68u. ---
**Author:** ![odyslam](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/odyslam/32/1684_2.png) [@odyslam](https://forums.balena.io/u/odyslam)\ **Post date:** [June 18, 2020, 5:48pm UTC](https://forums.balena.io/t/rpi-4-can-t-connect-to-network/135056/19 "2020-06-18T17:48:20Z")
For some reason, your router’s DHCP server is not assigning an IPv4 to the device via ethernet. This could be isolated to the particular ethernet port that your are using, or in general your router could be configured not to assign IPv4 via ethernet. I would advise to check the user’s manual and see how to reset the DHCP server configuration to the default. Thanks for using the forums and we hope that you enjoy balena! Best of luck 🙂