URL:
<http://savannah.nongnu.org/patch/?5506>
Summary: api_lib.c: netbuf_copy_partial() use memcpy instead
of byte copy
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: goldsimon
Submitted on: Dienstag 31.10.2006 um
The fact that DHCP and a simple UDP connection work does not mean everything
works. I'm assuming either TCP does not yet work for you or the COPY flag
passed from the httpd to tcp_write is missing. Maybe you should try to
implementation a simple TCP connection first, but be sure to try to send a
This is spam which is normally filtered out by the system. Don't know why
this one made it through. I'll check the sender email...
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 21. Juni 2016 7:45:43 nachm. schrieb Patrick Klos :
Hi ,
Digital Power on the
Please read doc/rawapi.txt where this is documented.
Noam, I'm a bit confused. The PCB passed to the recv callback should be the
one passed to tcp_recved. To handle the listen callback, this is different...
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 27. Juni 2016
I think you might have missed reading the documentation: tcp_write enqueue
data, tcp_outout tries to send it. You always have to call both.
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 13. Juli 2016 2:35:59 nachm. schrieb Jakub Schmidtke :
Maybe your sys_now() or sy
Sylvain Rochet wrote:
The fact that it is your code and not your code doesn't change anything
about the fact that it is completely wrong.
Indeed. Not completely wrong maybe, but at least bad quality. However, it
changes everything about suspecting something about Mike driver's code quality:
original udp_test function - that checks for
errors and reports them (not the "borrowed" one!).
I'm going to try bigger or faster packets in a minute.
Many thanks,
Mike.
On 28/07/2016 16:27, goldsimon wrote:
Sylvain Rochet wrote:
The fact that it is your code and not your
Please use 2.0.0 (beta 2) when switching versions. 1.4.1 is four years old
and you'd risk having to change once again in some weeks...
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 7. August 2016 8:58:35 vorm. schrieb Norbert Kleber
:
Hi everyone,
first of all i'l
Amit Ashara wrote:
LLDP can use the same MAC address as being used by lwIP. It is not mandated
that they be different.
No, but if you have more than one port, it's typical to have one MAC per
port. This helps to tell which port of a switch a device is connected to,
for example (e.g. used in
Hi Amit,
of course you must make up for a licence before sharing anything.
Personally, I'm not sure I would contribute to anything not compatible to
the lwip licence though.
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 19. August 2016 4:28:55 nachm. schrieb Amit Ash
Calling tcp_output() sends the data, but that doesn't mean the buffer is
free afterwards: it stays allocated until the remote host acknowledges it.
At this point, lwip calls your 'sent' callback.
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 31. August 2016 12:22:08 na
On the contrary: Xilinx does it perfectly right. They use their hardware at
interrupt level but feed rx packets into lwip in the main loop.
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 28. September 2016 2:35:54 nachm. schrieb garibaldi pineda garcia
:
Xilinx appli
A RST is sent when lwip knows that one of the two sides has not read (or
packed) all data that has been sent. This is what standard socket stacks
would do also.
Simon
Gesendet mit AquaMail für Android
http://www.aqua-mail.com
Am 28. September 2016 7:32:05 nachm. schrieb Roger Cover :
Gree
From all information given so far, I fail to see how this would be an lwip
problem.
Did you test your SSL application on a different platform and it worked or what
makes you think of an lwip problem instead of an application problem?
Don't get me wrong, lwip can have bugs. I just don't see that
Please don't hijack a thread but ensure you create a new one for a new topic by
creating a new mail instead of hitting the reply button and changing the
subject.
Thanks,
Simon
Am 16. März 2017 17:15:01 MEZ schrieb Stephen Cowell
:
>We're having some problems with a customer... we have over a
Mohamed Hnezli wrote:
> what makes me confused
> is that there is no problem with firefox
Did you read my mail you replied to?
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
After looking at the changelog, I also guess it must be your test. What's
changed there is that slowtmr checked for == max retries and I've changed it to
>=. The old code had the assumption that nrtx was increased in the timer only,
but in SYN_SENT, it is increased asynchronously as well.
Simon
Am 3. April 2017 23:30:52 MESZ schrieb Sylvain Rochet:
>WTF. Did you even read what the netbuf_next() function actually does ?
I can only agree to Sylvain. Noam, I am thankful to everyone contributing here,
but this example is just so wrong! Please stop confusing people.
Sion
___
dworkdev wrote:
>A short interrogation : Does LWIP supports DSCP marking ?
Yes.
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
You might achieve the required connection limitation by having only 4 TCP PCBs
in the memo pool...
Simon
Am 4. Mai 2017 17:56:09 MESZ schrieb Joel Cunningham :
>
>Do you have TCP_LISTEN_BACKLOG enabled in your port?
>
>Also keep in mind, the backlog only limits connections that have not
>been a
Noam Weissman wrote:
>My question was simple ... does anyone have an idea why select
>
>does not return when a connection to the correct port is initiated.
Can't help you much there other than saying: try to check the socket's status:
is there an acceptable connection pending in the queue? Has
Noam Weissman:
>Were is the semaphore released ?
In "event_callback()", if I remember correctly.
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Hey Bill,
Great to hear 2.0.2 fixes this. I'm a bit lost thinking about a bug fix. We had
some since then I guess, and I would have to dig through the log myself.
However, the most obvious would be a zero window where the persist timer
doesn't start or somehow doesn't work correctly.
Are you ab
Mike Rosing wrote:
> After searching a while I see that the LwIP is waiting for LAST_ACK, but the
> server never sends it.
I would have expected lwip to time out this PCB eventually (although that can
need quite some time). How long did you wait?
Simon___
Looks correct. I guess mpu mode is not used too often. My suggestion would
probably be to get select_cb from a Memo pool...
Simon
Am 6. September 2017 16:12:47 MESZ schrieb David Lockyer
:
>Hi,
>
>I have a project that uses an STM32F MCU running FreeRTOS (cortex mpu
>port) & lwip, with the MP
Adrian Figueroa wrote:
>This fails:
>
> if((DmaTxDesc->Status & ETH_DMATXDESC_OWN) != (uint32_t)RESET)
> {
>errval = ERR_USE;
>goto error;
> }
>
>When DmaTxDesc->Status equals 818937856. What does this mean? Is the
>DMA used by something else?
I could mean your DM
Adrian Figueroa wrote::
>I have no idea why I have no packet loss with TCP_WND and TCP_SND_BUF
>set to 2xTCP_MSS. Instead, I get rare ZeroWindow errors from my PC.
Because you don't fill your DMA buffers in this case and as a result, you don't
drop tx segments.
Implementing a zero copy driver
kevin wrote:
>sys_thread_new("httpd", httpd_init, NULL,
httpd is a callback API application. Please make sure you understand lwips
thrading requirements.
In other words: RTFM ;-)
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://l
antonio wrote:
>I *moved* the declaration of *struct pbuf from pbuf.h to pbuf.c*.
That won't work as in many places the struct needs to be known. Including
sizeof() and other direct instantiations (not via pbuf_alloc). We started a
scheme for private header files to solve this.
Simon
___
Giuseppe Modugno wrote:
>I'd like to protect some or all web pages and show them only to
>authorized
>people. I understood there are two methods: basic and digest.
I guess both are outdated. Modern web pages use a custom input field which is
sent to the server via POST. You'll need TLS obviousl
Arun Jyothi wrote:
>Can I get an example or steps to do SNMP Communication.
Have a look at the win32 or Unix ports in contrib, they would both include snmp
support.
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mai
Noam Weissman wrote:
>Create an empty file named ajax.shtml or ajax.html and add it to your
>file list.
>
>Inside the file you only write one tag without anything else. For
>example
That's a nice idea. I also have task #14269 open to make ssi processing
independent of the file's extension (a m
Giuseppe Modugno wrote:
> It's a pity lwip doesn't feature those
>secure network layers.
Actually, it's not that far away. Have a look at the for master. It's not in
the releases, yet.
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https:/
Amena El Homsi wrote:
>> I tried to explain that before. Your ROM is not ROM. Data must be
>kept
>> unchanged until it is actually sent. How do you ensure this??
>>
>Our System will take care of this, Data will be kept unchanged until it
>is
>actually sent. Headers are copied from the Pbuf_RAM to
You're right in that it doesn't work. The browser has no way to know the body
size.
The downside of not sending conten length is that the server will have to close
the connection. Reopening it might take longer than just sending zero bytes to
create the correct content size...
Simon
Giuseppe Modugno wrote:
>Any suggestions on how to detect my public IP address?
Would ipify.org work?
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Arun Jyothi wrote:
>char data[100]={"snmpget -d -v2 -c public 10.1.1.196
>1.3.6.1.4.1.20246.2.3.1.1.1.2.5.3.1.0"};
> [..]
>/* Sending packet by UDP protocol */
>err = udp_sendto(udpecho_raw_pcb, pkt_buf,snmp device IP Address, 161);
Do you really expect that you can send a shell command to the
Noam Weissman wrote:
>I am working with STM32F7 with LwIP 2.02 + FreeRTOS 9
>
>D and I cache are enabled.
The drivers supplied by ST, although using DMA transfer, are still copying the
frame payload to/from pbuf payload using memcpy. If you haven't changed this
yourself, you have cache line al
Jochen Strohbeck wrote:
>I'm using lwip 1.4.1 and FreeRTOS on a SAME70 custom board with success
>if D-cache is disabled. If I enable the D-cache no more packets are
>received. If I place the RX descriptor into a non-cacheable region I
>get
>packets again
No surprises so far ;-)
> but the recei
Jan Menzel wrote:
> I'd suggest to align (position and size) all receive
>buffers to d-cache lines so that invalidation does not cause any side
>effects.
And it's exactly this that lwip does not fully support yet. It doesn't work for
the tx side at all and for the rx side, we only have the work
zulu4711 wrote:
>just an update! I think it was the PPP_INPROC_IRQ_SAFE not being set
>that
>was my problem.
Yes, it can't work without that set. I'll update the port's lwipopts. I wasn't
aware of the changed defaults here (at some time in the past, this has worked
when I last checked it, but
Jan Menzel wrote:
>For TX there is nothing really needed on the LWIP side. Draining the
>d-cache is always possible without side effects. Its just a question of
>efficiently if a packet content does not start at a cache line.
Unless that buffer would be in the same cache line as an rx buffer, ye
Sylvain Rochet wrote:
> [..]
>Looks like you are calling netif_* functions outside the lwIP core
>thread, guess what ? This is not thread safe. (Or maybe it is with core
>locking enabled).
No, it's not. Core locking is really for the you layer only.
Simon
_
goldsimon wrote:
> Core locking is really for the you layer only.
That should have been API layer!
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Barnabás Králik wrote:
>I also don't see any reliable way to recover the destination address in
>the udp receive callback.
Have you tried ip_current_dst_addr() (or something like that)?
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://
Amena El Homsi wrote:
>I am using lwip 2.0.3 Release version, I din't find MEMP_SEPARATE_POOLS
>Macro. How to know if the pools are placed in one array or separate
>arrays?
They are always separate since 2.0.0, as the previously used common array for
all pool had no real advantage.
Simon
Sturman_1 wrote:
>I use microcontroller and want to connect GSM(PPPos) modem to
>PC(Ethernet)
>via controller. I have read that LwIP can forward ipv4 packets. But in
>order
>to forward ipv4 packets first need a set connection.
That's not how ip forwarding works. Ip forwarding is one hop in a rou
twagner wrote:
>I have also a webserver running.
>I can see that the used pcb mem goes back if the Client (not the MCU)
>closes
>the connection (modbus),
>but if the server (the MCU) closes the connection the used pcbs doesn't
>go
>back (webserver).
>If i have only the mobus connection in use the
Chris Seto wrote:
>I have a custom board with an STM32F4, and a TLK110 running LwIP 2.0.3.
>The
>board works great when it gets, an address, and I can freely exchange
>data
>with a socket server.
>
>On board bootup, I set the IP to 0 and then use dhcp_start() to start
>DHCP.
>When the code sees t
If the error persists with the current version, please open a bug at Savannah
and upload everything required to reproduce.
Thanks,
Simon
Am 11. März 2018 03:59:09 MEZ schrieb JM :
>I'm trying to port lwIP 1.4.1 and httpserver_raw to a PIC32MZ. No RTOS.
>After a web client establishes a TCP con
"Александр секрет" wrote:
>Hello.
>Tell me how to manage KEEPALIVE with NETCONN API
>
>It seems to me that they forgot about it and did not make the necessary
>functions or macros in NETCONN API.
Exactly. For keepalive, the socket api directly uses the raw tcp api instead of
going through the
Sergio R. Caprile wrote:
>You should capture the traffic on your customer premises to make sure
>this is what's happening. I'm curious to know.
You could also implement handling the Expect header in your http server and see
if this speeds up the transfer.
Simon
___
Am 18. Mai 2018 17:03:21 MESZ schrieb Biafra :
>Hi everyone,
>
>I'm new to lwip.
>I've noticed that the dhcp_option_hostname() function (to set the
>hostname for DHCP session) isn't executed on dhcp_discover() function.
>
>Is it the correct behaviour?
Is it incorrect behaviour?
Simon
_
Unless you want to use VLANs, I guess pretty much everything has been said here
:-)
Simon
Am 14. Juni 2018 17:04:04 MESZ schrieb Kamil Khoury :
>Thank you both for your response.
>To be specific, all received messages have the same multicast address.
>the
>only difference between the two types
I must say I've never tried. I have only tested slaac an link local addresses
so far. At which point does it reject using your address?
Simon
Am 25. Juli 2018 21:32:03 MESZ schrieb josephjah :
>Thanks for responding. I've tried using netif_ip6_addr_set() per your
>suggestion but while it sets t
Am 31. Juli 2018 11:13:00 MESZ schrieb Mike Danby :
>Hello,
>
>Forgive my ignorance I am new to the TCP/IP stack scene. I am currently
>trying to get the LWIP stack up and running with FreeRTOS on a
>Microblaze based system. I have successfully started a TCP server and
>managed to connect a clie
Am 31. Juli 2018 14:34:14 MESZ schrieb "Sergio R. Caprile" :
>What you see is the Naggle algorithm.
I thought so, too, but if he is seeing 20 seconds delay, it's not Nagle but
some bug.
In fact, nagle should only hold off sending data if there is already unacked
data under way. If unsent and
This sounds even more like a driver issue.
Am 1. August 2018 10:45:26 MESZ schrieb Mike Danby :
>When the test program is run for the first 3-5 seconds the each send
>call will result is the string (approx. 15 bytes) being transmitted to
>the client in separate frames. After that (even though the
Am 2. August 2018 15:47:21 MESZ schrieb GuyH :
>Hi,
>
>I had my application running with freertos OS with lwip 1.4 and I just
>moved
>to SDK 18.1 with lwip 2.02
What is SDK 18.1? I guess you are talking about some vendor-modified version of
our stack...
> - I've noticed that one of the change
Am 4. August 2018 04:52:36 MESZ schrieb Richard Man :
>Hello pardon me for asking newbie question.
>
>With the requisite call
>
>mqtt_client_info.tls_config = altcp_tls_create_config_client(cert,
>sizeof(cert));
>
>
>Let's say I am using an embedded system with no file system support. I
>am
>com
Am 7. August 2018 09:16:51 MESZ schrieb Sadegh916 :
>Hi all
>I'm using LWIP and RAW API. I have a TCP echo server example. It works
>well.
>But I have a question. How can I know how many clients are connecting
>to my
>TCP socket?
You'll have to manage that list yourself. There is no API to iter
Andy Pont wrote:
>Do we know when 2.1 will be out of beta and formally released? I’m not
>
>sure I would want to build the product using a beta or current top of
>tree!
That's only a matter of some days hopefully. I'll do that as soon as I get back
to work.
Simon
___
Amena El Homsi wrote:
>The pbuf structure is 16 bytes. Is their a plan to add more elements to
>it
>in the next lwip versions or its size will not be changed?
Its size has long been 16 bytes and there are requirements to leave it like
that. However, there are other requirements to change this,
Nathan Hartman wrote:
>Under git tag STABLE-2_1_0_RC1 it appears that CHANGELOG entries for
>STABLE-2.0.2 and STABLE-2.0.3 have disappeared. Is this intentional or
>an
>error?
This is intentional as those 2 stable versions are bugfix branches and this not
direct parents of the master branch.
Ranran wrote:
>On Thu, Oct 4, 2018 at 9:28 PM goldsi...@gmx.de
>wrote:
>>
>> On 04.10.2018 17:14, Ranran wrote:
>> > Does lwip support using multiple ports (physical interface) ?
>>
>> Yes. Do you want a single IP address or each netif with its own IP?
>> For a single IP address, you need somet
vr roriz wrote:
>[..]
>Then, I added the send_now control option, letting tcp_output (with
>send_now = 0) to be called by lwip itself.
Ok, so the application *never* calls tcp_output() but you leave this completely
to the stack? That might work somehow, but will lead to totally unpredictive
p
vr roriz wrote:
>That's my point, I thought it would be totally unpredective. But after
>some certain amount of data is periodically queued, the RTT starts to
>go down again and the throughput is achieved. That is what I would
>like to understand.
I think tcp_output() is called every time an rx
Joe Hinkle wrote:
>I've enabled TCP debugging in lwip and it is showing sequence and
>acknowledgement numbers that do not match what is shown for the packet
>on
>wireshark.
Uncheck "Relative sequence numbers" in wireshark.
Simon
___
lwip-users maili
Hamme, Janis" wrote:
> Since each packet would be processed
>immediately I can't think of any situation where I would need to store
>more than one incoming and one outgoing packet at a time. Queueing
>shouldn't occur anywhere - or am I missing something?
If your netif driver doesn't queue, tx p
Am 31. Oktober 2018 16:26:27 MEZ schrieb Bob Jones <0xdeadbeef2...@gmail.com>:
>Hello,
>
>I'm using lwIP the stack with sockets in our project to create multiple
>HTTP connections to a non-lwIP server. I've noticed in Wireshark traces
>that on some occasions the server will send a [FIN, ACK], an
Am 5. November 2018 17:49:42 MEZ schrieb Amena El Homsi
:
>Thanks for your reply. So if I want to support it I have to add some
>changes to etharp.c file.
Yes.
> Is there a plan to support such feature?
No, but I'm not opposed to accepting patches adding hooks for such things (see
the other
Am 5. November 2018 19:15:51 MEZ schrieb Martin Kortmann
:
>Hi,
>
>I have to copy and modify the code of etharp.c since several years.
>My problem with etharp.c is: My Ssstem includes one microcontroller
>(with lwip running on it) and several FPGAs. All of them are
>communicating via TCP/UDP, s
Am 13. November 2018 06:10:32 MEZ schrieb Craig McQueen
:
>I wrote:
>>
>> I have tried using LWIP_HOOK_DHCP_APPEND_OPTIONS() and
>> LWIP_HOOK_DHCP_PARSE_OPTION() to request additional DHCP options
>> from the server, using DHCP option 55
>> (DHCP_OPTION_PARAMETER_REQUEST_LIST).
>>
>> At first
Niklas Gürtler" wrote:
> [..]
>When I restart my WiFi access point, the link is reconnected as
>desired,
>and lwIP performs a DHCP reboot and receives the same address as
>before.
>Unfortunately, in this case, the status callback is never called after
>a
>dhcp reboot. I think this is because i
Pablo Ledergerber wrote:
>
>hello,
>
>I'm working on a project for a new sensor with ethernet connectivity,
>modbus TCP for data and a kind of discovery function with udp packets
>for identificationdata. During the sensor is working well, there are
>sometime packet retransmission and after a c
stevestrong wrote:
>Hi again,
>The whole system seems very dependent on the debug outputs.
>I placed debug prints on different places and I always get different
>results, with partially strange behavior, including sending ACK for not
>received frames.
>
>So I think this is a dead end, because no
Am 8. Januar 2019 11:50:48 MEZ schrieb "Norberto R. de Goes Jr."
:
>How are you?
>
>After a long time spent in this issue with debugging in my network
>drive
>(socket raw), lwip configuration tuning (lwipopts.h), my client code,
>etc,
>etc; I noted (using simhost -d) that large packets caused
Am 8. Januar 2019 14:19:44 MEZ schrieb "Norberto R. de Goes Jr."
:
>Hi Simon!
>I think a note about "gro" is appropriate, for instance, in
>http://lwip.wikia.com/wiki/Tuning_TCP site.
The wiki is not really a thing I do edit or look at. Where in the lwip sources
or docs (in the hit sources o
saad saeed wrote:
>Hello,
>Currently, I am using IPv6-auto address configuration. But in lwIP
>2.1.0, there is also DHCPv6 stateless.
>My Question: Are these one and a same thing?
No, the first configures an address via router solicitaions, the latter adds
things that aren't available from rou
Am 17. Januar 2019 12:11:22 MEZ schrieb Jacob Kroon :
>Hi,
>
>I apologize beforehand if the text looks like garbage, I'm pasting in
>gmail..
>
>I'm looking at the core lock check in the unix port:
>
>void sys_check_core_locking(void)
>{
>/* Embedded systems should check we are NOT in an interrup
Am 22. Januar 2019 08:34:51 MEZ schrieb saad saeed :
>Dear All,
>
>I am using Socket API. How can I make lwip_accept(),lwip_recv() and
>lwip_send() non-blocking?
This is not an lwip specific question. It works the same as for all BSD
compatible sockets implementations. Your favourite search en
Am 23. Januar 2019 15:05:06 MEZ schrieb cbe...@vienco.de:
>Hi,
>
>I'm working with the lwIP 1.4.1 on a TI M4 platform with rawapi and I'm
>having trouble to understand the documentation correctly.
>In particular the callback for tcp_recv(). In the rawapi.txt is said
>
>"If there are no errors
Hi,
Am 28. Januar 2019 17:42:39 MEZ schrieb "Baur, Elias"
:
>Hello everyone,
>
>
>I am new to lwIP and did a lot of research the last couple of days. My
>goal ist to do real time networking between wire-connected
>Beagleboards. Therefore, we have been setting up a Xenomai Co-Kernel on
>the boards
Am 4. Februar 2019 06:53:47 MEZ schrieb Devanand Biradar :
>Hello Sylvain,
>I have corrected my input & output serial driver.
>Now I am getting the IP addr, GW, subnet from GSM using PPPOS over
>LWIP.
>Status - CONNECTED.
>
>Now I want to use PING (using ICMP).
>I want to ping google.com, how to
Am 4. Februar 2019 08:59:37 MEZ schrieb "Daniel Liquete García"
:
>Good moorning,
>
>Thanks four your repply.
>
>The same day that i saw your answer, i found the error (Compile Error),
>but i dont know the exactly sintaxis to fix it.
>
>
>#if defined ( __CC_ARM )
>ETH_DMADescTypeDef DMARxDscr
Am 7. Februar 2019 16:56:04 MEZ schrieb Dirk Ziegelmeier :
>Can you at least check/debug to be sure your MAC delivers the desired
>packet to lwIP? e.g. by dumping the first few bytes of all received
>packets
>and looking for your desired broadcast?
>
>If that is not the case, consult your MAC ma
Am 8. Februar 2019 00:27:58 MEZ schrieb Stephen Cowell
:
>I'm attempting to update the SAM4E example project
>THIRDPARTY_LWIP_BASIC_HTTP_EXAMPLE1 from 1.4.1 to 2.1.2. The dev
>system
>is Atmel Studio 7 using ARM/GNU Common toolchain. I have NO_SYS =
>1
>this is the bare-metal implementa
Am 8. Februar 2019 20:18:23 MEZ schrieb Stephen Cowell
:
>
>On 2/7/2019 11:39 PM, goldsimon wrote:
>> Am 8. Februar 2019 00:27:58 MEZ schrieb Stephen Cowell
>> :
>> ...
>
>> > Does everyone have to go through and edit
>> >the
>> >header fi
Am 28. Februar 2019 12:16:00 MEZ schrieb Ajay Bhargav
:
>I am yet to update the repo to latest lwIP source, but you can still
>use it.
>Usage information is given here:
>https://github.com/ajaybhargav/lwip_nat/blob/master/src/core/ipv4/ip4_nat.c
>
>I will better create a different howto file f
Am 2. April 2019 21:34:28 MESZ schrieb Mike Spenard :
>Submitted bug report on 404 missing issue.
>
>Could you provide some guidance on why the fsdata.c I generated with
>makefsfile.exe including headers is causing a "HTTP headers not
>included in file system" error?
I'd have to look at the sou
Please, this is an international community list, could you write in English so
that everyone can understand?
Thanks,
Simon
Am 11. April 2019 16:22:25 MESZ schrieb Sarp Daltaban :
>Doğru kanka, tek thread yeterli eğer ppp'yi beslemiyorsan.
>Endoks & t4e'de çalışıyorum.
>
>tirmalabenikasibeni , 1
.de wrote
>> Am 02.08.2019 um 20:29 schrieb
>
>> goldsimon@
>
>> :
>>> Am 02.08.2019 um 17:34 schrieb lauziepi:
>>>> Hello,
>>>>
>>>> thanks for the reply! Regarding question #2, would you (or someone
>else)
>>>>
Am 19. September 2019 17:20:29 MESZ schrieb "koszo.simon"
:
>Hi everybody,
>
>I have a question about altcp API: Does "altcp_active_pcbs" (or
>something
>similar) exist?
No, I don't think so. And what you're doing with the old tcp isn't actually
supported: it might work, but be prepared for si
Am 20. September 2019 07:22:39 MESZ schrieb "koszo.simon"
:
>Hi Simon,
>
>Thank you for your quick answer.
>
>Do you have any suggestion how I would be able to make my tcp server
>application to send out packages on every socket which is connected to
>the
>same tcp local port in a a supported ma
Am 25. September 2019 23:37:22 MESZ schrieb Dave Nadler :
>I'm using lwip 2.1.2 on FreeRTOS, on ST platform.
>lwip-2.1.2\system\OS\sys_arch.c sys_mbox_new(..) uses macro
That file is not part of our distribution, don't know where you got it from.
Regards,
Simon
__
Am 2. November 2019 00:34:41 MEZ schrieb Toshiyasu Morita :
>I was looking through the lwip and I found some obvious problems in the
>way
>invalidate_cpu_cache() is used.
That function does not exist in lwIP. You're probably using some vendor
version?
Regards,
Simon
_
Am 7. November 2019 08:59:54 MEZ schrieb vinu :
>Hi Simon,
>
>Is it safe to call dhcp_network_changed() from application thread ? I
>tried
>it ans seems to be working properly.
No, it's not safe. Don't do that.
> Also, should i call
>netif_set_down()
>and netif_set_addr() before dhcp_network_ch
Am 7. November 2019 11:06:07 MEZ schrieb vinu :
>
>We found that the issue was only occuring when the browser used is
>chrome
>and not evident while testing with Firefox browser or wget from a linux
>pc.
The problem might be the number of parallel connectionss then?
Regards,
Simon
Am 7. November 2019 08:54:25 MEZ schrieb mtimm :
>Simon,
>Thank you. It works better ;)
>One more question about purpose of using custom pools.
>LwIP uses few internal pools like PBUF_POOL_base, TCP_PCB_BASE,
>UDP_PCB_BASE.
>What can be the reason of using additional custom pools? Is it about
>p
Am 8. November 2019 14:38:38 MEZ schrieb Harrold Spier
:
>Hi Mario,
>
>As far as I know, the current stable version of lwIP does only support
>SNMPv1 traps. I'm now using the latest lwIP git checkout, which does
>have
>support for SNMP v2c traps.
>
>As far as I can see, there is no support for S
1 - 100 of 122 matches
Mail list logo
