[BlueOnyx:21955] Re: Blueonyx 5209R - strange behavior. Server sends mails from wrong IP

[Dirk Estenfeld]

Hello Michael,

> This is *not* a 5209R, correct? The thing here is that 5207R/5208R had a
> long standing "specialty" that it didn't set up all routes that it
> should have set up. This actually goes way back and I'm no longer even
> sure if BlueQuartz also had the issue or if the bug was introduced with
> CentOS 5.

You mean the output of the second server.
For sure this is also a 5209R

ssh xx.xx.91.153 -l adminuser
adminuser at xx.xx.91.153's password:
Last login: Wed Apr 18 08:20:08 2018 from ...
[adminuser at server ~]$ cat /etc/build
build 20180208 for a 5209R in en_US

> Could you please check if your /etc/sysconfig/network does have this
> line in it:
>
> GATEWAYDEV="eth0"
>
> Additionally please check of it has ...
>
> GATEWAY="xx.xx.91.1"
>
> ... in it. I'd like to know if it has one or the other or both. Because
> depending on what /usr/sausalito/handlers/base/network/change_route.pl
> finds it does things a bit different.

Server with issue:
GATEWAYDEV="eth0" is missing
GATEWAY="xx.xx.91.1" is existing

Server without issue:
GATEWAYDEV="eth0" is missing
GATEWAY="xx.xx.91.1" is existing


> Speaking of which, there is another thing I'd like you to do:
>
> Edit /usr/sausalito/handlers/base/network/change_route.pl and turn on
> debugging by changing ...
>
> $DEBUG = "0";
>
> ... to this:
>
> $DEBUG = "1";
>
> Then run the handler this way from the command line as root:
>
> /usr/sausalito/handlers/base/network/change_route.pl -c 2
>
> Please report back what it shows on the shell.

Here is the output:

---
/usr/sausalito/handlers/base/network/change_route.pl -c 2
Running: starting
/usr/sausalito/handlers/base/network/change_route.pl: starting.
Running: My primary IPv4 ipaddr: xx.xx.91.192
Running: My primary IPv4 netmask: 255.255.255.0
Running: My primary IPv6 ipaddr:
Route for primary IPv4 IP xx.xx.91.192 already exists.
Running: Found extra IPv4 IP: xx.xx.91.193 ... already has a route.
@unique_netroutes: $VAR1 = [
          'xx.xx.91.0'
        ];

@routes_existing_ipv4: $VAR1 = [];

@routes_existing_ipv6: $VAR1 = [];

/sbin/ip route add xx.xx.91.0/255.255.255.0 dev eth0
RTNETLINK answers: File exists
Running: Loopback ... already has a route.
---

> FWIW: It might be worth a try to edit that handler and to comment out
> the "if"-condition right under this comment:
>
> # Make sure all IPv4 extra-IPs have routes:
>
> That should be lines 230-267 and this deals with the routes for the
> alias IP's (anything but the primary IPv4 IP).

Should I do this?

Best regards,
Dirk

---

blackpoint GmbH - Friedberger Straße 106b - 61118 Bad Vilbel