From: kristrev
Date: Tue Nov 11 2008 - 05:34:36 EST


I have a question relate to the SO_BINDTODEVICE sockopt. On one of my
machines, it works perfectly and I am able to connect using specific
interfaces. On my laptop, however, one of the interfaces refuses to
transfer/receive any data.

The actual sockopt-call is successful and all the interfaces work (tested
them individually adjusting the metric in the routing table), leading me
to believe this is a routing table-related problem. My routing table
currently looks like this: dev eth1 proto kernel scope link src
metric 10 dev eth0 proto kernel scope link src dev wlan0 proto kernel scope link src
metric 100
default via dev eth0
default via dev eth1 metric 10
default via dev wlan0 metric 100

The one thing that puzzles me is that, with the exception of an additional
interface and different IP-addresses, this is exactly the same as on my
other machine (where it works). The only major difference, as far as I
can tell, is that they run different kernels ( vs, but
looking at the mailing lists I couldn't find any sign that the behavior of
SO_BINDTODEVICE has been altered.

Does anyone have any hints or suggestions?

Thanks in advance,

To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at