Hi again :-) Ok, I have now learned how to make that work. Learning this via ssh on a dial up connection has been a bit of a trial to say the least. I only managed to make 5 experiments in that time, because, of course, whenever I was wrong, I'd lock myself out... Simply, I have 3 dsl lines, and I wanted to multipath two of them. One 2MB xdsl line was all mine (ppp0) and, for trial purposes, the other came off of a switch from an existing NT router. For a week and a half I couldn't tell any diff between my set up and known setups from this list (thanks William et al.). In the end, I had to be *told* the ip of the NT router and then it worked no problem: I had been using the wrong ip :-( I will hard code it for now, because ultimately I will just be grepping for pppx's (when the NT router is replaced by this), but I really wonder how I could have discovered it. I saw these: Destination Gateway Genmask Flags Metric Ref Use Iface 148.235.145.81 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 66.181.42.64 0.0.0.0 255.255.255.224 U 0 0 0 eth1 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 172.36.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 148.235.145.81 0.0.0.0 UG 0 0 0 ppp0 148.235.145.81 dev ppp0 proto kernel scope link src 200.67.64.110 66.181.42.64/27 dev eth1 scope link 10.0.0.0/24 dev eth0 scope link 172.36.0.0/16 dev eth2 scope link 127.0.0.0/8 dev lo scope link default via 148.235.145.81 dev ppp0 The ip I needed was 66.181.42.68 to get out on eth1. How can I discover that without being told? I've typed ip xxx so often that I now understand the wisdom behind allowing all those short forms, I've read the cref.ps, lartc and stef's site etc., but I must be missing some ls command somewhere... -- Regards, Paul Evans