Hi all,
I have a problem manually replicating on a second server the same route
configuration that has been automatically set up in the first one by an
application
Each server has two nics with ips on two different /20 subnets:
10.50.16.0/20 (the second nic) and 10.50.32.0/20 (the first nic)
I appreciate any suggestion from the experts here.
first server:
$ip a
...
2: ens300f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state
UP group default qlen 1000
...
altname enp65s0f0np0
inet 10.50.42.76/20 brd 10.50.47.255 scope global dynamic noprefixroute
ens300f0np0
...
3: ens300f1np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state
UP group default qlen 1000
...
inet 10.50.22.126/20 brd 10.50.31.255 scope global noprefixroute br-ex
$ ip r
default via 10.50.16.1 dev ens300f1np1 proto static metric 48
default via 10.50.32.1 dev ens300f0np0 proto dhcp src 10.50.42.76 metric
100
10.50.16.0/20 ens300f1np1 proto kernel scope link src 10.50.22.126 metric
48
10.50.32.0/20 dev ens300f0np0 proto kernel scope link src 10.50.42.76
metric 100
second server:
$ ip a
...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group
default qlen 1000
...
altname enp65s0f0
altname ens300f0
inet 10.50.39.223/20 brd 10.50.47.255 scope global noprefixroute eth0
...
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group
default qlen 1000
...
altname enp65s0f1
altname ens300f1
inet 10.50.25.153/20 brd 10.50.31.255 scope global noprefixroute br-ex
$ ip r
default via 10.50.16.1 dev eth1 proto static metric 48
default via 10.50.32.1 dev eth0 proto static metric 100
10.50.16.0/20 dev eth1 proto kernel scope link src 10.50.25.153 metric 48
10.50.32.0/20 dev eth0 proto kernel scope link src 10.50.39.223 metric 100
it seems all ok but in some circustances I get differen behaviour that let
me think the responsible could be the different "default" line setting on
the first interface
default via 10.50.32.1 dev ens300f0np0 proto dhcp src 10.50.42.76 metric
100
--> OK first server automatically configured, even if I think it is not
correct to have two "default" lines...
default via 10.50.32.1 dev eth0 proto static metric 100
--> KO second server
I don't understand what the "src 10.50.42.76" means and how to put it in
the second server too
I tried to use
nmcli con mod eth0 ipv4.never-default yes
but it seems not to create that part....
also the command
ip route del default dev eth0
remove the line but probably some services have already started considering
that interface as the one for host ip and uncorrectly bound to it
The first nic manages an iscsi boot and I suspect I have to dig in its
external initialization, but any hint on the produced difference with the
"src 10.50.42.76" could help
Thanks in advance,
Gianluca
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
