<?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 Re: setting iptables in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096589#M87568</link>
    <description>&lt;BR /&gt;I am not to sure of what you need, so correct me if i am on the wrong track.&lt;BR /&gt;&lt;BR /&gt;No not user you can identify the "node" from where a packet is from or going to by its mac address, this is very low in your network stack (4 level model), iptables deal with such a low level, so it knows about things like mac address(XX:XX:XX:XX:XX:XX),ip(XXX.XXX.XXX.XXX), it now about protocol like (tcp,udp..etc), but it does not know about thing at levels like user name.&lt;BR /&gt;&lt;BR /&gt;If what you are after is how to construct an iptable rule to deal with a mac address then the following should do it. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;iptables -A FORWARD -m mac --mac-source XX:XX:XX:XX:XX -j ACCEPT&lt;BR /&gt;iptables -A FORWARD -m mac --mac-source XX:XX:XY:XY:XY -j DROP&lt;BR /&gt;&lt;BR /&gt;Let us know if this is what you need.&lt;BR /&gt;&lt;BR /&gt;J-P</description>
    <pubDate>Sat, 18 Oct 2003 04:26:16 GMT</pubDate>
    <dc:creator>Huc_1</dc:creator>
    <dc:date>2003-10-18T04:26:16Z</dc:date>
    <item>
      <title>setting iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096588#M87567</link>
      <description>hello all members&lt;BR /&gt;hope u r fine&lt;BR /&gt;&lt;BR /&gt;i want to configure my iptables to authenticate users by their MAC is that possible or is there any other way to authenticate users in LAN. &lt;BR /&gt;&lt;BR /&gt;plz advice</description>
      <pubDate>Sat, 18 Oct 2003 03:34:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096588#M87567</guid>
      <dc:creator>Muhammad Imran Hussain</dc:creator>
      <dc:date>2003-10-18T03:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: setting iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096589#M87568</link>
      <description>&lt;BR /&gt;I am not to sure of what you need, so correct me if i am on the wrong track.&lt;BR /&gt;&lt;BR /&gt;No not user you can identify the "node" from where a packet is from or going to by its mac address, this is very low in your network stack (4 level model), iptables deal with such a low level, so it knows about things like mac address(XX:XX:XX:XX:XX:XX),ip(XXX.XXX.XXX.XXX), it now about protocol like (tcp,udp..etc), but it does not know about thing at levels like user name.&lt;BR /&gt;&lt;BR /&gt;If what you are after is how to construct an iptable rule to deal with a mac address then the following should do it. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;iptables -A FORWARD -m mac --mac-source XX:XX:XX:XX:XX -j ACCEPT&lt;BR /&gt;iptables -A FORWARD -m mac --mac-source XX:XX:XY:XY:XY -j DROP&lt;BR /&gt;&lt;BR /&gt;Let us know if this is what you need.&lt;BR /&gt;&lt;BR /&gt;J-P</description>
      <pubDate>Sat, 18 Oct 2003 04:26:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096589#M87568</guid>
      <dc:creator>Huc_1</dc:creator>
      <dc:date>2003-10-18T04:26:16Z</dc:date>
    </item>
    <item>
      <title>Re: setting iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096590#M87569</link>
      <description>hello&lt;BR /&gt;&lt;BR /&gt;yes u r right,&lt;BR /&gt;&amp;amp; also plz guide how to allow or disallow known application &amp;amp; ports like allowing msn, yahoo,http &amp;amp; disallowing kazaa, imesh.&lt;BR /&gt;&lt;BR /&gt;Thank u for understanding&lt;BR /&gt;</description>
      <pubDate>Sat, 18 Oct 2003 05:03:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096590#M87569</guid>
      <dc:creator>Muhammad Imran Hussain</dc:creator>
      <dc:date>2003-10-18T05:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: setting iptables</title>
      <link>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096591#M87570</link>
      <description>First, allow the MAC addresses the way Jean Pierre suggested.&lt;BR /&gt;Then, the best is to allow the ports corresponding to what you need, and dissallow the rest (including imesh and other kazaas).&lt;BR /&gt;Steven provided a good example in this thread :&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x67de68da2286d711abdc0090277a778c%2C00.html&amp;amp;admit=716493758+1066482174278+28353475" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x67de68da2286d711abdc0090277a778c%2C00.html&amp;amp;admit=716493758+1066482174278+28353475&lt;/A&gt;&lt;BR /&gt;You may wish to try this one, adding at the begining the MAC addresses. You can also use the tips we gave you here :&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x9d4b8b82cc91d711abdc0090277a778c%2C00.html&amp;amp;admit=716493758+1066481908866+28353475" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0x9d4b8b82cc91d711abdc0090277a778c%2C00.html&amp;amp;admit=716493758+1066481908866+28353475&lt;/A&gt;&lt;BR /&gt;Ask us if you want some comment on the file.&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;J</description>
      <pubDate>Sat, 18 Oct 2003 08:03:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/setting-iptables/m-p/3096591#M87570</guid>
      <dc:creator>Jerome Henry</dc:creator>
      <dc:date>2003-10-18T08:03:15Z</dc:date>
    </item>
  </channel>
</rss>

