11:45 p.m.
For some reason I am having a tough time getting my linux server to act
as a router. Can someone give me some basic instructions so that I can
figure out what I am missing
Thanks
Richard Tracy
12:33 a.m.
Am Fr, den 27.02.2004 schrieb linux server um 06:45:
For some reason I am having a tough time getting my linux server to
act
as a router. Can someone give me some basic instructions so that I can
figure out what I am missing
You should ive some information about the task the route has to perform:
- routing between two offfical standard networks
- routing from a private network (home/office) with adress translation
- what type of networks (ethernet - ethernet / cable - ethernet / ...)
- firewall requirements
As a first information you may study
http://www.linuxguruz.com/iptables/howto/2.4routing.html
Peter
1:09 a.m.
Am Fr, den 27.02.2004 schrieb linux server um 06:45:
> For some reason I am having a tough time getting my linux server to act
> as a router. Can someone give me some basic instructions so that I can
> figure out what I am missing
You should ive some information about the task the route has to perform:
- routing between two offfical standard networks
- routing from a private network (home/office) with adress translation
- what type of networks (ethernet - ethernet / cable - ethernet / ...)
- firewall requirements
As a first information you may study
http://www.linuxguruz.com/iptables/howto/2.4routing.html
Peter
for just having basic routing functions, check in /proc/sys/net/ipv4
whether your ip_forward is set to 1. if no, do echo 1 > ip_forward and
your fedora box should immediately handle as a router.
check with /sbin/route, whether your routes to your other networks are set
clearly, specially the default gateway.
as mentionned above, this does just routing between 2 tcp/ip-networks, no
masquerading/NAT and other security issues. To configure this out easily
and quickly i could recommend firestarter.
HTH
Roger
5:31 a.m.
On Friday 27 February 2004 09:09, Roger Grosswiler wrote:
for just having basic routing functions, check in /proc/sys/net/ipv4
whether your ip_forward is set to 1. if no, do echo 1 > ip_forward and
your fedora box should immediately handle as a router.
The "RedHat (tm)" way of doing this is putting it in /etc/sysctl.conf
AFAIK.
--- cut ---
# Controls IP packet forwarding
net.ipv4.ip_forward = 1
--- cut ---
if you need some more control over the routing, please read
/usr/share/doc/initscripts-x.xx/* to see how to change/add files
in your /etc/sysconfig/network-scripts
I personally like to have:
--- /etc/sysconfig/network-scripts/route-lo ---
unreachable 10.0.0.0/8
unreachable 172.16.0.0/12
unreachable 192.168.0.0/16
--- end ---
to make sure I will not route unknown private nets to the whole internet.
The private subnets I use are shorter routes, so they take precedence.
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
5:35 a.m.
On Fri, Feb 27, 2004 at 01:31:56PM +0200, Doncho N. Gunchev wrote:
The "RedHat (tm)" way of doing this is putting it in
/etc/sysctl.conf AFAIK.
--- cut ---
# Controls IP packet forwarding
net.ipv4.ip_forward = 1
--- cut ---
Since when is using sysctl considered to be RH-specific?
It is not, AFAIK.
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
6:14 a.m.
On Fri, 27 Feb 2004 12:35:05 +0100 Jos Vos <jos(a)xos.nl> wrote:
On Fri, Feb 27, 2004 at 01:31:56PM +0200, Doncho N. Gunchev wrote:
> The "RedHat (tm)" way of doing this is putting it in
/etc/sysctl.conf AFAIK.
> --- cut ---
> # Controls IP packet forwarding
> net.ipv4.ip_forward = 1
Since when is using sysctl considered to be RH-specific?
It is not, AFAIK.
it's not even Linux specific, although the names in /etc/sysctl.conf
may vary from un*x to the next.
richard
--
Richard Welty rwelty(a)averillpark.net
Averill Park Networking 518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security
6:30 a.m.
On Fri, 27 Feb 2004 12:35:05 +0100 Jos Vos <jos(a)xos.nl> wrote:
> On Fri, Feb 27, 2004 at 01:31:56PM +0200, Doncho N. Gunchev wrote:
> > The "RedHat (tm)" way of doing this is putting it in /etc/sysctl.conf
> AFAIK.
> > --- cut ---
> > # Controls IP packet forwarding
> > net.ipv4.ip_forward = 1
> Since when is using sysctl considered to be RH-specific?
> It is not, AFAIK.
it's not even Linux specific, although the names in /etc/sysctl.conf
may vary from un*x to the next.
right. seems that i missed out something ;-) thanx for information,
otherwise it would get a new thread if i would have to install the next
linux-router ;-) thought it is still in /etc/sysconfig/blabla
richard
--
Richard Welty
rwelty(a)averillpark.net
Averill Park Networking
518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
7:31 a.m.
On Friday 27 February 2004 13:35, Jos Vos wrote:
On Fri, Feb 27, 2004 at 01:31:56PM +0200, Doncho N. Gunchev wrote:
> The "RedHat (tm)" way of doing this is putting it in /etc/sysctl.conf
AFAIK.
> --- cut ---
> # Controls IP packet forwarding
> net.ipv4.ip_forward = 1
> --- cut ---
Since when is using sysctl considered to be RH-specific?
It is not, AFAIK.
I did not mean it is RedHat specific, I wanted to say it is the way RedHat
does this. I bet there are other Linux distros and *nix-es that have sysctl.
If you just 'echo 1 > /proc....' and then 'service network restart'
redhat
scripts will override your seting... that's what I wanted to say... but seems
i did not do it clear :) Sorry for my English...
10xz for correcting me.
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
8:06 a.m.
Thank you very much I got it working using zebra
Thanks
Richard Tracy
On Thu, 2004-02-26 at 23:09, Roger Grosswiler wrote:
> Am Fr, den 27.02.2004 schrieb linux server um 06:45:
>> For some reason I am having a tough time getting my linux server to act
>> as a router. Can someone give me some basic instructions so that I can
>> figure out what I am missing
>
> You should ive some information about the task the route has to perform:
> - routing between two offfical standard networks
> - routing from a private network (home/office) with adress translation
> - what type of networks (ethernet - ethernet / cable - ethernet / ...)
> - firewall requirements
>
> As a first information you may study
> http://www.linuxguruz.com/iptables/howto/2.4routing.html
>
> Peter
for just having basic routing functions, check in /proc/sys/net/ipv4
whether your ip_forward is set to 1. if no, do echo 1 > ip_forward and
your fedora box should immediately handle as a router.
check with /sbin/route, whether your routes to your other networks are set
clearly, specially the default gateway.
as mentionned above, this does just routing between 2 tcp/ip-networks, no
masquerading/NAT and other security issues. To configure this out easily
and quickly i could recommend firestarter.
HTH
Roger
10:40 a.m.
How do I set it up so that the ip_forward is set permanently, when I
reboot it sets it back to 0. Also if I set the ip_forward to 1 am I
using the zebra program or am I using the O/S
Thanks for your help
Richard Tracy
On Thu, 2004-02-26 at 23:09, Roger Grosswiler wrote:
> Am Fr, den 27.02.2004 schrieb linux server um 06:45:
>> For some reason I am having a tough time getting my linux server to act
>> as a router. Can someone give me some basic instructions so that I can
>> figure out what I am missing
>
> You should ive some information about the task the route has to perform:
> - routing between two offfical standard networks
> - routing from a private network (home/office) with adress translation
> - what type of networks (ethernet - ethernet / cable - ethernet / ...)
> - firewall requirements
>
> As a first information you may study
> http://www.linuxguruz.com/iptables/howto/2.4routing.html
>
> Peter
for just having basic routing functions, check in /proc/sys/net/ipv4
whether your ip_forward is set to 1. if no, do echo 1 > ip_forward and
your fedora box should immediately handle as a router.
check with /sbin/route, whether your routes to your other networks are set
clearly, specially the default gateway.
as mentionned above, this does just routing between 2 tcp/ip-networks, no
masquerading/NAT and other security issues. To configure this out easily
and quickly i could recommend firestarter.
HTH
Roger
10:21 p.m.
linux server wrote:
How do I set it up so that the ip_forward is set permanently, when I
reboot it sets it back to 0. Also if I set the ip_forward to 1 am I
using the zebra program or am I using the O/S
Thanks for your help
Richard Tracy
Make it persistent by editing the /etc/sysctl.conf file changing
net.ipv4.ip_forward = 0
To a 1 instead.
Routing is built-in, not zebra. There is no router to router protocol
involved here so only the routes configured staticly or from bringing up
interfaces are known. See output of 'route' command (run as root) to
see what the configured routes are.
Chris
--
-----------------------------------------------------------
"Spend less! Do more! Go Open Source..." -- Dirigo.net
Chris Johnson, RHCE #807000448202021
7358
days inactive
7362
days old
10 comments
7 participants
participants (7)
-
Christopher K. Johnson -
Doncho N. Gunchev -
Jos Vos -
linuxserver -
Peter Boy -
Richard Welty -
Roger Grosswiler