Jump to content

Recommended Posts

Posted

The espressobin has three ethernet ports.  In Ubuntu Armbian, left to right (looking into the ports), they're called "lan1", "lan0", and "wan". 

 

The weird thing is that you can't bring them up until you've *first* brought up eth0, which is not associated with a physical port.  This causes all kinds of havoc trying to use /etc/network/interfaces/, because it takes a couple of seconds for eth0 to come up, in which time the other interfaces have already failed.

 

1) What is this mysterious eth0?

 

2) My attempts to bridge lan0 and lan1 from .../interfaces have failed.  Got an example you can give me?

Posted
On 11/5/2017 at 9:52 PM, Igor said:

We use systemd-networkd at Espressobin. Check those manuals/examples:

 

Fair enough.  I guess I've been grumpy about systemd long enough, time to figure out what it is.  Thanks for the nudge.

Posted
23 hours ago, zador.blood.stained said:

SoC/CPU network interface that connects to the Topaz switch

So I guess I'm one of today's 10,000.  Lucky me!  And thanks.

Posted
On 11/6/2017 at 11:22 AM, Igor said:

We use systemd-networkd at Espressobin. Check those manuals/examples:

 

http://xmodulo.com/switch-from-networkmanager-to-systemd-networkd.html

https://wiki.archlinux.org/index.php/systemd-networkd

 

Leave /etc/network/interfaces empty.

 

I tried to set a static IP using armbian-config. It configured /etc/network/interfaces file instead of the file in /etc/systemd/network.

When this happened, br0 had 2 IPs, which were set by systemd DHCP and /etc/network/interfaces static IP I guess.

Anyway commenting out /etc/network/interfaces and setting the correct values in /etc/systemd/network/10-br0.network worked for me.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines