Hi all
I try to develop a multiple servers with netconn and freeRTOS, the
application have a telnet server(port 23) and a gateway server(port 6020) in
two tasks. Both servers are not accept the connection when the both tasks is
running. but it can accept the connection and data when one
Should be 172 below... sorry.
Stephen Cowell
Project Manager/Engineer
Plasmability LLC
Office (512) 267-7087
Cell (512) 632-8593
www.plasmability.com
On 4/11/2016 3:42 PM, Stephen Cowell wrote:
Hey Simon...
There is also an NTP client running... using
SNTP. They have it set to 0.0.0.0, so
Hey Sergio...
Yes, I'm aware we are 'classless' now, but the
nomenclature was the easiest way to describe/
google it. I understand /23... much the same as
class-B.
I assume that they have a virtual gateway devoted
to each drop... not sure why, but the gateway is
ping-able.
We are shipping the
Stephen,
As far as I know, class B network should work OK. I'm running devices with
"strange" subnets, too, and they have no problem.
Can you post an example IP setting of the device, gateway and client trying
to ping the device?
Does the device have multiple netifs or only one?
Simon
I've got an embedded FTP product out in the
field built on lwIP 1.4.1... so far so good... but
now a customer has a problem getting one to
work (static IP) on a class-B (172.31.xxx.xxx)
subnet. Raw API, no OS... running FatFS
and FTPD on Atmel SAM4E16E.
I have not been able to obtain/set up a
You should first validate the port by running a known to work
application, pick one from the contrib tree. The port must not call
basic (non-netconn or non-socket) lwIP functions from different threads.
You must specify which API you are using, and it is quite helpful if you
post your piece
Hi Jan,
That's sounds great...
Thx,
Noam.
-Original Message-
From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On
Behalf Of Jan Menzel
Sent: Monday, April 11, 2016 11:53 AM
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] API question
Hi Noam!
I
Hi Noam!
I recently finished an application with almost the same setup: mbedTLS
(successor of PolarSSL with better licensing options) via socket API
(found some example for my MCU which I used as started) and SNTP client
from contrib tree which uses RAW API. Works very well since month.