On Fri, Dec 9, 2022 at 5:09 PM John Lemonovich
wrote:
> Hello Denys,
>
> I am working on an embedded Linux project using an intel Arria 10 FPGA and
> have been using IPv4 for a long time, and now need IPv6. I found your email
> online searching for help. I have many things working with IPv6, b
From: Denys Vlasenko
> Sent: 13 December 2022 15:22
>
> On Fri, Dec 9, 2022 at 5:09 PM John Lemonovich
> wrote:
> > Hello Denys,
> >
> > I am working on an embedded Linux project using an intel Arria 10 FPGA and
> > have been using IPv4 for
> a long time, and now need IPv6. I found your email o
From: John Lemonovich
> Sent: 13 December 2022 15:59
>
> Thanks for the replies. Yes David, it's also my understanding per the spec,
> that the client's link-
> local address must be included for the solicit message. The reply from the
> server is unicast. What
> do you mean by the proper IPv
On Tue, Dec 13, 2022 at 4:58 PM John Lemonovich
wrote:
>
> Thanks for the replies. Yes David, it's also my understanding per the spec,
> that the client's link-local address must be included for the solicit message.
Where does it say that in https://www.rfc-editor.org/rfc/rfc3315 ?
> The repl
On 14/12/2022 00:47, Denys Vlasenko wrote:
On Tue, Dec 13, 2022 at 4:58 PM John Lemonovich
wrote:
Thanks for the replies. Yes David, it's also my understanding per the spec,
that the client's link-local address must be included for the solicit message.
Where does it say that in https://www
From: John Lemonovich
> Sent: 13 December 2022 20:35
>
> How are you getting a solicit message through with :: as the source
> address, which I've found no
> server likes as I've tested 3 of them? Or is mine not using the link local
> address because I'm not
> doing anything with the default.
On Wed, Dec 14, 2022 at 8:55 AM Nicolas Cavallari
wrote:
>
> On 14/12/2022 00:47, Denys Vlasenko wrote:
> > On Tue, Dec 13, 2022 at 4:58 PM John Lemonovich
> > wrote:
> >>
> >> Thanks for the replies. Yes David, it's also my understanding per the
> >> spec, that the client's link-local address
On Wed, Dec 14, 2022 at 10:52 AM David Laight wrote:
>
> From: John Lemonovich
> > Sent: 13 December 2022 20:35
> >
> > How are you getting a solicit message through with :: as the source
> > address, which I've found no
> > server likes as I've tested 3 of them? Or is mine not using the link
From: Denys Vlasenko
> Sent: 14 December 2022 10:04
>
> On Wed, Dec 14, 2022 at 10:52 AM David Laight wrote:
...
> If it's the code from the above, then no, kernel will not fill in
> any IPv6 source addresses, as it does not even know it's
> an IPv6/UDP packet - we use raw sockets here,
> and we
On Wed, Dec 14, 2022 at 8:59 PM John Lemonovich
wrote:
> Thank you all for the replies so far. I am admittedly an FPGA
> designer/hardware guy, and an embedded software/networking person only enough
> to be able to get the hardware working 😊
>
>
> Here is a the wireshark (via tcpdump) of the so
From: Denys Vlasenko
> Sent: 14 December 2022 21:17
...
> For comparison, this is how DHCPv4 looks on the wire:
>
> 28:df:eb:11:48:92 > Broadcast, ethertype IPv4 (0x0800), length 342:
> (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length
> 328)
> 0.0.0.0.bootpc > 255.255.255
On Wed, Dec 14, 2022 at 11:23 PM David Laight wrote:
> From: Denys Vlasenko
> > Sent: 14 December 2022 21:17
> A Linux system that runs the dhcp client never reports any
> received ethernet packets as 'discarded by software' because
> they all get passed to dhcp!
> (At least one time I looked anyw
12 matches
Mail list logo
