hi, So I have the following: ROUTER 10.0.0.254 | 10.0.0.3(eth0) MY_DEBIAN_RTR 209.52.x.126(eth1) | LAN (the 209.52.x.64/26 subnet) I need to route the 209.52.x.64 subnet through MY_DEBIAN_RTR and on to the telephone company router. I''d probably like 209.52.x to have it''s own table (if that is a good idea). The debian box will eventually do some firewalling, and some traffic monitoring. But first I have to get the traffic flowing. I have read some docs, and the HOTO, but they were not too much help. Thanks, j. -- ...................... ..... Jason C. Leach .. Current PGP/GPG Key ID: 43AD2024 _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
As you can confirm in your own draw that you shown us, you have different nets . You need : 1.- A static route to ROUTER 10.0.0.254 from de LAN 209 or 2.- Configure some routing protocols like RIP with Zebra suite. These configurations tipe are the same as Cisco routers, for any configurations problem you can look at www.cisco.com and search "configuring RIP" for example Best Regards!!!! LievenX -.-.LievenX..--. ----- Mensaje Original ----- De: "Jason C. Leach" <jleach@ocis.net> Fecha: Jueves, Septiembre 26, 2002 4:47 am Asunto: [LARTC] simple question> hi, > > So I have the following: > > ROUTER 10.0.0.254 > | > 10.0.0.3(eth0) > MY_DEBIAN_RTR > 209.52.x.126(eth1) > | > LAN (the 209.52.x.64/26 subnet) > > > I need to route the 209.52.x.64 subnet through MY_DEBIAN_RTR > and on to the telephone company router. I''d probably like > 209.52.x to have it''s own table (if that is a good idea). > The debian box will eventually do some firewalling, and some > traffic monitoring. But first I have to get the traffic flowing. > > I have read some docs, and the HOTO, but they were not too > much help. > > Thanks, > j. > > > > -- > ...................... > ..... Jason C. Leach > .. > > Current PGP/GPG Key ID: 43AD2024 > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/ >_______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a linuxbox running shorewall, and on the lan side nic I have multiple networks, and ip''s from both assigned to the nic. One network is private, and the other is public ip''s. I have a web server running on the firewall with multiple virtual hosts configured. I have the private ip on the lan tied to the default apache config, and the public ip on the lan tied to a vurtual configuration. Also the public ip on the wan is tied to another virtual host. I want all web traffic on the private network that is trying to go through the firewall to get forwarded to the firewall and be answered by the apache default config. All this config will do is redirects the request to my domain. So no matter where they try to go, they will end up at my page. The following will do the trick. ACCEPT lan:192.168.1.0/24 fw:192.168.1.1:80 tcp http - all I think it is required to specify the 192.168.1.1 on the firewall so it is answered by the proper apache config. Am I right? The 192.168.1.1 is the main ip on the nic, and the public ip is a alias. Then came the question, will the following rule do the same thing? ACCEPT lan:192.168.1.0/24 lan:192.168.1.1:80 tcp http - all Would this act any different? - -- Regards Joseph Watson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9l9v5ABydhMNsDgMRAqX/AJ49x9j4fK4eVuwfQJMxA15YWKdHoACgzhKv mGExxcT5A/DK6prz2L1yBog=z1pS -----END PGP SIGNATURE----- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 30 September 2002 01:07 am, Joseph Watson wrote:> Hello, >Sorry I have the wrong list here :) - -- Regards Joseph Watson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9l92+ABydhMNsDgMRAp1vAJ9wUqtPWCqXGOqVN2hu+dJtX+oKFQCgkBub 7DK5G7KEIqa3EwkbZUeiIXc=HiAH -----END PGP SIGNATURE----- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/