Hey all,
I still have the Problem that I can't determine a Broadcast on higher
levels (netconn/netbuf), which I need.
I saw the SOF_BROADCAST option added in 1.3.1, but that won't help me
unless I'm willing to rewrite a lot of our code (which I'm not).
The other problem is that we treat LwIP as
Err.. sorry the subject on this is completely wrong... but anyways___
lwip-users mailing list
lwip-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lwip-users
Thanks,
it did work :) I was wondering about the MAC address, is there a similar set
of function we could use? Know if it's possible to change it on run time?
Thanks!
Alex
>> Date: Sat, 25 Jul 2009 16:35:38 +0400
>> From: Mike Kleshov
>> Subject: Re: [lwip-users] Restarting lwip/ethernet
I'm trying to understand all these options in opt.h/lwipopt.h so I can assign
them intelligently instead of guessing and wondering why communication fails.
So, this is what I think is correct; please correct me if I'm wrong:
In the case of all PBUFs being the same size as defined by PBUF_POOL_B
In 1.3.1, we added the function ip_current_header(), which should give
you everything you need (unless I understood you wrong).
Simon
Fabian Koch wrote:
Hey all,
I still have the Problem that I can't determine a Broadcast on higher
levels (netconn/netbuf), which I need.
I saw the SOF_BROAD
JM schrieb:
I'm trying to understand all these options in opt.h/lwipopt.h so I can
assign them intelligently instead of guessing and wondering why
communication fails. So, this is what I think is correct; please
correct me if I'm wrong:
In the case of all PBUFs being the same size as defined
Technically, the MAC is only stored in netif->hwaddr and only used from
the ARP, DHCP and AutoIP modules (aside from maybe your netif driver and
SNMP). So you might get what you want by stopping both DHCP and AutoIP
and then just changing netif->hwaddr.
I did not test this though! Also, care m
If you say PBUF pool is only for incoming packet, then lwip SNMP driver is in
Fault.
SNMP uses pbuf to send trap and response:
err_t
snmp_send_response(struct snmp_msg_pstat *m_stat)
{
...
/* try allocating pbuf(s) for complete response */
p = pbuf_alloc(PBUF_TRANSPORT, tot_len, PBUF_POOL);
.
> If you say PBUF pool is only for incoming packet, then lwip SNMP driver is
> in Fault.
I know, there's some 'room for improvement' in the snmp code... In any case
it's a bad example and the pbuf pool really should only be used for incoming
packets right now.
The reason is that *if* outgoing
