On 10/4/25 12:07, Rainer Gerhards wrote:
An alias like lo:1 is*not a real device* from the kernel’s perspective;
it’s a historical syntax for assigning an additional address to lo.
Binding the TCP sender to lo (loopback) while connecting to a remote
host will fail, because packets cannot egress via lo. That’s why rsyslog
logs “unable to bind.”
That's a good point. Let me try a tun device, this should be a "real" device
in linux land.
I know ip is better, but ifconfig is faster to type ;-)
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
