610685d27b
### Why I did it An in-band syslog server will not receive any syslog if it is configured without a VRF specified, which is because `eth0` is always specified as the `device` of a syslog server and the syslog packets will be sent to `eth0` regardless of its destination IP address. ### How I did it Pass the option "device" in rsyslog.conf only if when syslog server's source address is configured with a non-default VRF #### How to verify it Manually test: 1. Configuring a syslog server without VRF specified or with `default` as the VRF: no `device` passed in `rsyslog.conf` 2. Configuring a syslog server with non-default VRF: the configured VRF passed as `device` in `rsyslog.conf` |
||
|---|---|---|
| .. | ||
| backend_acl | ||
| bash | ||
| config-chassisdb | ||
| config-setup | ||
| config-topology | ||
| constants | ||
| containercfgd | ||
| copp | ||
| corefile_uploader | ||
| cron.d | ||
| ebtables | ||
| environment | ||
| fstrim | ||
| hostname | ||
| interfaces | ||
| kdump | ||
| kubernetes | ||
| logrotate | ||
| misc | ||
| monit | ||
| ntp | ||
| pcie-check | ||
| pip | ||
| platform | ||
| rasdaemon | ||
| readline | ||
| reset-factory | ||
| resolv-config | ||
| rsyslog | ||
| secureboot | ||
| smartmontools | ||
| snmp | ||
| sudoers | ||
| sysctl | ||
| syslog | ||
| system-health | ||
| systemd | ||
| topology | ||
| warmboot-finalizer | ||
| watchdog-control | ||