Hi Alex,
Yes, I have tried that as well.
Apologies, I should have mentioned that I tried both addresses. The far end (CPE WAN) and the local and it makes no difference. It still wants to send the route via the default to the wrong interface.
set routing-options rib inet6.0 static route 36a2:d840:60:ff46::1/128 next-hop 36a2:d840:0060:ff45::1 (ge-0/0/4 interface exit to CPE WAN)
user@ethernet-test-340# run show route 36a2:d840:60:ff46::1
inet6.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
::/0 *[Static/5] 5d 22:29:02
> to 36a2:d840:70::2 via ge-0/0/15.10
As an add on, I have now tested that the internal LAN Can ping the CPE WAN address. What makes this even more weird is the following:
CPE WAN ping to SRX340 ge-0/0/4 Interface - Success
CPE WAN to Facebook IPv6 address - Success
Laptop internal LAN ping to CPE WAN - Success
Laptop internal LAN ping to SRX340 CPE ge-0/0/4 interface - failure
How the hell can I ping the CPE WAN interface from the laptop but NOT the SRX340 ge-0/0/4 interface when the CPE WAN itself can? Sorry, I've answered this question myself, because there is no route back for the internal LAN....
When I look on the SRX340, the route shows correct for the CPE WAN out of interface ge-0/0/4. This proven by being able to ping facebook via the CPE WAN.... Very strange issue.... it's like the SRX just cannot see the CPE WAN interface and therefore installs no routes but it must do because of the CPE WAN ping'ing the internet....
Very frustrating.