tech-net archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: ipv6 gateway on different subnet
Thank you both for your input.
> should be this
>
> route add -inet6 -interface 2602:fed2:7116:d82c::1 2602:fed2:7116::1
I have tried that and it fails.
#route add -inet6 -interface 2602:fed2:7116:d82c::1 2602:fed2:7116::1
route: writing to routing socket: Network is unreachable
add host 2602:fed2:7116:d82c::1: gateway 2602:fed2:7116::1: Network is
unreachable
Reversing the addresses works.. the command does at least. The Internet
does not.
#route add -inet6 -interface 2602:fed2:7116::1 2602:fed2:7116:d82c::1
#route add -inet6 default 2602:fed2:7116::1
> inet6 2602:fed2:7116:d82c::1/64
> !route add -inet6 -net 2602:fed2:7116::1/128 -connected -link -iface $int
>
> Seems to work absolutely fine.
>
> BTW, you appear to be in the same datacentre as my VPS, but different
> provider - I have a VPS with linveo.com there (and I have actually
> sent them a NetBSD image that automatically sets up the network
> configuration).
That's a fun coincidence.
I noticed 'alias' was missing from the end of the inet6 address, and was
surprised it worked. I thought it was required per the docs I read.
https://www.netbsd.org/docs/network/ipv6/
I tried with and without, but still had ping issues after several
minutes.
I can't believe I never thought to change the prefix on the gateway to a
higher number. I even had a clue when the vps provided debian image
showed the gateway as a /128 with netstat (netstat is now removed,
but was on an older version of debian).
I also saw that '-cloning' had been deprecated in the route man page,
and to use '-connected', but didn't translate that to my testing.
Here's the current settings. I tried different variations last night,
but nothing worked perfectly.
/etc/rc.conf
defaultroute6="2602:fed2:7116::1"
ifconfig_vioif0="
inet 23.173.152.249 netmask 255.255.255.0
inet6 2602:fed2:7116:d82c::1 prefixlen 64 alias
inet6 2602:fed2:7116:d82c::2 prefixlen 64 alias
!route add -inet6 -net 2602:fed2:7116::1/128 -connected -link -iface vioif0
"
After a few minutes both connections still fail, but now I can ping
google.com to get ::1 working. I used to have to ping the gateway
It is not pingable from outside when it stalls. I have to ping
the gateway to get ::2 working.
There's a long delay as well on the first ping.
ping6 -S 2602:fed2:7116:d82c::1 google.com
PING6(56=40+8+8 bytes) 2602:fed2:7116:d82c::1 --> 2607:f8b0:4023:1002::8a
16 bytes from 2607:f8b0:4023:1002::8a, icmp_seq=0 hlim=112 time=5078.508 ms
netstat -rn
Internet6:
Destination Gateway
Flags Refs Use Mtu Interface
::/104 ::1
UGRS - - 33624 lo0
::/96 ::1
UGRS - - 33624 lo0
default 2602:fed2:7116::1
UGS - - - vioif0
::1 lo0
UHl - - 33624 lo0
::127.0.0.0/104 ::1
UGRS - - 33624 lo0
::224.0.0.0/100 ::1
UGRS - - 33624 lo0
::255.0.0.0/104 ::1
UGRS - - 33624 lo0
::ffff:0.0.0.0/96 ::1
UGRS - - 33624 lo0
2001:db8::/32 ::1
UGRS - - 33624 lo0
2002::/24 ::1
UGRS - - 33624 lo0
2002:7f00::/24 ::1
UGRS - - 33624 lo0
2002:e000::/20 ::1
UGRS - - 33624 lo0
2002:ff00::/24 ::1
UGRS - - 33624 lo0
2602:fed2:7116::1/128 link#1
UCS - - - vioif0
2602:fed2:7116:d82c::/64 link#1
UC - - - vioif0
2602:fed2:7116:d82c::1 link#1
UHl - - - lo0
2602:fed2:7116:d82c::2 link#1
UHl - - - lo0
fe80::/10 ::1
UGRS - - 33624 lo0
fe80::%vioif0/64 link#1
UC - - - vioif0
fe80::216:3eff:fed7:cf50 link#1
UHl - - - lo0
fe80::%lo0/64 fe80::1
U - - - lo0
fe80::1 lo0
UHl - - - lo0
ff01:1::/32 link#1
UC - - - vioif0
ff01:2::/32 ::1
UC - - 33624 lo0
ff02::%vioif0/32 link#1
UC - - - vioif0
ff02::%lo0/32 ::1
UC - - 33624 lo0
2602:fed2:7116::1 d8:67:d9:58:3d:1b
UHL - - - vioif0
--
Thanks
Peter
Home |
Main Index |
Thread Index |
Old Index