Re: saddr based blackhole/unreachable route
2016-10-11 20:39 GMT+02:00 Bjørnar Ness : > Hello, netdev > > In a typical setup (eth0=internet, eth1=lan) i populate routing table > 100 with saddrs I want > dropped, and: "ip ru a pref 100 lookup table 100" > > What I would expect to see is packets with a saddr in table 100 coming > in eth0 will go out eth1, > with replies beeing dropped, but I do not see the packets going out eth1 at > all. > > Have tried searching and following the fib codepath, but have still > not managed to understand what is really going on here. Answering my own question, I guess its rp_filter kicking in here. and it also explains why I dont get icmp unreachable Is there a better way to do source based rtbh? -- Bj(/)rnar
saddr based blackhole/unreachable route
Hello, netdev In a typical setup (eth0=internet, eth1=lan) i populate routing table 100 with saddrs I want dropped, and: "ip ru a pref 100 lookup table 100" What I would expect to see is packets with a saddr in table 100 coming in eth0 will go out eth1, with replies beeing dropped, but I do not see the packets going out eth1 at all. Have tried searching and following the fib codepath, but have still not managed to understand what is really going on here. Is the saddr looked up in the routing table? Why dont I get icmp unreachable for unreachable routes? Is tcpdump tricking me here? I like the behavior, I just don't know if I can trust it. Kernel 4.8.1 Regards, -- Bj(/)rnar
bonding (IEEE 802.3ad) not working with qemu/virtio
As subject says, 802.3ad bonding is not working with virtio network model. The only errors I see is: No 802.3ad response from the link partner for any adapters in the bond. Dumping the network traffic shows that no LACP packets are sent from the host running with virtio driver, changing to for example e1000 solves this problem with no configuration changes. Is this a known problem? -- Bj(/)rnar
