http://bugzilla.opensuse.org/show_bug.cgi?id=1047939 Bug ID: 1047939 Summary: ipv4 link local route not set on AWS AMI Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: rene@linuxfoundation.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hi, As per summary. When booting openSUSE 42.2 (also confirmed with upgrade to 42.3), the route table is missing the ipv4 link local network route. # ip r s default via 10.60.31.254 dev eth0 10.60.16.0/20 dev eth0 proto kernel scope link src 10.60.16.154 10.60.87.144/28 dev eth1 proto kernel scope link src 10.60.87.152 I would expect to see a route like this: # ip ro s match 169.254.169.254 169.254.0.0/16 dev eth0 scope link metric 1002 Without this route, users cannot access http://169.254.169.254 correctly. In the first route table provided, packets with destination of 169.254.169.254 would go via 10.60.31.254. If 10.60.31.254 was configured to NAT, this causes the metadata service to receive packets from 10.60.31.254 and not the server sending the original packet. This causes all sorts of trouble for EC2 instances within AWS, especially if they rely on IAM roles/profiles. Potential fix is to add the route to /etc/sysconfig/network/routes and restart wicked.service. 169.254.0.0/16 - - eth0 -- You are receiving this mail because: You are on the CC list for the bug.