On 2022 sam 06 aoû - 09:51, Zack Newman wrote:
> Correction. Apparently even though it is not explicitly stated,
> Section 2.4 merely allocates fe80::/10 for link-local addresses while
> Section 2.5.6 defines what range, fe80::/64, from that allocation is
> currently valid, so it is not a contradic
On 2022 ven 29 jui - 14:08, Stuart Henderson wrote:
> On 2022-07-28, Nicolas Goy 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
> >
>
On 2022-07-28, Nicolas Goy 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 n
On 2022 jeu 28 jui - 12:20, Kevin Wallace wrote:
> On 2022-07-28 11:32 AM, Nicolas Goy wrote:
> > I found something weird that might be a bug.
>
> > ping6 fe80:b2b:11fe:161::2%vport0
>
> The KAME IPv6 code uses the second word of link-local addresses for
> internal bookkeeping, and clears it befo
I found something weird that might be a bug.
If I do
doas ifconfig vport0 inet6 fe80::2/10
Then
ping6 fe80:b2b:11fe:161::2%vport0
On the tcpdump output, I see a different address
20:31:15.816576 fe80::fce1:baff:fed1:b34 > ff02::1:ff00:2: icmp6: neighbor sol:
who has fe80:0:11fe:161::2
-
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
I added this as my first line in pf.conf
pass quick log on vport0 proto icmp6
When I do tcpdump -i vport0 I do see the packets
19:21:09.846069 fe80:b2b:11fe:161::2 > ff02::1:ff01:1: icmp6: neighbor sol: who
has [class 0xe0]
But there is nothing on tcpdump -i pflog0
It seems those pack
As additional info, here are my sysctl
net.inet6.ip6.forwarding=1
net.inet6.ip6.redirect=1
net.inet6.ip6.hlim=64
net.inet6.ip6.mrtproto=0
net.inet6.ip6.maxfragpackets=200
net.inet6.ip6.log_interval=5
net.inet6.ip6.hdrnestlimit=10
net.inet6.ip6.dad_count=1
net.inet6.ip6.auto_flowlabel=1
net.inet6
Ok, actually the ISP router is also trying the multicast after failing
the unicast:
Here are two packets, the first one works, the router responds (openbsd
box), but the second one is ignored.
first one (works is responded to):
[+] Frame 12012: 86 bytes on wire (688 bits), 86 bytes captured (688
On 2022 jeu 28 jui - 16:14, Nicolas Goy wrote:
> On 2022 jeu 28 jui - 15:52, Nicolas Goy wrote:
> > On 2022 jeu 28 jui - 13:18, Nicolas Goy wrote:
> > >
> > > - I can ping internet from my router, but it cuts every 10 seconds or
> > > so. If I inspect the traffic, I see that the ISP router is se
On 2022 jeu 28 jui - 15:52, Nicolas Goy wrote:
> On 2022 jeu 28 jui - 13:18, Nicolas Goy wrote:
> >
> > - I can ping internet from my router, but it cuts every 10 seconds or
> > so. If I inspect the traffic, I see that the ISP router is sending
> > neighbor discovery with my router address, an
On 2022 jeu 28 jui - 13:18, Nicolas Goy wrote:
>
> - I can ping internet from my router, but it cuts every 10 seconds or
> so. If I inspect the traffic, I see that the ISP router is sending
> neighbor discovery with my router address, and that my router does not
> respond.
>
This seems to
Hello,
My ISP gave me a /56 and told me it was statically routed (no
DHCPv6-PD).
Let's say this prefix 2a02:aa08::YY00::/56 is now x00::/56
What I want to do, is to split this prefix into /64 and use the /64 for
my vlans.
So what I did is on my interfaces I have the following ips:
wan x00:
13 matches
Mail list logo
