Re: [lwip-users] How to build a simple TCP [...]

[Antonio de Angelis]

Yes, you are right! If I put the two instances on the same machine, they run
with the same MAC address because I have only one Ethernet adapter... can
you explain what should I change in pktif.c exactly? I'm a beginner in lwip,
I understand that now the problem is that both instances have the same MAC
address but I don't know how to fix this issue... thank you and thanks to
Kieran and Bill, all of your mails help me very much understanding the
problem!!! :-)

Antonio de Angelis

-----Messaggio originale-----
Da: address@hidden
[mailto:address@hidden Per conto
di address@hidden
Inviato: mercoledì 9 luglio 2008 21.00
A: Mailing list for lwIP users
Oggetto: Re: [lwip-users] How to build a simple TCP [...]

After making the same mistake, I think you don't need a bridge: could it 
be that your 2 instances of lwIP are running with the same MAC address? 
This is not covered by the netif used with the win32 port: you have to 
change the MAC address for pktif.c at line 131 to prevent using the same 
MAC address.

Simon

Antonio de Angelis wrote:
> UPDATE: I've tried to put the server process on a different machine on 
> my home network, and it seems to work. But I want to make it work on the 
> same machine... I attach the wireshark dump of the communication... is 
> it working in the exact way?
>
> Antonio de Angelis
>
> address@hidden ha scritto:
>   
>> Antonio de Angelis wrote:
>>     
>>> [lengthy post...]
>>>   
>>>       
>> First of all, your mail is very difficult to read if you mix such long 
>> code passages with the actual questions you want to ask. Chances you 
>> get a response are higher if the problem is expalined shortly and code 
>> is put at the end of the mail.
>>
>> As to your problem: I don't really know why this doesn't work, I 
>> already did such a setup on my PC. Did you try your client application 
>> to connect to some other (non lwIP) server? Maybe even outside your 
>> PC? If you still have problems, you can try to use wireshark to 
>> monitor the ethernet packets sent on the network. Maybe that helps to 
>> find the problem.
>>
>> Simon
>>
>>
>> _______________________________________________
>> lwip-users mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/lwip-users
>>
>>     
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users



_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users