Ok there is still something wrong. In the http server demo I can see the "Welcome to our lwIP HTTP web server demo", however I need to refresh the page about 3 times. It fails to connect for the first times. As long as the connection is established the page is then refreshed fast, but if stay idle for a couple of (tens of) seconds, ie without refreshing/trying to connect, I get the same behaviour. I created a TCP server in a different port (1234) and instead of parsing HTTP data I print the incoming data in a terminal through serial port/uart. Same result.
I configured the server as follows: #define LWIP_IPADDR(p) IP4_ADDR(p, 169, 254, 232, 152) #define LWIP_GATEWAY(p) IP4_ADDR(p, 169, 254, 232, 148) #define LWIP_NETMASK(p) IP4_ADDR(p, 255, 255, 255, 0) and my ethernet configuration is (despite being in portuguese I think it's easy to understand): http://s4.postimg.org/w393586e5/ethernetconfig.png In wireshark I get the following: http://s4.postimg.org/6usupaqu5/wireshark.png Which presumably illustrates what I described above. Fails to connect a few times, then send some packets, and after some idle time if faisl to connect again. Do you have any idea of what's going wrong? Any help is greatly appreciated. Meanwhile, I definitely need to get a good TCP/IP reference book to understand a little bit better all these protocols. Mário Ribeiro On 4 July 2014 22:07, Mario Ribeiro <mario.ri...@gmail.com> wrote: > 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
