Share pc internet with dietpi via ssh

Fernando · 1 February 2024 12:40

this is consuming too much time with little results, deciding against wasting more time with this project

Jappe · 1 February 2024 12:44

What OS is running on the PC?

Joulinar · 1 February 2024 12:49

should be Linux according to the other forum post where OP tried to connect a Neo directly instead of connecting it to his broadband router.

@Fernando
you might need to setup a bridged interface on your desktop computer BridgeNetworkConnections - Debian Wiki

Fernando · 1 February 2024 13:29

this is consuming too much time with little results, deciding against wasting more time with this project

Fernando · 2 February 2024 09:45

this is consuming too much time with little results, deciding against wasting more time with this project

Jappe · 2 February 2024 11:56

You add eth1 and eth2 to the bridge and later you config eth2 (which you don’t need) and add br0 to eth2, which makes no sense (you can not define a bridge port on a physical interface)

I guess you would just need something like:

auto br0
iface br0 inet static
    bridge_ports eth1 eth2
    address 192.168.1.2
    netmask 255.255.255.0
    gateway 192.168.1.1

Like shown in the debian wiki

Fernando · 2 February 2024 12:19

this is consuming too much time with little results, deciding against wasting more time with this project

Jappe · 2 February 2024 14:52

Do you use also DietPi on the PC?

Jappe · 2 February 2024 15:40

So I tested it on a RPi 3b and made a bridge between eth0 ~~and wlan0~~. If you use Debian with network manaher or some other OS with network manager you have to follow tutorials for that OS or for a networkl config which uses network manager.
On DietPi we use only ifupdown and I got it working with. (I tried to add wlan0 to the bridge too, but the wifi chip from the RPi 3 does not support bridging, so I just added eth0)

apt install bridge-utils
nano /etc/network/interfaces

content of /etc/network/interfaces:

# Location: /etc/network/interfaces
# Please modify network settings via: dietpi-config
# Or create your own drop-ins in: /etc/network/interfaces.d/

