Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #5315
| From | Ralf Fassel <ralfixx@gmx.de> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: DHCP as default for new network interface |
| Date | 2023-06-30 11:05 +0200 |
| Message-ID | <ygazg4hgw0l.fsf@akutech.de> (permalink) |
| References | <yga8rc3imcd.fsf@akutech.de> <ib6umjx5r1.ln2@Telcontar.valinor> <yga4jmqihot.fsf@akutech.de> <ssa0njx0s7.ln2@Telcontar.valinor> |
* "Carlos E.R." <robin_listas@es.invalid> | On 2023-06-29 14:20, Ralf Fassel wrote: | > * "Carlos E.R." <robin_listas@es.invalid> | > | On 2023-06-28 18:27, Ralf Fassel wrote: | > | > Opensuse 15.4 if it matters. | > --<snip-snip>-- | > | > However, I would like to have DHCP as default for an new network | > | > adapter | > | > attached, so I don't need to fire up network configuration each time I | > | > add a new network adapter. | > | > How would I go for this? | >> | > | I think you should use Network Manager instead of wicked. | > Thanks for the suggestion, which reminded me that I indeed chose | > 'wicked' on installation some years ago and kept that throughout the | > releases. | > I tried to change to Networkmanager in yast, but it immediately | > complained it required some app or other (did not say exactly which) to | > run properly - I do not run KDE or Gnome desktop :-/, and Yast said it | > could not longer control the interface options (since Networkmanager did). | > At that point I remembered *why* I had changed to wicked... and | > decided | > that I do not want the original requested feature *that* much. | > Thanks > | Ok, so... did you manage to change to NM? Does it work? No, I haven't changed (yet). NM looks promising, but the messages when switching to it in yast (even *before* 'Apply') scared me off, since right now I did not want to spend the time investigating if something went wrong. However, I will try it on the next OS release update (15.5 is already released). | Yes, when you change to NM, YaST can no longer control/configure the | connections, except some items (notably, computer name). And it | probably needs to install somethings, which should be handled | automatically, no matter what desktop you use (or even in text mode). Sounds like 'nmcli' is the tool in question. | openSUSE is removing wicked in the future, going for NM only. Good to know. TNX R'
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
DHCP as default for new network interface Ralf Fassel <ralfixx@gmx.de> - 2023-06-28 18:27 +0200
Re: DHCP as default for new network interface "Carlos E.R." <robin_listas@es.invalid> - 2023-06-28 19:13 +0200
Re: DHCP as default for new network interface Ralf Fassel <ralfixx@gmx.de> - 2023-06-29 14:20 +0200
Re: DHCP as default for new network interface "Carlos E.R." <robin_listas@es.invalid> - 2023-06-29 14:43 +0200
Re: DHCP as default for new network interface Ralf Fassel <ralfixx@gmx.de> - 2023-06-30 11:05 +0200
Re: DHCP as default for new network interface Bit Twister <BitTwister@mouse-potato.com> - 2023-06-29 09:27 -0500
csiph-web