<?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: using Linux as a bridge and firewall in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742524#M90196</link>
    <description>All, I got this to work. Basically I was missing a patch for kernel 2.4.18; specificallly the bridging patch.</description>
    <pubDate>Wed, 12 Jun 2002 20:17:19 GMT</pubDate>
    <dc:creator>K.C. Chan</dc:creator>
    <dc:date>2002-06-12T20:17:19Z</dc:date>
    <item>
      <title>using Linux as a bridge and firewall</title>
      <link>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742521#M90193</link>
      <description>All,&lt;BR /&gt;I've tried setting up RH 7.2 as a Bridge and Firewall. I've re-compiled the kernel 2.4.18 to include bridging. Put eth0 and eth1 in promiscius mode and enable bridging via "brcfg -ena"&lt;BR /&gt;but it's still not working bec. I am only able to ping one side of the network not the other.&lt;BR /&gt;&lt;BR /&gt;Here's what I want to do, I have eth0=63.x.x.x.133 and eth1 as 63.x.x.x.134. eth0 has a route to the default router and eth1 is connected to a hub/switch (the protected side of the network; this is only a test, as soon as I get this to work with iptables it's going in btw the router and the switch).  How do I make eth0 and eth1 pass network traffic to each other so that I can ping all servers on eth0 side and all servers on eth1 side?</description>
      <pubDate>Wed, 12 Jun 2002 02:23:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742521#M90193</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2002-06-12T02:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: using Linux as a bridge and firewall</title>
      <link>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742522#M90194</link>
      <description>Hi,&lt;BR /&gt;Have configured in such a way that only non-routable protocols to be bridged and IP should&lt;BR /&gt;be routed ?.&lt;BR /&gt;regards,&lt;BR /&gt;U.SivaKumar</description>
      <pubDate>Wed, 12 Jun 2002 04:49:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742522#M90194</guid>
      <dc:creator>U.SivaKumar_2</dc:creator>
      <dc:date>2002-06-12T04:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: using Linux as a bridge and firewall</title>
      <link>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742523#M90195</link>
      <description>Yes, I've tried routing but it onl works on 1 interface of the NIC; since both Nic have the same network (63.78.100.0 I can only seem to route out one interface). e.g:&lt;BR /&gt;Kernel IP routing table&lt;BR /&gt;Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface&lt;BR /&gt;63.78.100.0     0.0.0.0         255.255.255.0   U        40 0          0 eth1&lt;BR /&gt;63.78.100.0     0.0.0.0         255.255.255.0   U        40 0          0 eth1&lt;BR /&gt;127.0.0.0       0.0.0.0         255.0.0.0       U        40 0          0 lo&lt;BR /&gt;0.0.0.0         63.78.100.1     0.0.0.0         UG       40 0          0 esome_pc_on_eth0_sideth0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;For some reason I can ping with "ping -I eth0 some_pc_on_eth0_side", it works and vice versa with "ping -I eth1 some_pc_on_eth0_side". But if I ping with the "-I" option, it doesn't work. I know if I tried to ping (w/o the -I option) the router  which in on eth0 side, I can't reach it because both route for 63.78.100.0 points to eth1 side. I've tried adding 63.78.100.0 for eth0 but it doesn't work. This is why I think a bridge might work. Any idea on how should I approach this? Should I use bridging or Routing. If so please shed some light onto this. Thanks.</description>
      <pubDate>Wed, 12 Jun 2002 13:09:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742523#M90195</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2002-06-12T13:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: using Linux as a bridge and firewall</title>
      <link>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742524#M90196</link>
      <description>All, I got this to work. Basically I was missing a patch for kernel 2.4.18; specificallly the bridging patch.</description>
      <pubDate>Wed, 12 Jun 2002 20:17:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/using-linux-as-a-bridge-and-firewall/m-p/2742524#M90196</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2002-06-12T20:17:19Z</dc:date>
    </item>
  </channel>
</rss>

