Skip to contentSkip to conversation

Ethernet Connection

Buildroot Andreas Ziegler 2 participants 2 messages Oct 8, 2024 – Oct 9, 2024 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi Andy,

Quoted 5 lines · Andrew McCann

Can anyone comment on whether you expect the default rpi3b+ configuration to connect to LAN?
Regards
Andy

It should work. I use a custom configuration, but it was derived from the Buildroot standard originally.

Quoted 9 lines
Quoted 6 lines · On Wed, Oct 2, 2024 at 5:24?PM Andrew McCann <[email protected]> wrote:

Hi All

I'm trying to get basic networking working with a Rpi-3b+. I note that with the default config, raspberrypi3_64_defconfig, eth0 is setup as the network interface to configure through DHCP. Also BR2_PACKAGE_IFUPDOWN_SCRIPTS are enabled by default.

Don't you use a bespoke kernel? Check if the necessary modules are enabled.

ifupdown-scripts provides an init.d script and generates network/interfaces. Check if the latter matches your system.

Run '/etc/init.d/S40network restart' and follow up on any error messages.

Quoted 8 lines
Quoted 8 lines

However, when I boot the system with sdcard.img, the pi does not connect to my network. Are there are things that I need to enable that are not part of the default configuration?

My longer term goal is to ssh (using dropbear) into my pi via the LAN, and use iwctl to configure iwd for wireless connectivity. But first I need to establish the LAN connection. Please let me know any advice that you have, or any documentation that you can recommend.

I relied on linux-from-scratch [1] and linux-wireless [2] while setting up wireless networking, but you might succeed just by adding wpa_supplicant and supplying the necessary configuration details.

The Buildroot package handles wpa_supplicant via an ifup/down script; if you use a (custom, via skeleton) init.d script instead, you need to adapt network/interfaces.

Kind regards,
Andreas

Quoted 2 lines
Quoted 2 lines

Regards
Andy

[1] https://www.linuxfromscratch.org/
[2] https://wireless.wiki.kernel.org/
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

#2 lore raw

HI Andreas
Thanks for your detailed reply and for the sources. I will try your recommendations and see if I can get this to work. Regards
Andy

Quoted 57 lines · Andreas Ziegler

Hi Andy,

Quoted 6 lines · Andrew McCann

Can anyone comment on whether you expect the default rpi3b+ configuration
to connect to LAN?
Regards
Andy

It should work. I use a custom configuration, but it was derived from the Buildroot standard originally.

Quoted 4 lines

On Wed, Oct 2, 2024 at 5:24?PM Andrew McCann
<[email protected]>
wrote:

Quoted 8 lines
Quoted 8 lines

Hi All

I'm trying to get basic networking working with a Rpi-3b+. I note that
with the default config, raspberrypi3_64_defconfig, eth0 is setup as the
network interface to configure through DHCP. Also BR2_PACKAGE_IFUPDOWN_SCRIPTS are enabled by default.

Don't you use a bespoke kernel? Check if the necessary modules are enabled.

ifupdown-scripts provides an init.d script and generates network/interfaces. Check if the latter matches your system.

Run '/etc/init.d/S40network restart' and follow up on any error messages.

Quoted 6 lines
Quoted 6 lines

However, when I boot the system with sdcard.img, the pi does not connect
to my network. Are there are things that I need to enable that are not part
of the default configuration?

Quoted 7 lines
Quoted 7 lines

My longer term goal is to ssh (using dropbear) into my pi via the LAN, and
use iwctl to configure iwd for wireless connectivity. But first I need to
establish the LAN connection. Please let me know any advice that you have,
or any documentation that you can recommend.

I relied on linux-from-scratch [1] and linux-wireless [2] while setting up wireless networking, but you might succeed just by adding wpa_supplicant and supplying the necessary configuration details.

The Buildroot package handles wpa_supplicant via an ifup/down script; if you use a (custom, via skeleton) init.d script instead, you need to adapt network/interfaces.

Quoted 9 lines

Kind regards,
Andreas

Quoted 2 lines
Quoted 2 lines

Regards
Andy

[1] https://www.linuxfromscratch.org/
[2] https://wireless.wiki.kernel.org/

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot