On 27/10/2020 17:36, Roberto Ragusa wrote:
Maybe your problem is just in how to achieve this with NetworkManager,
which is probably not the right tool for these "non desktop" setups.
I must admit that I don't have a lot of experience with NetworkManager -
I've been clinging onto the old network scripts. :)
RHEL/CentOS, which are really "non-desktop" distros, are pretty much
moving everything onto NetworkManager, so I think that'll be the way for
everything soon.
I vaguely recall hearing that the network-scripts package was going away
entirely in RHEL 9, but I'm not sure where I heard that so might be
making that up. In any case, since it looks like NetworkManager will be
the future, I'm trying to get my head around it a bit more.
With good old ifcfg scripts you do not even need aliases anymore, I
achieve a similar configuration through:
IPADDR=x.x.x.2
NETMASK=255.255.255.254 (this is to catch the router at x.x.x.1, your
correct mask is another possible option here)
IPADDR0=x.x.x.3
NETMASK0=255.255.255.255
IPADDR1=x.x.x.4
NETMASK1=255.255.255.255
...and so on
(for IPV6 you would need IPV6ADDR and a single line with
IPV6ADDR_SECONDARIES).
Well, you still end up with numerous addresses attached to the NIC
itself. It's not *too* bad with IPv4 since you're probably dealing with
only a few tens or hundreds of addresses in a subnet. I can't imagine
it working at all for an IPv6 /64 though.
This solution certainly works (for the IPv4 case), it just feels like
there should be a better way of saying "answer ARP / neighbour discovery
for anything in this whole network", rather than having attach each
individual IP address to the NIC.
--
- Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
