<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic dhcp-default-router with interface ve in Korea – 한국어</title>
    <link>https://community.ruckuswireless.com/t5/Korea-%ED%95%9C%EA%B5%AD%EC%96%B4/dhcp-default-router-with-interface-ve/m-p/100156#M31</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Is there a way to allow the terminal to receive dhcp even if the dhcp-default-router ip of dhcp and the interface ve ip are different?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 29 Nov 2024 08:24:55 GMT</pubDate>
    <dc:creator>user_e8ad9f</dc:creator>
    <dc:date>2024-11-29T08:24:55Z</dc:date>
    <item>
      <title>dhcp-default-router with interface ve</title>
      <link>https://community.ruckuswireless.com/t5/Korea-%ED%95%9C%EA%B5%AD%EC%96%B4/dhcp-default-router-with-interface-ve/m-p/100156#M31</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Is there a way to allow the terminal to receive dhcp even if the dhcp-default-router ip of dhcp and the interface ve ip are different?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Nov 2024 08:24:55 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Korea-%ED%95%9C%EA%B5%AD%EC%96%B4/dhcp-default-router-with-interface-ve/m-p/100156#M31</guid>
      <dc:creator>user_e8ad9f</dc:creator>
      <dc:date>2024-11-29T08:24:55Z</dc:date>
    </item>
  </channel>
</rss>

