HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: using Linux as a bridge and firewall
Operating System - Linux
1833738
Members
2526
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2002 07:23 PM
06-11-2002 07:23 PM
using Linux as a bridge and firewall
All,
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"
but it's still not working bec. I am only able to ping one side of the network not the other.
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?
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"
but it's still not working bec. I am only able to ping one side of the network not the other.
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?
Reputation of a thousand years can be determined by the conduct of an hour
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2002 09:49 PM
06-11-2002 09:49 PM
Re: using Linux as a bridge and firewall
Hi,
Have configured in such a way that only non-routable protocols to be bridged and IP should
be routed ?.
regards,
U.SivaKumar
Have configured in such a way that only non-routable protocols to be bridged and IP should
be routed ?.
regards,
U.SivaKumar
Innovations are made when conventions are broken
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2002 06:09 AM
06-12-2002 06:09 AM
Re: using Linux as a bridge and firewall
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:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
63.78.100.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1
63.78.100.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo
0.0.0.0 63.78.100.1 0.0.0.0 UG 40 0 0 esome_pc_on_eth0_sideth0
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.
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
63.78.100.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1
63.78.100.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo
0.0.0.0 63.78.100.1 0.0.0.0 UG 40 0 0 esome_pc_on_eth0_sideth0
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.
Reputation of a thousand years can be determined by the conduct of an hour
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2002 01:17 PM
06-12-2002 01:17 PM
Re: using Linux as a bridge and firewall
All, I got this to work. Basically I was missing a patch for kernel 2.4.18; specificallly the bridging patch.
Reputation of a thousand years can be determined by the conduct of an hour
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP