Bas Wijnen wrote:
>Ah. So the resulting connection is just regular TCP, and the other side
>doesn't
>see any difference?
Well, that depends on how you configure it. The remote side sees tcp, or tls,
or
> In that case what you call altcp and what this
>hardware
>calls altcp is not the same
Manu Abraham wrote:
> [..]
> #error "lwip_sanity_check: WARNING: TCP_WND is larger than space
>provided by PBUF_POOL_SIZE * (PBUF_POOL_BUFSIZE - protocol headers).
>If you know what you are doing, define LWIP_DISABLE_TCP_SANITY_CHECKS
>to 1 to disable this error."
>
>So, What should be done ?
>
Am 6. Juli 2020 19:09:51 MESZ schrieb "Laurenz Altenmüller"
:
>Hi,
>
>I want to unit test some embedded firmware on native host arch by
>building it against the lwip unix port (latest master). Right now I
>want
>to add a fake IP and MAC to the ARP table with
>`etharp_add_static_entry()` so th
Am 4. April 2020 08:04:32 MESZ schrieb Jochen Strohbeck :
>Now, in 2.1.x, the first http request after host and controller power
>up is
>served but still delayed for ca. 5s and I don't know if this is a
>"feature"
>or bug of ARP.
>Please have a look at the commented 1st trace below.
Please send
Am 14. März 2020 18:47:01 MEZ schrieb Sachin Gole :
>In 2.1.2 version, There is no dev folder to run lwip_unittest
>
>
>~/Downloads/lwip-2.1.2$ ls
>build CMakeCache.txt cmake_install.cmake COPYING
> CPackSourceConfig.cmake FEATURES Makefile src UPGRADING
>CHANGELOG CMakeFiles CM
Am 25. Februar 2020 23:32:44 MEZ schrieb SimonW :
>I've searched all the documentation at
>http://www.nongnu.org/lwip/2_1_x/index.html. There is not mention of
>VLAN.
I said search the code. Sadly, we're not better than other open source software
when it comes to documentation:-)
>There are
>
Am 25. Februar 2020 22:38:31 MEZ schrieb SimonW :
>[..]
>Makes reference to including IPv4 config and not adding IPv6 addresses.
No, that might be misleading. The netifs get no addresses at all.
>I
>could do with fuller documentation - or better still an example.
This is a standard bridge. Bef
Am 24. Februar 2020 22:45:18 MEZ schrieb SimonW :
>Can anyone point me to an example using the bridge netif that is in
>lwip 2.1?
>Ideally with 1 leg using either an embedded MAC, or RNDIS over USB host
>- I
>have both legs working independently.
>
>Bonus question: I understand that the 2.1 brid
Am 24. Februar 2020 23:42:06 MEZ schrieb SimonW :
>Does anyone know if support for VLAN is planned for lwip?
Did you grep through the code searching for "vlan"? If not, I'd suggest to do
that.
Regards,
Simon
___
lwip-users mailing list
lwip-users@no
Am 22. Februar 2020 14:36:58 MEZ schrieb Trampas Stern :
>Do you have the example code for the STM32? Even just the mbedtls
>config
>and lwip config files would be good starting point.
Not right now, sorry. I haven't done that myself but a collegue of mine. Plus
the code in question is not cur
Am 20. Februar 2020 17:00:46 MEZ schrieb eitan via lwip-users
:
>Hello,
>
>I have a small device that sends data over TCP at a fast rate, this is
>a
>small and not very cable hardware.
>Now, LwIP is (as it should) maintains an acknowledge Q of ACKed packets
>so
>it could re-transmit if it has to
Am 20. Februar 2020 15:23:55 MEZ schrieb praveenkumar raavi
:
>Hi,
>
>Any update on my query...
I'm not sure I even understand what your actual problem is. But being stuck in
the timer function surely sounds like a threading problem...
Regards,
Simon
>
>Regards,
>PraveenKumar.
>
>On Thu, 13
Am 17. Februar 2020 13:21:46 MEZ schrieb Trampas Stern :
>How should I be using the 'lwip_cyclic_timers' ?
It's an array of timer callback functions and their required timer frequency.
You should use this to set up your timers, so you'll be calling all required
timers in the future.
Regards,
Please do not reply to digest mails. That breaks email threading for sure and
you risk people lose track of your story.
Regards,
Simon
Am 4. Februar 2020 18:29:20 MEZ schrieb Renato Barresi
:
>Hi Sylvain,
>
>I changed VJ_SUPPORT to 0 and still got the same behavior.
>
>I'm sending the PPP debu
Trampas Stern wrote:
>err_t httpd_post_receive_data(void *connection, struct pbuf *p)
>{
> pbuf_free(p);
>return ERR_OK;
>}
Ah, yes. And the problem still is that the example does not do that. I'll file
a bug...
Regards,
Simon
___
lwip-users mailing
Adam Baron wrote:
>I did search of POST related problems sorted by date. I will do so
>again.
>
>PBUF_POOL_SIZE is affecting number of POST I can do directly. That is,
>I
>can do as many posts as PBUF_POOL_SIZE is defined.
I think the user reporting this last time,did not free the pbuf passed to
Adam Baron wrote:
>OK, so my lwip gets stuck exactly after 16 POSTs.
>
>Maybe the POST is not freeing PCB, or other structures properly.
I rather think not freeing a pbuf could be the cause. I think we had that a
little while ago. Have you searched the list archive?
Regards,
Simon
___
Trampas Stern wrote:
>I was trying to use the httpd.c example which does some POST data
>parsing.
>From the httpd.h file it appears that httpd_post_begin() function is
>called
>with the first packet of data. However in reality it appears in use
>that
>it is usually called with just the POST head
Amena El Homsi wrote:
>Hello,
>
>After disconnecting from an AP I have to reset the PCBs pools. If I did
>not
>do that and I reconnect to the AP and If I tried to bind a socket to a
>port
>that I already used in the previous connection, binding fails (port in
>use).
That should not be required.
Liju John wrote:
>Still you can disable the streaming feature of the TCP and send like
>udp
>packets with TCP_NODELAY set socket option on the TCP level. This
>option is
>available on the socket. You can explore on it.
While this is correct, it's not a good suggestion in this thread: the remote
Urvi wrote:
>[..]
>
>But when I send 1 data packet of size=6 bytes (call tcp_write() and
>then
>tcp_output()) and next packet of size=45 bytes (call tcp_write() and
>then
>tcp_output()), then at server side it receives as a one single data
>packet
>of size=51 bytes; due to this my complete data p
Am 8. November 2019 16:15:06 MEZ schrieb vinu :
>Suppose the DHCP server decides to change the ip issued to my device
>after
>the lease time expiry, how can the application know that there is an ip
>change? Does the status callback be called in this case?
Yes.
Regards,
Simon
__
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
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 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: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 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 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 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 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
.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)
>>>>
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
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
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 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 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 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 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 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
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 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
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 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
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 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
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
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
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
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
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
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 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 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
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
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
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
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
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
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.
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,
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
___
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
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 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
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 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
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
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
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
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
_
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
___
"Александр секрет" 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
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
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
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
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
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
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://
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
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
_
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
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:
> 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
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
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
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
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
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
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
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:/
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
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
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
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
___
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
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
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
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
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___
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
1 - 100 of 122 matches
Mail list logo
