MX Linux networking problem

[CharlesV]

Do you have anything that supports that conclusion?

I have several test machines that I have used under SecureBoot and have never had any issues with networking.

[Tom Dooley]

Ok, then just go on with secure boot enabled.

[MultipleX]

This forum software is driving me nuts!
Seems to keep adding posts instead of editing them!

Click on the pencil.

Yup, the pencil is what I have been clicking on to edit. Can't rule out clicking the quote by mistake but not as far as I am aware.

Wow! Lots of ideas here. Thank you!.
I did a lot of this networking 101 stuff last night and determined that its not network connectivity.
Today discovered it is actually a DHCP issue.... The MX OS did not acquire the address I was expecting it to have done and I was trying to connect to thin air....

Sounds like you have it resolved. If you need / want to make your MX machine a static IPv4, then you can use Network Manager Applet to change to a static ip. edit the connection, change to the IPv4 tab, and change from autmomatic ( dhcp) and to static and assign the ip you want. ( just keep it out of your routers dhcp pool.)

OR

If you can, go into your router and assign an ip FOR the MX machine using it's MAC address. This is a better method imo, but not everyone has this ability.

Assigning an IP gfor the MAC address on the router is exactly what I did quite some time ago as my router does have this ability. I also use that for a couple of Raspberry Pis. It works fine for the Pis and for Mint but for some reason not for MX. If anyone has any ideas as to why, then I am interested to know. Could it be a bug in dhclient on MX perhaps? As a workaround I have manually assigned a static IP in MX - by as you say, changing from automatic to manual and add the IP/mask/gateway details.

[MultipleX]

Are you trying to say having secureBoot enabled is causing his network issue?

Maybe.

Please elaborate. Secure boot affects the boot up process for sure, but once the system is booted, it should behave the same as usual. I am aware that secure boot can cause DKMS drivers to fail because they would need to be signed, but I am using the shim so it shouldn't be an issue. I can always test it with secure boot disabled. It only needs to be on for Win anyway.

[FullScale4Me]

Have you looked at The Debian Administrator's Handbook section 8.2. Configuring the Network

or https://www.debian.org/doc/manuals/debian-reference/ch05.en.html ?

[siamhie]

This forum software is driving me nuts!
Seems to keep adding posts instead of editing them!

Click on the pencil.

Yup, the pencil is what I have been clicking on to edit. Can't rule out clicking the quote by mistake but not as far as I am aware.

checkmark.png

From left to right. Edit post, Information, Reply with quote and Accept this answer.

[atomick]

Try this here are examples of 1st .
/etc/network/interfaces file this works better for DHCP alone in MX

cat /etc/network/interfaces looks like this with 2 lines I added to common MX-defined entry to interfaces.

Code: Select all

 # interfaces(5) file used by ifup(8) and ifdown(8)

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto wlan0
iface wlan0 inet dhcp  

only these 2 lines, next we move over to /etc/NetworkManager/system-connections/

Continue to setting your Static via NetworkManager and or the Icon on the Desktop Tool panel beside speaker apps button there. right click
I'm going to add an idea for you to which you may actually manually write your own network definitions for each interface
or use this info as a template to build in your own. Details to figures and numbers game entries.

Code: Select all

  #----------------/etc/NetworkManager/system-connections   
:::::::::::::: Example: -more of both my devices.nmconnection  files wlan0 an eth0  yet filenames would be myWifi.nmconnection and StaticWired.nmconnection
myWifi.nmconnection
::::::::::::::
[connection]
id=SSIDname   # this is your SSID on your router as you defined
uuid=83935c68-2222-1111-3333-1c4efba11zd2
type=wifi
interface-name=wlan0
timestamp=11111111

[wifi]
mode=infrastructure
ssid=aSSIDname

[wifi-security]
key-mgmt=wpa-psk
psk=funkyKeypass

[ipv4]
method=auto

[ipv6]
addr-gen-mode=stable-privacy
method=disabled

[proxy]
::::::::::::::  
StaticWired.nmconnection
::::::::::::::
[connection]
id=myPrivate_Static_eth0
uuid=e7de3bcd-cd08-3439-a605-ccffa7e38333   # all these are none real your own hardware will fill in similar
type=ethernet
autoconnect-priority=-999
interface-name=eth0
timestamp=111111111

[ethernet]
duplex=full
mac-address=n2:R1:65:44:D2:36
mtu=9000
speed=10000

[ipv4]
address1=10.10.100.2/29
may-fail=false
method=manual
never-default=true
route1=10.10.100.2/29,10.10.100.1,100

[ipv6]
addr-gen-mode=stable-privacy
method=disabled

[proxy] 

