On Wed, 2015-09-09 at 07:28 +0200, Jean-Christian de Rivaz wrote: > Hello, > > I have successfully setup a AX25 interface and NM see it this way: > nmcli d > DEVICE TYPE STATE CONNECTION > ax0 unknown connected ax0 > eth2 ethernet unavailable -- > ttyACM0 gsm unavailable -- > lo loopback unmanaged -- > sit0 sit unmanaged -- > wlan2 wifi unmanaged -- > > The ax0 interface have only a IP address (configured while creating > the > ax0): > ifconfig ax0 > ax0 Link encap:AMPR AX.25 HWaddr MENHIR-6 > inet addr:192.168.222.16 Bcast:192.168.222.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MTU:256 Metric:1 > RX packets:832 errors:14 dropped:0 overruns:0 frame:0 > TX packets:688 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:10 > RX bytes:74961 (73.2 KiB) TX bytes:89851 (87.7 KiB) > > How can I configure NM to add a static default gateway and a static > DNS > server when, and only when, NM have to use the ax0 interface ? This > is > on a Debian Jessie system, so there is no /etc/sysconfig directory.
The device ax0 was created and upped outside of NM's knowledge, so NM created a temporary connection "ax0" to reflect that external setup. This is what you see as active in `nmcli d`. You can modify and reuse this created connection, or create a different connection (possibly deleting the generated one). Note that NM doesn't understand AX25 devices, but it should still work to do Layer3/IP configuration. In general such unknown devices is treated as "generic". If you look at the created connection `nmcli connection show ax0` you should see that it's of connection.type=generic. Basically, adjust the generic connection to have the settings you want. See `man nm-settings` for possible options. Especially the "ipv4" section. Thomas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
