Details
- 
        Type:
 extRequest
            
         - 
        Status: Closed
 - 
            Priority:
 Major
                
             - 
            Resolution: Done
 - 
            Fix Version/s: 2021
 - 
            Component/s: FIWARE-TECH-HELP
 - 
            Labels:None
 
- 
                        HD-Chapter:Unknown
 - 
                        HD-Enabler:Unknown
 - 
                        HD-Node:Unknown
 
Description
Hello,
I read about Idas and Figway for IoT devices,
and in a blog post (Step 3.1) problems are mentioned that occur
behind a NAT when using Figway:
https://www.fiware.org/tag/figway/
Where as in a "native IDAS implementation" the NAT problem is not mentioned:
So would NAT be only a problem when using Figway when not using / having
a router to configure?
In case the NAT problem also is there in the above implementation, a
workaround might be a VPN or a "reversed SSH tunnel".
Albeit for VPN it might have to be a be an openVPN protocol as
Microsoft's protocol can be complicit to NAT rules i believe to have read.
I investigate how to realize an IoT implementation most independent from
infrastructure so it can be moved in different environments/networks
without new configuration.
R
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-incense-coaching@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-incense-coaching mailing list
Fiware-incense-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-incense-coaching
[Created via e-mail received from: Ridha Azaiz <ridha@aerialpower.com>]
Issue Links
- relates to
 - 
            
        
        HELC-1443
        FIWARE.Request.Coach.INCENSe.Question on NAT dependency with IoT
    
-         
     - Closed
 
 -         
 
Hi,
may you help this INCENSe SME?
Regards,
P.