https://bugzilla.novell.com/show_bug.cgi?id=233098 Summary: kernel or amanda regression: wrong source IP addr (was OK in SL 10.0) Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: matthias.andree@gmx.de QAContact: qa@suse.de Greetings, I have an amanda setup which worked properly in SUSE Linux 10.0, but fails in openSUSE 10.2 now. It is apparently a regression WRT handling multi-homed amanda server hosts. Observed behavior below. Pertinent packages: amanda-2.5.1.1-17 kernel-default-2.6.18.2-34 Network setup: lo 127.0.0.1 eth0 192.168.1.1 eth1 192.168.0.1 <- main IP address of computer (behind a router) 192.168.0.1 also is the interface to the router, i. e. the interface to carry the default route. With SL 10.0, amanda would work properly. With OS 10.2, amanda (amcheck) logged timeouts waiting for ACK. Amanda is configured to backup 192.168.0.1, 192.168.1.2 and 192.168.0.3. With OS 10.2, I observe that even the packets sent to 192.168. tcpdumping, I found out that amanda would send packets _from_ 192.168.1.1 (rather than the expected 192.168.0.1 as would have been correct for the given path) to 192.168.0.1 and 192.168.0.3, when instead the source address should have been 192.168.0.1. I have worked around this by setting eth0's primary address to 192.168.0.1 and adding an alias of 192.168.1.1 as eth0:1, but that's just some odd and fragile hack that trades less important services, and not a solution. To me, this looks like a new kernel networking bug at first glance, since stracing amcheck, I haven't found any bind() calls to other addresses than 0.0.0.0, and the kernel is supposed to take care that it picks the right source IP for outgoing UDP traffic. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.