Hey Fabian, Thanks for the enlightenment! :) I was looking at my wireless connection parameters instead of the ethernet. Now I use IP 169.254.232.150 with netmask 255.255.0.0 and it's working!
Best regards, Mário Ribeiro On 4 July 2014 08:14, Fabian Koch <fabian.k...@de.abb.com> wrote: > Hey Mario, > > > > this looks like your communication partner doesn’t have the right IP set > as target: > > > > ip_input: iphdr->dest 0xFFFFFEA9 netif->ip_addr 0x4301A8C0 (0xFFFEA9, > 0x1A8C0, 0xFF000000) > ip_input: packet not for us. > > the destination IP is: 0xFFFFFEA9, which is 169.254.255.255 (that is the > AutoIP range that e.g. windows assigns if it doesn’t get an IP from dhcp). > > And that is certainly “not a packet for us” since your netif has > 192.168.1.67 with a netmask of 255.255.255.0 > > > > Does that help? > > Otherwise, create a wireshark capture of the traffic. > > > > Kind regards, > > Fabian > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
