Hi,
> I have a fedora38 server that's been updated to new versions many times over the years. It seems now I'm having a problem with the static route I created many years ago no longer being supported. I knew this was coming, but I'm unfamiliar with the new methods. I'm using the old network-tools method, not NM or even nmcli.
>
> It clearly doesn't understand my current config:
> Nov 16 15:25:52 mail03 network[1123]: Bringing up interface enp0s31f6:
> Nov 16 15:25:52 mail03 network[1313]: INFO : [ipv6_wait_tentative] Waiting for interface enp0s31f6 IPv6 address(es) to leave the 'tentative' state
> Nov 16 15:25:52 mail03 ipv6_wait_tentative: Waiting for interface enp0s31f6 IPv6 address(es) to leave the 'tentative' state
> Nov 16 15:25:53 mail03 network[1313]: INFO : [ipv6_wait_tentative] Waiting for interface enp0s31f6 IPv6 address(es) to leave the 'tentative' state
> Nov 16 15:25:53 mail03 ipv6_wait_tentative: Waiting for interface enp0s31f6 IPv6 address(es) to leave the 'tentative' state
> Nov 16 15:25:54 mail03 network[1370]: Error: either "to" is duplicate, or "gw" is a garbage.
> Nov 16 15:25:54 mail03 network[1368]: WARN : [/etc/sysconfig/network-scripts/ifup-routes] Failed to add route 192.168.1.0/24 gw 68.195.11.42 dev enp0s31f6, using ip route replace instead.
> Nov 16 15:25:54 mail03 /etc/sysconfig/network-scripts/ifup-routes: Failed to add route 192.168.1.0/24 gw 68.195.11.42 dev enp0s31f6, using ip route replace instead.
> Nov 16 15:25:54 mail03 network[1372]: Error: either "to" is duplicate, or "gw" is a garbage.
> Nov 16 15:25:54 mail03 NET[1386]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
> Nov 16 15:25:54 mail03 network[1123]: [ OK ]
>
> In /etc/sysconfig/network-scripts/route-enp0s31f6 I have the following:
> 192.168.1.0/24 gw 68.195.11.42 dev enp0s31f6
>
> In /etc/sysconfig/network-scripts/ifcfg-enp0s31f6 I have the following (my domain sanitized):
> # cat ifcfg-enp0s31f6|grep -Ev '^$|^#'
> HWADDR=4c:ed:fb:bb:47:93
> BOOTPROTO=static
> DEVICE=enp0s31f6
> TYPE=Ethernet
> _ONBOOT_=yes
> IPADDR=68.195.11.45
> GATEWAY=68.195.11.41
> NETMASK=255.255.255.248
> PREFIX=29
> SEARCH="example.com"
> DOMAIN="example.com"
> DNS1=127.0.0.1
> ZONE=FedoraServer
> NM_CONTROLLED=no
>
> I'm also still using iptables, not firewalls or ipfw.
>
> Ideas on how to "upgrade" my server would be greatly appreciated.
The first step you should do is to migrate the /etc/sysconfig/network-script to the NetworkManager standard configuration in /etc/NetworkManager. The /etc/sysconfig-method got deprecated some times ago and iwas withdrawn with F37 or so (don’t remember the exact release, it feels like it was soooo long ago). The network guys provided a nice migration tool which does all the work. Search the Fedora Magazine, there was an informative article about the migration process. (Just found it: https://fedoramagazine.org/converting-networkmanager-from-ifcfg-to-keyfiles/). The migration tool migrates the static routes, too.
In case of difficulties, feel free to ask. Maybe on our Fedora Server mailing list.
This was a big help, thanks. The only thing it didn't do was migrate my static route. I installed NetworkManager-tui and used the text interface to add it manually. Now that I see what I did, I could probably do it again manually.
I'll also join the Fedora Server mailing list after all these years.
-- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
