On 2022 ven 29 jui - 14:08, Stuart Henderson wrote: > On 2022-07-28, Nicolas Goy <m...@kuon.ch> wrote: > > > > Ok, I think I found the issue. > > > > The cisco is useing the address fe80:b2b:11fe:161::2 but for some > > reason, openbsd doesn't link this. > > > > I cannot ping fe80:b2b:11fe:161::2%vport0 > > > > The system is adding fe80::%vport0/64 to the routing table. > > > > I am not sure, but I think that's the cause. > > > > I tried to add it to the routing table but it says "file exists". > > I suggest you send output from the commands which show the current > actual state of the system, i.e. netstat -rnfinet6, ifconfig -A, etc. > And instead of e.g. "I cannot ping X", show the actual command you > typed and what happened. > > For anyone who might have an idea what's up, it's a lot easier to read > these than it is to interpret information from english descriptions, > and might give some clues from things which you didn't describe. > Also it's much easier to compare this with how things look on a working > system. > > I don't think there's a dmesg in the information scattered in the > thread either, sometimes that is useful, which is why it's always > requested. > >
Well, yes, maybe I missed some info. But hopefully someone figured it out, my ISP is using a link local address that does not follow RFC 4129 which states that there must be 54 0 before the interface id. https://www.rfc-editor.org/rfc/rfc4291.html#section-2.5.6 I asked my ISP to changeg the link local address, but no answer yet, they are "working on it". -- Nicolas Goy Engineer & Developer https://www.kuon.ch https://www.goyman.com