# Drop-in configs
source interfaces.d/*

#lo
auto lo
iface lo inet loopback

# Ethernet
allow-hotplug eth0
iface eth0 inet manual

#bridge
auto br0
iface br0 inet static
    bridge_ports eth0 wlan0
    address 192.168.178.60
    netmask 255.255.255.0
    gateway 192.168.178.1
    dns-nameservers 9.9.9.9 1.1.1.1

Then I did:

ifdown --force eth0 br0 && ifup br0 && ifup eth0

root@DietPi:~# ip a gives me now:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
    link/ether b8:27:eb:50:48:0b brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether b8:27:eb:05:1d:5e brd ff:ff:ff:ff:ff:ff
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b8:27:eb:50:48:0b brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.60/24 brd 192.168.178.255 scope global br0
       valid_lft forever preferred_lft forever
    inet6 fe80::ba27:ebff:fe50:480b/64 scope link
       valid_lft forever preferred_lft forever

Everything done via ssh.
Before the bridging eth0 had the IP 192.168.178.60 now the bridge has it.

I did also some connection checks:

root@DietPi:~# ping dietpi.com
PING dietpi.com (172.67.170.219) 56(84) bytes of data.
64 bytes from 172.67.170.219 (172.67.170.219): icmp_seq=1 ttl=58 time=13.5 ms
64 bytes from 172.67.170.219 (172.67.170.219): icmp_seq=2 ttl=58 time=12.4 ms
^C
--- dietpi.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 12.413/12.979/13.545/0.566 ms

root@DietPi:~# wget dietpi.com
--2024-02-02 15:42:31--  http://dietpi.com/
Resolving dietpi.com (dietpi.com)... 172.67.170.219, 104.21.28.141, 2606:4700:3030::6815:1c8d, ...
Connecting to dietpi.com (dietpi.com)|172.67.170.219|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://dietpi.com/ [following]
--2024-02-02 15:42:31--  https://dietpi.com/
Connecting to dietpi.com (dietpi.com)|172.67.170.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

index.html              [ <=>                ] 169.28K  --.-KB/s    in 0.04s

2024-02-02 15:42:31 (4.69 MB/s) - ‘index.html’ saved [173339]

Fernando · 4 February 2024 09:46

this is consuming too much time with little results, deciding against wasting more time with this project

Jappe · 4 February 2024 09:50

In your case you have to config it on your PC.
But if you use standard debian with network manager then some extra config is probably needed.

What do you use on your PC?

Fernando · 4 February 2024 11:10

this is consuming too much time with little results, deciding against wasting more time with this project

Jappe · 4 February 2024 12:16

Exactly, every interface which should be part of the bridge needs to set to be unconfigured or set to manual-
This is also important if you use network manager, like they say in the debian wiki:

# Set up interfaces manually, avoiding conflicts with, e.g., network manager
 iface eth0 inet manual
 iface eth1 inet manual

Fernando · 4 February 2024 12:46

this is consuming too much time with little results, deciding against wasting more time with this project

Joulinar · 4 February 2024 13:04

I know I asked this more than once already, but never got an answer on this. How does your desktop connect to the internet? Is it connected to a broadband router? How do you access the internet?

Fernando · 4 February 2024 13:19

this is consuming too much time with little results, deciding against wasting more time with this project

Joulinar · 4 February 2024 13:59

again, without any knowledge this is not suppressing.

I did a test myself using an Orange Pi Zero 3 and a RPi4. Got the bridge up in less than 5 minutes.

OPi Zero 3 is connected to internet
OPi Zero 3 with onboard eth0 and a USB-to-Ethernet adapter eth1
RPi4 is connected to OPi Zero 3 via lan cable

Following the Debian guide BridgeNetworkConnections - Debian Wiki

apt install bridge-utils
brctl addbr br0
brctl addif br0 eth0 eth1
replace /etc/network/interfaces as follow
nano /etc/network/interfaces
add

# Location: /etc/network/interfaces
# Please modify network settings via: dietpi-config
# Or create your own drop-ins in: /etc/network/interfaces.d/

# Drop-in configs
source interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# Set up interfaces manually, avoiding conflicts with, e.g., network manager
iface eth0 inet manual
iface eth1 inet manual

# Bridge setup
auto br0
iface br0 inet dhcp
bridge_ports eth0 eth1

save & exit
reboot
Bridge interface br0 will receive an IP address via DHCP with this contig. However, you can assign a STATIC as well if STATIC was already used on eth0 before.
Nothing need to be configured on the RPI4. It’s running with default DHCP configuration because I have a DHCP server within my network who will assign correct IP address, usually a broadband router.
This is how it looks like on the Zero 3 providing the bridge interface

root@DietPiOPiZ3:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP group default qlen 1000
    link/ether 02:00:49:73:c1:28 brd ff:ff:ff:ff:ff:ff
    altname end0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
    link/ether f8:e4:3b:78:1b:00 brd ff:ff:ff:ff:ff:ff
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 02:00:49:73:c1:28 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.23/24 brd 192.168.0.255 scope global dynamic br0
       valid_lft 86388sec preferred_lft 86388sec
    inet6 fe80::49ff:fe73:c128/64 scope link
       valid_lft forever preferred_lft forever
root@DietPiOPiZ3:~#

root@DietPiOPiZ3:~# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.02004973c128       no              eth0
                                                        eth1
root@DietPiOPiZ3:~#

root@DietPiOPiZ3:~# ip r
default via 192.168.0.1 dev br0
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.23
root@DietPiOPiZ3:~#

Fernando · 4 February 2024 14:13

@Joulinar going to take a 30 min break, and after wipe all interfaces, bridges, etc, then try your method.
I think so much modifications, its causing background conflict.

Joulinar · 4 February 2024 14:20

before doing anything, check how your desktop computer internet facing interface is getting an IP address assigned. DHCP or STATIC.

Fernando · 4 February 2024 15:52

its dhcp, of which i have somewhat limited control over.