Good question. They actually weren't on the Office ERX (I could swear I had set them up) but they don't seem to make a difference.
This is on the Office ERX:
david@Meadows-Router# traceroute 192.168.4.1
traceroute to 192.168.4.1 (192.168.4.1), 30 hops max, 38 byte packets
1 192.168.4.1 (192.168.4.1) 61.955 ms 58.123 ms 52.496 ms
[edit]
david@Meadows-Router# traceroute 192.168.10.1
traceroute to 192.168.10.1 (192.168.10.1), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * *^C
[edit]
david@Meadows-Router# show protocols static
interface-route 192.168.1.0/24 {
next-hop-interface vtun0 {
description "Parents Home"
}
}
interface-route 192.168.4.0/24 {
next-hop-interface vtun0 {
description "Dave Home"
}
}
interface-route 192.168.10.0/24 {
next-hop-interface vtun0 {
}
}I have also tried the route to 192.168.10.0/24 as a static route with a next-hop IP of 192.168.4.1, since vtun0 on this router has multiple clients. Same effect.
On the Tomato router, it actually makes it over the VPN correctly, but then my home ERX SFP just seems to drop the ball:
root@router:/tmp/home/root# traceroute 192.168.4.1 traceroute to 192.168.4.1 (192.168.4.1), 30 hops max, 38 byte packets 1 192.168.4.1 (192.168.4.1) 63.384 ms 61.708 ms 63.857 ms root@router:/tmp/home/root# traceroute 192.168.3.1 traceroute to 192.168.3.1 (192.168.3.1), 30 hops max, 38 byte packets 1 10.8.0.1 (10.8.0.1) 67.996 ms 62.292 ms 64.331 ms 2 * * * ^C
What could be the matter here? Thanks for the help.