Network Reachability Changed, Immediate Out of Memory Crash

Hi @rcrawley

I stumbled on this tread about your problems with Ubuntu 22.04
What strikes me is the lack of information about the actual configuration of your network, a topology overview and actual configuration of the Ubuntu machine.
The information you provide is fragmented, non substancial and inconclusive.
What also can be a factor is your knowledge on Linux and Networking, no info about that.

I tried to look at your problem, but there are no clues for me to guide you to a solution, and the community probably can not as well.

To get a solution your only option is to provide relevant informationā€¦
Your network topology, ā€œEthernet between RoonCore and Cambridgeā€ does not cut it.
How is the Ubuntu machine configured, does it have a fixed IP address, DHCP, custom configurations you made in /etc/*, patch level etc etc.

ā€¦
Anyways, my Core is an Mac Mini i7 2012 with Ubuntu 22.04.3 LTS.
It runs smooth with no issues ā€¦

Since you run Ubuntu on a MacBook Pro, did you configure it to run as a ā€œserverā€, eg. use GitHub - linux-on-mac/mbpfan: A simple daemon to control fan speed on all MacBook/MacBook Pros (probably all Apple computers) for Linux Kernel 3 and newer etc.?

Good luck with solving your issue :+1:t2:
(disclaimer: this post does not commit me to help you in any way or form in the future.)

Hi @PeterD. I canā€™t decide if I appreciate your bluntness or if I feel your response is unnecessarily harsh. :slight_smile: Nonetheless, here you go.

Iā€™ve provided more networking details further up in the thread:

I feel like my CV is a bit of a strange ask in general but also given the details Iā€™ve provided above, but if it helps: Iā€™ve been managing *nix machines professionally for many decades.

  • Linux config set to DHCP, static IP provided by the upstream router
  • No custom network configurations, OOTB
  • Patch level is current (managed via apt update)
$ nmcli device show
GENERAL.DEVICE:                         enx00e04c0425b4
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:E0:4C:04:25:B4
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     Wired connection 1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.1.15/24
IP4.GATEWAY:                            192.168.1.1
IP4.ROUTE[1]:                           dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.ROUTE[3]:                           dst = 0.0.0.0/0, nh = 192.168.1.1, mt = 100
IP4.DNS[1]:                             192.168.1.1
IP4.DOMAIN[1]:                          lan
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         enx00e04c68041d
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:E0:4C:68:04:1D
GENERAL.MTU:                            1500
GENERAL.STATE:                          20 (unavailable)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --

I assume youā€™re asking which pre-configured build I installed? Linux Mint Cinnamon:

$ cat linuxmint/info 
RELEASE=21.1
CODENAME=vera
EDITION="Cinnamon"
DESCRIPTION="Linux Mint 21.1 Vera"
DESKTOP=Gnome
TOOLKIT=GTK
NEW_FEATURES_URL=https://www.linuxmint.com/rel_vera_cinnamon_whatsnew.php
RELEASE_NOTES_URL=https://www.linuxmint.com/rel_vera_cinnamon.php
USER_GUIDE_URL=https://www.linuxmint.com/documentation.php
GRUB_TITLE=Linux Mint 21.1 Cinnamon

And Iā€™m guessing this would be your next question:

$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination  

$ sudo ufw status
Status: inactive

None expected. I wouldnā€™t expect a non-Roon support employee to help support very specific Roon behaviors, issues, and logs, but the conversation and ideation is always appreciated.