Hello David That is a clean and good explination on OUI but I have 16 million MAC addres I bought a range a month ago and the two devices have a different MAC addres because the router assignes two differen IP based on the mac addresses.
I placed the two divices running LWIP and a laptop in a seperate isolated network on a router and whe devices continue working for a few hours. On the corpate network the devices stopt working witin minutes. So might be the swich that was causing this problem or something else in our network. If i find out more on this topic i will post it on this mailing list. Thansk everyone for the feedback. Ruben ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ From: da...@abbey.co.nz To: rvdkr...@elmo-online.nl Date: 0:14:34, 05.02.2011 Subject: Re: [lwip-users] LWIP stops responding on Ping and HTTP calls from a browser ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ >>That sort of problem sounds suspiciously like your two devices are using the >>same Ethernet MAC address. This would confuse the switch, as switches operate >>by learning where a particular MAC address is connected. If there were two >>devices connected with the same MAC address, the switch would have to disable >>one or both of them, depending on how it is implemented. When you unplug one >>of your devices, the switch clears its records of all MAC addresses >>associated with that port, resolving the conflict. >> >>MAC addresses must be allocated uniquely to every device by the manufacturer >>of the device. The manufacturer must purchase a block of addresses from IEEE. >>They are available in blocks of either 16 million (an "Organizationally >>Unique Identifier", OUI for short) or 4096 (an "Individual Address Block", >>IAB for short). Within the OUI or IAB, you are responsible for ensuring that >>each device you manufacture has a unique address. If you expect to use at >>least three IABs over the lifetime of your company, then it is cheaper to buy >>an OUI. Large companies have multiple OUIs. >> >>----- Original Message ----- >>From: Ruben >>To: lwip-users@nongnu.org >>Sent: Saturday, April 30, 2011 1:53 AM >>Subject: Re: [lwip-users] LWIP stops responding on Ping and HTTP calls from a >>browser >> >> >>Hello >> >>I have to devices connected to switch which is connected to an other switch >>where my PC is connected to. >>If is disconnect one of my devices the problem that the stack stops >>responding is solved / the device keeps responding on ping / telnet / http. >> >>when i watch the lwip_stat stucture in my debugger I see some protocol error >>but that might be caused by the stack only dealing with two type of >>protocols: IP and ARP header type 0x800 and 0x806 the error was gererated on >>type 0x69. >> >>I am not sure why the two devices on the same switch cause this kind of >>behaviour. maybe the switch is nog very good or the Lwip stack had an >>unexpected influence in both devices. >> >>I'm going to think about it in the weekend and hopefully get an idea on how >>to test / analyse / solve this. >> >>Any suggestions ? >> >>Ruben >> >>~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ >>From: l...@elmo-online.nl >>To: rvdkr...@elmo-online.nl >>Date: 9:01:31, 04.29.2011 >>Subject: Re: [lwip-users] LWIP stops responding on Ping and HTTP calls from a >>browser >>~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ >> >> >> >> >>>>Hi Kieran >>>> >>>>I got the stat working unfortunately the debug function not yet. >>>>But in the port files i found how to decare the printf for the stats >>>>function. >>>> >>>>I have some errors on etharp >>>> >>>> ETHARP >>>>xmit: 7 >>>>recv: 1256 >>>>fw: 0 >>>>drop: 54 >>>>chkerr: 0 >>>>lenerr: 0 >>>>memerr: 0 >>>>rterr: 0 >>>>proterr: 54 >>>>opterr: 0 >>>>err: 0 >>>>cachehit: 1042 >>>> >>>>when refresh the web browser the proterr increases. >>>>this also happend on ping. >>>> >>>>any sugestions or remarks ? >>>> >>>>Ruben >>>> >>>>~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ >>>>From: kie...@recoil.org >>>>To: rvdkr...@elmo-online.nl >>>>Date: 14:32:15, 04.28.2011 >>>>Subject: Re: [lwip-users] LWIP stops responding on Ping and HTTP calls from >>>>a browser >>>>~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ >>>> >>>> >>>> >>>>>>On Thu, 2011-04-28 at 11:58 +0200, Ruben van der Kraan wrote: >>>>>> > I call "stats_display();" >>>>>> > >>>>>> > but is the define "#define LWIP_PLATFORM_DIAG(x) printf" wrong or not? >>>>>> > in the help I found >>>>>> > >>>>>> > Platform specific diagnostic output - >>>>>> > LWIP_PLATFORM_DIAG(x) - non-fatal, print a message. >>>>>> > LWIP_PLATFORM_ASSERT(x) - fatal, print message and abandon >>>>>> > execution. >>>>>> > Portability defines for printf formatters: >>>>>> > U16_F, S16_F, X16_F, U32_F, S32_F, X32_F, SZT_F >>>>>> > >>>>>> > I think I also have to define somthing like this >>>>>> > >>>>>> > #define U16_F unsigned short >>>>>> >>>>>> Look at one of the example ports in contrib/ports/ for details of what >>>>>> to do with these. >>>>>> >>>>>> Kieran >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
