Hi,
I had a problem with the Sierra Wireless modem where transport on port
80 worked OK for http GET but for some reason POST would fail. I spent a
long time looking at the problem but the Sierra Wireless technical
support was about as useful as a chocolate fire guard. So I ran away
from the problem by moving the web-server to any other port than 80
where it works OK.
The instrument has a multi-cast debugging socket and I have a simple PC
application which provides a command line console so I can resolve the
instrument's IP address. However I feel that this is too complex for the
user's. The only comment I would make about lwIP and IGMP was that
enabling the protocol was simple but I missed setting the
NETIF_FLAG_IGMP flag in the network interface!
It looks like Windows is using UPnP to discover the DSL router. However
UPnP looks to be quite a big protocol. Does anyone else use this for
device discovery?
Thank you for your reply - it was very helpful!
Adam.
On 16/06/2015 09:55, Noam Weissman wrote:
> Hi,
>
> First of all they do not need to type port number as default is 80 for
> HTTP, unless you use
> a private port at your WEB server.
>
> As for discovery it depends what you want to achieve. If it is only and
> always local network
> you can run a simple UDP server that listens on a specific port for a
> special packet
> (you need to define that).
>
> Once you defined the protocol and have the server part running at your
> embedded side,
> you should run some application (PC app etc...) that sends a discovery
> request. This discovery
> message is the define packet sent via broadcast to your embedded. The
> embedded side will
> receive this packet and response to the client with any data you may
> need.
>
> If the device is behind a router or on a company network broadcast is
> not sufficient as broadcast
> Will work only on the subnet. In that case you will need to send a
> multicast message.
>
> If you multicast a message you will have to enable the IGMP module in
> your lwipopts.h, add
> The IGMP module and in your UDP listening server you will have to join
> the multicast group.
>
> Some discovery protocols are bonjour defined by Apple, SDDP defined by
> Control4 and others.
>
> Read some info on the above and if you need more information ask and
> I'll try to answer.
>
>
> BR,
> Noam.
>
>
> -----Original Message-----
> From:address@hidden
> [mailto:address@hidden On Behalf Of Adam
> Fullerton
> Sent: Tuesday, June 16, 2015 11:38 AM
> To:address@hidden
> Subject: [lwip-users] Networking device discovery protocols
>
> Hi,
>
> I'm using lwIP V1.4.1 in a low power remote monitoring project. Off site
> connection is made via a Sierra wireless AirLink GX400 modem. For on
> site maintenance connection is made with direct connection to
> instrument. In this scenario there is a DHCP server which gives the
> clients IP addresses. I would prefer it if they did not have to type in
> the V4 IP address and port number into the web browser. If I use the
> windows explorer to look at my computer network I can see the DSL modem
> and double clicking the icon opens a web browser on the management site.
> Can any one tell me what protocols I need to implement to achieve this
> and are there any samples of this for lwIP?
>
> Thank you for your help,
>
> Adam.
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
>
https://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
>
> ************************************************************************
> ************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals &
> computer viruses.
> ************************************************************************
> ************
>
>
>
>
>
>
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
> ************************************************************************************
>
>
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
>
https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users