Network manager always connects to eth0, instead of 'Home' profile

Johncc330 · 08-19-2023, 09:21 AM

On a newly installed Slackware64-15.0, NetworkManager always connects to eth0, though

There is no profile eth0
There _is_ a profile 'Home'
I tried to define eth0 as unmanaged device
I tried to set Home as autoconnect

This is quite annoying, as the parameters associated with 'eth0' don't work anywhere for me, so I first have to change to 'Home' or whatever.

camorri · 08-20-2023, 12:04 PM

Not sure what you mean by 'profile'.

Can you be more specific? Where, and how did you configure eth0? There are more ways than 1 in Slackware.

You can configure it a file /etc/rc.d/rc.inet1.conf or you use the Connections in KDE. I'm guessing you used the connections method, however, please clarify.

The first enthernet device is known as eth0, the second is eth1 and so on.

Can you clarify what you are trying to accomplish, as it is not clear by what you have posted.

Johncc330 · 08-20-2023, 02:37 PM

Quote:

Not sure what you mean by 'profile'.

I mean 'NetworkManager' profile or configuration. I have a profile called 'Home' with the internal ethernet
addresses, and another at the university where I have to use DHCP

Quote:

Can you be more specific? Where, and how did you configure eth0? There are more ways than 1 in Slackware.
You can configure it a file /etc/rc.d/rc.inet1.conf or you use the Connections in KDE. I'm guessing you used the connections method, however, please clarify.

The first enthernet device is known as eth0, the second is eth1 and so on.

eth0 is configured by rc.inet1.conf, and works fine when using it as connection to my 'big' computer.

Quote:

Can you clarify what you are trying to accomplish, as it is not clear by what you have posted

.

I want to configure wlan0 as an access point and route traffic to eth0 if the IP is not in the local net.

Using nmcli, I configured wlan0 successfully as an Access Point. It is active (i.e. transmitting beacons),
and I can connect with my phone. For the moment, I didn't configure any encryption - till I find out how
to do whatever is necessary to get from the wlan0 to eth0. I suspect that is the reason I get 'Connected,
no internet'.

Kernel ip4 forwarding is enabled. The script to enable the AP I'm using is about as standard as it can get.

It worked with my previous notebook. The wifi chip is different, but the kernel seems happy, and using
'iwlist wlan0 scan' I can see neighbourhood traffic. And, as mentioned above I _can_ connect.

__________________

camorri · 08-20-2023, 03:36 PM

Thank-you for clarifying. I have not set that up myself, however a little searching turned up this.

Quote:

You'll need to enable ip_forwarding:

echo 1 >/proc/sys/net/ipv4/ip_forward

Set a default route out of eth0:

ip route add default via 192.168.137.1

Then tell clients on the wlan0 LAN to use 192.168.144.111 as their gateway. If you control the dhcp server, change your gateway in the dhcp config.

You'll probably need to set up NAT as well, if you want clients on 192.168.144.0/24 to connect to the internet:

iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

You will have to adjust the IP addresses for your network. Hope this helps.