<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Routing problem USG 50&#x27; in forum &#x27;ZyXEL&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Routing-problem-USG-50-27868578</link>
<description></description>
<language>en</language>
<pubDate>Sat, 25 May 2013 21:18:31 EDT</pubDate>
<lastBuildDate>Sat, 25 May 2013 21:18:31 EDT</lastBuildDate>

<item>
<title>Re: Routing problem USG 50</title>
<link>http://www.dslreports.com/forum/Re-Routing-problem-USG-50-27960712</link>
<description><![CDATA[Aleksandar posted : Or try IP passthrough on ISP router that should change just one port role to act as a bridge and then you will have public IP on WAN port of the zyxel]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Routing-problem-USG-50-27960712</guid>
<pubDate>Wed, 30 Jan 2013 07:26:08 EDT</pubDate>
</item>

<item>
<title>Re: Routing problem USG 50</title>
<link>http://www.dslreports.com/forum/Re-Routing-problem-USG-50-27869290</link>
<description><![CDATA[Brano posted : There are several options you can do<br>- open WAN-to-LAN firewall with appropriate routing rules<br>- connect USG and ISP router using LAN ports only<br>- add LAN-to-LAN cable between USG and ISP router and keeping the WAN cable<br>...all depends what your desired end setup is<br><br>But frankly, I'd try to get public IP on USG WAN port and using the ISP router in bridging mode. That will get you away from double NAT troubles.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Routing-problem-USG-50-27869290</guid>
<pubDate>Mon, 31 Dec 2012 14:43:51 EDT</pubDate>
</item>

<item>
<title>Re: Routing problem USG 50</title>
<link>http://www.dslreports.com/forum/Re-Routing-problem-USG-50-27869062</link>
<description><![CDATA[Kirby Smith posted : Unless your firewall is opened to pass pings to downstream components, the USG will happily drop them into the bit dust bin.<br><br>Reading significant sections of the USG User Manual is necessary to gain a good perspective on how it works and what can be done to configure it to one's goals.<br><br>kirby]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Routing-problem-USG-50-27869062</guid>
<pubDate>Mon, 31 Dec 2012 13:32:57 EDT</pubDate>
</item>

<item>
<title>Routing problem USG 50</title>
<link>http://www.dslreports.com/forum/Routing-problem-USG-50-27868578</link>
<description><![CDATA[dras posted : Hello, I `m new here, Could someone please help me out.<br>I Have attached one network sketch with this email.<br><br>Using a Zywall USG50 connected to a ISP Router via the WAN1 port.<br>KPN Router uses 192.168.2.x and is DHCP. I`m not able to change anything in this Router due of the ISP policy.<br><br>My Issiue:<br>I`m able to see subnet 192.168.2.x from subnet 192.168.1.x <br>But if i try it in the opposite way I am only able to ping to 192.168.2.252. Not any further.<br><br>I`m not sure if this has to do with routing or Nat problems? <br><br>thanks in advance  :)<br><br>I hava a drawing attached<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#FFFFFF nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/27868578?c=2063504&ret=L2ZvcnVtL3IyNzg2ODU3OC54bWw%3D"><IMG class="apic" BORDER=0 TITLE="776999 bytes" WIDTH=600 HEIGHT=400 SRC="/r0/download/2063504.thumb600~4c63101b2ffb3b504a2f9e1b3f90807e/Network.jpg/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Routing-problem-USG-50-27868578</guid>
<pubDate>Mon, 31 Dec 2012 10:47:38 EDT</pubDate>
</item>

</channel>
</rss>
