<?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>MQX Software SolutionsのトピックRe: Reply on same interface as incoming?</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235287#M6526</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN class="GingerNoCheckStart"&gt;&lt;/SPAN&gt;Hi christian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you solved the problem. Congratz... well done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;ram&lt;/P&gt;&lt;P&gt;&lt;SPAN class="GingerNoCheckEnd"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Jul 2013 12:00:40 GMT</pubDate>
    <dc:creator>Ramtry</dc:creator>
    <dc:date>2013-07-19T12:00:40Z</dc:date>
    <item>
      <title>Reply on same interface as incoming?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235283#M6522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a system with two interfaces. Both interfaces are connected to the internet.&lt;/P&gt;&lt;P&gt;One of them is set as the default route. A side effect of this is that if a packet comes in on the non-default-route interface,&lt;/P&gt;&lt;P&gt;the reply is sent back through the default route interface. But i want to send it back to the incomming interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My Problem is, one of these interfaces is behind a router in a subnet and the router ist forwarding incomming packages to this interface.&lt;/P&gt;&lt;P&gt;Now, i will answer to the the same interface, but RTCS can't reach/find the incomming ip-adress and try to send it back to the defaultgateway(other interface).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to create for each interface an extra routingtable(ipradix) or is there an simpler way to realise this problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope somebody can help me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 10:19:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235283#M6522</guid>
      <dc:creator>chris-quin</dc:creator>
      <dc:date>2013-06-24T10:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: Reply on same interface as incoming?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235284#M6523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As soon as RTCS IPv4 sends a packet to a different subnet, it goes via gateway. RTCS IPv6 allows to select the interface, but not RTCS IPv4, as far as I am aware. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 11:42:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235284#M6523</guid>
      <dc:creator>Martin_</dc:creator>
      <dc:date>2013-07-19T11:42:35Z</dc:date>
    </item>
    <item>
      <title>Re: Reply on same interface as incoming?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235285#M6524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Martin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for your reply.&lt;/P&gt;&lt;P&gt;Now i am able to send IPv4 packages.&lt;/P&gt;&lt;P&gt;I edited MQX, so now i am able to root over Interface. Everything works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If somebody need a solution, i can post the modified code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;greetings chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 11:55:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235285#M6524</guid>
      <dc:creator>chris-quin</dc:creator>
      <dc:date>2013-07-19T11:55:32Z</dc:date>
    </item>
    <item>
      <title>Re: Reply on same interface as incoming?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235286#M6525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Christian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the same type of application. But &lt;SPAN class="GINGER_SOFATWARE_correct"&gt;i&lt;/SPAN&gt; am using QT creator for handling the network related packet. Two ethernet port say eth0 and eth1 both are connected to &lt;SPAN class="GINGER_SOFATWARE_correct"&gt;router&lt;/SPAN&gt; and port forwarding is done in eth0. Client connection and packet handling are done in QT with &lt;SPAN class="GINGER_SOFATWARE_correct"&gt;asyn&lt;/SPAN&gt; server-client &lt;SPAN class="GINGER_SOFATWARE_correct"&gt;prgramming&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="GINGER_SOFATWARE_correct"&gt;thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="GINGER_SOFATWARE_correct"&gt;ram&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 11:59:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235286#M6525</guid>
      <dc:creator>Ramtry</dc:creator>
      <dc:date>2013-07-19T11:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: Reply on same interface as incoming?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235287#M6526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN class="GingerNoCheckStart"&gt;&lt;/SPAN&gt;Hi christian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you solved the problem. Congratz... well done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;ram&lt;/P&gt;&lt;P&gt;&lt;SPAN class="GingerNoCheckEnd"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 12:00:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235287#M6526</guid>
      <dc:creator>Ramtry</dc:creator>
      <dc:date>2013-07-19T12:00:40Z</dc:date>
    </item>
    <item>
      <title>Re: Reply on same interface as incoming?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235288#M6527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ram Ramasamy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i solve/fixed the problem for me. I increased a little bit mqx.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if a new interface is added, i additional register which gateway was used and added this and the interface together. If a TCP/IP message receive and i will send a package, i am looking for the interface with the &lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;corresponding gateway and register this to the hop-destination.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;greeting chris&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 12:09:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235288#M6527</guid>
      <dc:creator>chris-quin</dc:creator>
      <dc:date>2013-07-19T12:09:56Z</dc:date>
    </item>
    <item>
      <title>Re: Reply on same interface as incoming?</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235289#M6528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Christian, I think it would be great if you post your modifications to MQX, to get this working. There have been more users asking for this kind of functionality on this forum and seems that you have functional solution. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jul 2013 12:11:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Reply-on-same-interface-as-incoming/m-p/235289#M6528</guid>
      <dc:creator>Martin_</dc:creator>
      <dc:date>2013-07-19T12:11:32Z</dc:date>
    </item>
  </channel>
</rss>

