Re: IPv6 static gateway IP problem

Thomas Kupper <[email protected]>
Newsgroups gmane.os.openbsd.misc
Message-ID <[email protected]>
Filip Lax wrote on 07.06.2026 00:40:
> Thank you so much Thomas, some progress, it works!
> 
> Sorry I bother to a few more question:
> 
> Testing a bit I sudden see "neighbor sol" message come from ::2 instead of ::1, and traffic no longer work. They use two gateway? I add both?

If you write ::2, are you referring to 2a03:118e:202::2 or 
2a03:118e:202:55::2?

Neighbour solicitations are used by nodes to find other nodes, not routers:

https://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol#Functions

> 
> And How I can use specific octets for my address? I test to use ex. "::123" making my address "2a03:118e:202:55::123" instead of "2a03:118e:202:55::" but then it doesn't work at all.

Are you sure the complete 2a03:118e:202::/64 prefix is routed to your 
server? Or do you only get one IPv6 address out of /64 prefix?

If the /64 prefix is indeed routed to your server then you can add 
another IPv6 to your interface and that will work.

ifconfig vio0 inet6 ....::123 alias

https://man.openbsd.org/ifconfig#alias

Btw - slaacd: you can stop & disable slaacd if you get a link local 
default route which doesn't work. RAs is a normal way to get a default 
route but providers may handle it differently.

> 
> ________________________________________
> From: Thomas Kupper <[email protected]>
> Subject: Re: IPv6 static gateway IP problem
> 
>> You have to add the gateway first, an example can be found in the
>> route(8) manpage: https://man.openbsd.org/route#EXAMPLES :
>>
>> "Add a static inet6(4) route to a host which is on the vio0 interface
>> that is outside your prefix, and use that host as a default gateway, as
>> used by some hosting providers:
>>
>> # route add -inet6 2001:db8:efef::1 -cloning -link -iface vio0
>> # route add -inet6 default 2001:db8:efef::1"
>>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.