Even though my name is on that bug report (I reopened it), I completely
forgot about that.
I don't even remember how I got there, though I do remember doing step
by step debugging and finding those flags. Somehow the wireshark capture
led me there but I don't remember the symptoms.
Simon reported
Hello Sergio,
thanks for your support, I found my mistake, I changed the IP address
from 192.168.0.2 to 172.168.0.2 because the 192.168.0.2 is already
taken in my network. When using 192.168.5.2 everything is working
fine. Hence I think I have to read something more about tap devices
and default
Hello again,
forget my last mail, I think I found something like a real reason for
the not working minimal example. After some debugging (starting with
the not working ARP resolution) I found that the netif flags are not
initialised in the mintapif_init in mintapif.c. After adding:
netif-flags =
Hi,
On Tue, Oct 07, 2014 at 03:37:39PM +0200, Matthias Dübon wrote:
Hello again,
forget my last mail, I think I found something like a real reason for
the not working minimal example. After some debugging (starting with
the not working ARP resolution) I found that the netif flags are not
OK, here I go...
The UN*X examples use a tun/tap device, and there is a specific
configuration parameter for different flavors of it. Check the Makefile
for this, did you ?
#To compile for linux: make ARCH=linux
#To compile for cygwin: make ARCH=cygwin
#To compile for openbsd: make ARCH=openbsd
Hello everyone,
I am quite new to lwip and I tested the lwip minimal example in the
lwip-contrib folder under a linux (Ubuntu) system. The example is
running, I see SNMP output messages but I am not able resp. I don't
understand how to use the echo server.
I turned on all debug messages and used
