<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[configuration specifics for IPv6 global unicast address (GUA)]]></title><description><![CDATA[<p dir="auto">Hi!<br />
I posted a message a few weeks ago related to this topic.  There were many readers of the topic, but no responders.  Interesting....</p>
<p dir="auto">Within days I'm going to design a sensor data and status reporting regime for field deployed Omega2+ (O2+) devices.  Implementation would shortly follow.</p>
<p dir="auto">It seems every device I run in my house (office is at house as well) will come up with a IPv6 GUA address, with the exception of the O2+ devices.  What is the significance of this?  Every device (desktops, telephones, RPi's and others) come up globally routeable.  I can sit at the pub (not that I ever do that) and ssh into the Pi or one of the Linux servers using a IPv6 address with total disregard to the IPv4 NAT reality of most home and office environments.  The O2+ devices are not automatically generating IPv6 GUA addresses and are therefore cannot be routed to from the outside of a NAT environment.</p>
<p dir="auto">What config parameters need to be changed, and in which files, to "encourage" the O2+ devices to compute their IPv6 GUA addresses?</p>
<p dir="auto">thanks!<br />
Bill</p>
]]></description><link>http://community.onion.io/topic/3010/configuration-specifics-for-ipv6-global-unicast-address-gua</link><generator>RSS for Node</generator><lastBuildDate>Wed, 09 Sep 2026 00:52:30 GMT</lastBuildDate><atom:link href="http://community.onion.io/topic/3010.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 05 Jul 2018 23:43:30 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to configuration specifics for IPv6 global unicast address (GUA) on Thu, 05 Jul 2018 23:43:30 GMT]]></title><description><![CDATA[<p dir="auto">Hi!<br />
I posted a message a few weeks ago related to this topic.  There were many readers of the topic, but no responders.  Interesting....</p>
<p dir="auto">Within days I'm going to design a sensor data and status reporting regime for field deployed Omega2+ (O2+) devices.  Implementation would shortly follow.</p>
<p dir="auto">It seems every device I run in my house (office is at house as well) will come up with a IPv6 GUA address, with the exception of the O2+ devices.  What is the significance of this?  Every device (desktops, telephones, RPi's and others) come up globally routeable.  I can sit at the pub (not that I ever do that) and ssh into the Pi or one of the Linux servers using a IPv6 address with total disregard to the IPv4 NAT reality of most home and office environments.  The O2+ devices are not automatically generating IPv6 GUA addresses and are therefore cannot be routed to from the outside of a NAT environment.</p>
<p dir="auto">What config parameters need to be changed, and in which files, to "encourage" the O2+ devices to compute their IPv6 GUA addresses?</p>
<p dir="auto">thanks!<br />
Bill</p>
]]></description><link>http://community.onion.io/post/17188</link><guid isPermaLink="true">http://community.onion.io/post/17188</guid><dc:creator><![CDATA[William Scott]]></dc:creator><pubDate>Thu, 05 Jul 2018 23:43:30 GMT</pubDate></item></channel></rss>