<?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[Omega2+ WiFi router conflict]]></title><description><![CDATA[<p dir="auto">I have this problem with setting up the Omega2+ for the first time. I connect it to my home WiFi network and it crashes my existing network. I think it creates a DHCP conflict but i'm not sure.</p>
]]></description><link>http://community.onion.io/topic/1483/omega2-wifi-router-conflict</link><generator>RSS for Node</generator><lastBuildDate>Sat, 10 Oct 2026 16:44:15 GMT</lastBuildDate><atom:link href="http://community.onion.io/topic/1483.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 27 Jan 2017 09:28:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Omega2+ WiFi router conflict on Fri, 27 Jan 2017 09:28:37 GMT]]></title><description><![CDATA[<p dir="auto">I have this problem with setting up the Omega2+ for the first time. I connect it to my home WiFi network and it crashes my existing network. I think it creates a DHCP conflict but i'm not sure.</p>
]]></description><link>http://community.onion.io/post/9673</link><guid isPermaLink="true">http://community.onion.io/post/9673</guid><dc:creator><![CDATA[Jackdaw]]></dc:creator><pubDate>Fri, 27 Jan 2017 09:28:37 GMT</pubDate></item><item><title><![CDATA[Reply to Omega2+ WiFi router conflict on Fri, 27 Jan 2017 10:43:17 GMT]]></title><description><![CDATA[<p dir="auto">I had the same sort of problem, it also caused wired ethernet to fail completely. For the record, main network was on 192.168.1.x and was using a different wifi channel than the Omegas initially booted up on. Dual frequency, 2.4 and 5GHz Wireless-N.</p>
<p dir="auto">Didn't find a resolution to <em><strong>directly</strong></em> use that network.</p>
<p dir="auto">I was able to connect to my phone's hotspot at first, and ran the needed firmware updates via that. Still seemed to crash main network if I tried to connect to it.</p>
<p dir="auto">Later on I dug out an old Wireless-G router and connected it downstream of main network (using a different SSID and with its own DHCP using 192.168.2.x). The Omega2+ and Omega2 are able to connect to the sub-network without causing further problems.</p>
]]></description><link>http://community.onion.io/post/9677</link><guid isPermaLink="true">http://community.onion.io/post/9677</guid><dc:creator><![CDATA[Keij H]]></dc:creator><pubDate>Fri, 27 Jan 2017 10:43:17 GMT</pubDate></item><item><title><![CDATA[Reply to Omega2+ WiFi router conflict on Fri, 27 Jan 2017 10:47:30 GMT]]></title><description><![CDATA[<p dir="auto">Mh, sounds like the same problem. My normal ethernet connections were stable though. The documentation: <a href="https://docs.onion.io/omega2-docs/fix-ip-addr-collisions.html" rel="nofollow">https://docs.onion.io/omega2-docs/fix-ip-addr-collisions.html</a> says that i need a different subnet for my home network. The omega has 192.168.3.x and i have 192.168.1.x, so thats not the problem. I will try to setup the Omega with mobile internet and disable the hotspot when it's done. Thanks for your reply!</p>
]]></description><link>http://community.onion.io/post/9678</link><guid isPermaLink="true">http://community.onion.io/post/9678</guid><dc:creator><![CDATA[Jackdaw]]></dc:creator><pubDate>Fri, 27 Jan 2017 10:47:30 GMT</pubDate></item></channel></rss>