> > > > CLIENT: eth0 - ipc0 = 2001:660:5301:26:2c0:9fff:fe1a:caca > > > > eth1 - ipc1 = 2001:688:1fa1:2:204:75ff:fef8:93a4 > > > > SERVER: eth0 - ips0 = 2001:660:5301:26:210:5aff:febe:bb78 > > > > eth1 - ips1 = 2001:688:1fa1:2:204:75ff:fee8:52fd > > > > > > > You have to add an entry in your routing table saying that destination > > > 2001:688:1fa1:2:204:75ff:fee8:52fd is reachable through iface ipc0. > > > Otherwise the ROUTE target can't figure out whether the destination > > > is on-link or gateway'ed. > > > Try with something like this : > > > ip -f inet6 route add 2001:688:1fa1:2:204:75ff:fee8:52fd dev eth0 > > > Same remark applies for case 3). > > > > Hmm... thank you for your proposal, but is does not seem to be the > > solution for my problem. Should I add routing entries for ALL IPv6 > > addresses that I would like to access through ipc0 ??? I would like to > > have an access to the whole internet via both ipc0 and ipc1, but > > depending on the binding in the client software. So, when I bind my client > > to ipc0, I access all the internet via ipc0. When I bind my client to > > ipc1, I access all the internet via ipc1. > > My example above it was only my local testbed. > > Is it possible? > > Then add a default route that goes through 2001:688:1fa1:2:204:75ff:fee8:52fd : > ip -f inet6 route add 2001:688:1fa1:2:204:75ff:fee8:52fd dev eth0 > ip -f inet6 route add default via 2001:688:1fa1:2:204:75ff:fee8:52fd > So the ROUTE target knows that when sending through eth0, the next hop > is your server and that it is on the ipc0 link. Looks good. But I should use my gateway connected to the ipc0 (and also the second one, connected to ipc1). ips0 and ips1 are addresses of one normal host in my network, they are not gateway addresses. > So the complete ruleset should be in your case something like that : > > ip -f inet6 route add 2001:688:1fa1:2:204:75ff:fee8:52fd dev eth0 > ip -f inet6 route add 2001:660:5301:26:210:5aff:febe:bb78 dev eth1 > ip -f inet6 route add default via 2001:688:1fa1:2:204:75ff:fee8:52fd > ip -f inet6 route add default via 2001:660:5301:26:210:5aff:febe:bb78 Yeah, something like this, but with gateways addresses. > ip6tables -t mangle -A POSTROUTING --source > 2001:660:5301:26:2c0:9fff:fe1a:caca -j ROUTE --oif eth0 --continue > ip6tables -t mangle -A POSTROUTING --source > 2001:688:1fa1:2:204:75ff:fef8:93a4 -j ROUTE --oif eth1 --continue > > So, the ROUTE target is used for selecting between the two default > routes. I'll try it, thanks. Regards Pawel
