Hi,
There is lots of talk about internet security and I was wondering what
we could do for LWIP to make it 'hardened'?
What could we add to LWIP that would reduce its vulnerability to attack?
A list of suggestions would be a good start:
1. Ability to turn off PING so its not so easy to find
Hi
I have a device with 2 Ethernet interfaces. Can I have two
"instances" of lwip to handle those? My problem is that both
are equal and should allow the same functionality. E.g. it
should be possible to have handlers that listen on the same
(UDP) port for each interface. But lwip can obviously on
Fabian Cenedese wrote:
> I have a device with 2 Ethernet interfaces. Can I have two
> "instances" of lwip to handle those?
Not unless you use a full-blown OS that can give the 2 instances seperated
address spaces. In other words, the answer is possibly "no, you can't".
> My problem is that both
At 11:50 28.02.2013 +0100, you wrote:
>Fabian Cenedese wrote:
>> I have a device with 2 Ethernet interfaces. Can I have two
>> "instances" of lwip to handle those?
>
>Not unless you use a full-blown OS that can give the 2 instances seperated
>address spaces. In other words, the answer is possibly
Thank you for the quick reply Stephane. Let me warn you that I'm not an LWIP
expert. I believe I am doing as you suggest. Here is some more information:
This thread gets into tcpip_apimsg() and posts to the mbox.
>>If you're talking about your netif driver giving the packets to the stack