Here you can write these files or configure them matching what the NetworkManager Icon provides to each tab at the top. "Ethernet IPv4 IPv6" tabs
simply set thru match and configure to your own detail schema. once you have set

sudo /etc/init.d/NetworkManager restart

to reset the network although be real honest. A warm reboot cycle would set things all right! this is all standard text so featherpad can work setting things up. Worth a try.
PS: my wired are 2.5gig speeds so seeing 9000 as mtu is in some hs docs for such settings. /etc/sysctl.conf has kernel settings will leave out but 1500 could least get you started to change from 9000.
and set speed to 1000. Again depending on your net. Pi-devices don't really work at Gig Speeds but setting all the same can work.
All numbers are changed from my own network and used a cool Perl tool ipcalc for the 10.10.100.1/29 network information.
All hopes this pokes a hole in the elephant at the end 'it works' or hard codes getting you close w/o hair pull.

[CharlesV]

Wow! Lots of ideas here. Thank you!.
I did a lot of this networking 101 stuff last night and determined that its not network connectivity.
Today discovered it is actually a DHCP issue.... The MX OS did not acquire the address I was expecting it to have done and I was trying to connect to thin air....

Sounds like you have it resolved. If you need / want to make your MX machine a static IPv4, then you can use Network Manager Applet to change to a static ip. edit the connection, change to the IPv4 tab, and change from autmomatic ( dhcp) and to static and assign the ip you want. ( just keep it out of your routers dhcp pool.)

OR

If you can, go into your router and assign an ip FOR the MX machine using it's MAC address. This is a better method imo, but not everyone has this ability.

Assigning an IP gfor the MAC address on the router is exactly what I did quite some time ago as my router does have this ability. I also use that for a couple of Raspberry Pis. It works fine for the Pis and for Mint but for some reason not for MX. If anyone has any ideas as to why, then I am interested to know. Could it be a bug in dhclient on MX perhaps? As a workaround I have manually assigned a static IP in MX - by as you say, changing from automatic to manual and add the IP/mask/gateway details.

Using the router and assigning on the MAC address is exactly how my MX machines work. Something is off with your mac or router if its not working for you.

[DukeComposed]

Using the router and assigning on the MAC address is exactly how my MX machines work. Something is off with your mac or router if its not working for you.

DHCP works like this: You build or buy a network device, something like a cable modem from your ISP or a wireless access point or you build a server yourself. It runs dhcpd and it listens for machines on your LAN that are booting up and connecting for the first time asking for an IP address. The network device says "I've been told you can have something between 192.168.0.10 and 192.168.0.100, so you get, um, 192.168.0.11 and no one else will get that address from me. I'll write that down." And then it does.

DHCP servers issue ephemeral leases, and those leases can be renewed... or not. If a machine drops off the network and fails to renew the lease before it expires it isn't guaranteed to get the same IP address again.

How do you get an IP address on a LAN without an IP address? You use your MAC address. MAC addresses are hard-coded strings like "00:11:22:33:44:55" and they're unique per network interface. If you have a laptop, the laptop's Ethernet port has a different MAC address than the 802.11 wireless adapter. But there's something else.

Hard-coded IPs. I can set up DHCP as perfectly as anyone could, but if a friend comes over to my place with a laptop and has his wireless card set to always use 192.168.0.11 because that's how he runs his home network, it's going to conflict with my LAN. My DHCP server just assigns IP addresses. That's it. But it's already allocated 192.168.0.11, so its job is done. The machine with a DHCP client got 192.168.0.11 assigned to it and it's happy. Now my buddy comes alone with a machine that didn't touch DHCP, doesn't care what DHCP is, and says, "Hey, LAN. I'm 192.168.0.11. Here are my packets."

IP is really, really bad at conflicting address resolution. Packets can go to my machine. Packets can go to my buddy's laptop. It's chaos. Avoid chaos.

In this case, OP needs to check the MAC address of the machine, confirm the network interface has the same MAC address in Mint and MX, meaning there's no macchanger-style MAC address randomizing software being used here, and when both Mint and MX agree that the network interface has, say, "11:22:33:44:55:66" as its MAC address, to put a DHCP reservation into the network device -- a reservation is a lease that never expires -- so that this exact hardware device will always, always, be issued the same IP address, and that no other device will get that address just because it hasn't been leased recently.

[CharlesV]

@DukeComposed Thank you duke. What I was trying to convey to the op, and did a very poor job of saying, is that MX works like all the rest of the linux distro's in how it does dhcp. And that the pinning the ip with his Mac SHOULD work just like all the rest. This method is exactly how I run many networks - letting the router be the brain on "static" ips.