Skip to contentSkip to conversation

additional routes?

LARTC Tomas Bonnedahl 2 participants 5 messages Nov 28, 2002 – Nov 29, 2002

lore
Share & tools
lore
#0 lore raw

hello, a simple question; on a router, if I want network A to be routed to network C that goes through network B, using policy routing, do i need to specify a route to network B also, or could i just have routes to A and C in the routing table?

the reason that im asking is because i dont know how the ip utility uses the main table together with antoher table. if i didnt use policy routing, just "regular", this would not work, but perhaps if not finding a route to network B, it checks the main table?

please enlighten me.

regards,

tomas bonnedahl
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#1 lore raw

(Forwarded to the list because I can't properly operate a MUA--maybe they'll take away my license to read email someday.)

Tomas,

Perhaps you want a summary of how the kernel makes a routing decision?

See my description of the route selection process:

http://plorf.net/linux-ip/html/routing-selection.htm

I'm not sure you need policy routing though... If network B is reachable from network A, and the router for network B is directly connected to network A but is not the default gateway, you'll have something sort of like this:

network-C via router-B
network-B via router-B
network-A dev ethX
default via default-gw

Is this your configuration? If so, then you need no policy routing.

-Martin

On Thu, 28 Nov 2002, Tomas Bonnedahl wrote:

: hello, a simple question; on a router, if I want network A to be routed : to network C that goes through network B, using policy routing, do i : need to specify a route to network B also, or could i just have routes : to A and C in the routing table?
:
: the reason that im asking is because i dont know how the ip utility : uses the main table together with antoher table. if i didnt use policy : routing, just "regular", this would not work, but perhaps if not : finding a route to network B, it checks the main table?
:
:
: please enlighten me.
:
: regards,
:
: tomas bonnedahl
: _______________________________________________
: LARTC mailing list / [email protected]
: http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
:

Signature · 8 lines
Martin A. Brown --- SecurePipe, Inc. --- [email protected]




_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#2 lore raw
In reply to Tomas Bonnedahl

thanks for your reply martin, i am yet to read your paper.

the reason for using policy routing is that i manage several networks and i do want some kind of control on who can access whose network. this i thought is best accomplished with policy routing using ip route and ip rule.

if i want to allow hosts from network A to reach and talk to hosts on network C, but _not_ hosts on network B, is this best controlled by iptables? since i now probably need to specify the route to network B in that very table, i cannot deny network A hosts to talk to network B with ip, or can i?

regards,

tomas bonnedahl

Quoted 36 lines · Martin A. Brown

Tomas,

Perhaps you want a summary of how the kernel makes a routing decision?

See my description of the route selection process:

http://plorf.net/linux-ip/html/routing-selection.htm

I'm not sure you need policy routing though... If network B is reachable from network A, and the router for network B is directly connected to network A but is not the default gateway, you'll have something sort of like this:

network-C via router-B
network-B via router-B
network-A dev ethX
default via default-gw

Is this your configuration? If so, then you need no policy routing.

-Martin

On Thu, 28 Nov 2002, Tomas Bonnedahl wrote:

: hello, a simple question; on a router, if I want network A to be routed : to network C that goes through network B, using policy routing, do i : need to specify a route to network B also, or could i just have routes : to A and C in the routing table?
:
: the reason that im asking is because i dont know how the ip utility : uses the main table together with antoher table. if i didnt use policy : routing, just "regular", this would not work, but perhaps if not : finding a route to network B, it checks the main table?
:
:
: please enlighten me.

Quoted 15 lines

:
: regards,
:
: tomas bonnedahl
: _______________________________________________
: LARTC mailing list / [email protected]
: http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
:

Signature · 1 line
Martin A. Brown --- SecurePipe, Inc. --- [email protected]

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#3 lore raw
In reply to Tomas Bonnedahl

Tomas,

I'm glad to be of help.

: if i want to allow hosts from network A to reach and talk to hosts on : network C, but _not_ hosts on network B, is this best controlled by : iptables? since i now probably need to specify the route to network B : in that very table, i cannot deny network A hosts to talk to network B : with ip, or can i?

I'd suggest you use iptables and a prohibit route:

http://plorf.net/linux-ip/html/tools-ip-route.htm#EX-TOOLS-IP-ROUTE-ADD-FROM

Here's an example:

# ip route add prohibit x.x.x.x/24 from y.y.y.y/24

I would be inclined to block packets at the packet filter as well.

# iptables -t filter -A FORWARD -d x.x.x.x/24 -s y.y.y.y/24 -j REJECT

Good luck,

-Martin

Signature · 7 lines
Martin A. Brown --- SecurePipe, Inc. --- [email protected]



_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#4 lore raw
In reply to Tomas Bonnedahl

hello again and thanks for replying.

the prohibit rule is supposed to be in that particular table that im creating for hosts whose src address is network A? i was also thinking of blackholeing as default. would this work?

ip route add networkB dev eth1 table X
ip route add networkA via networkB-router dev eth1 table X ip route add 0/0 blackhole table X
<rule for making networkA hosts use table X>

since i dont want to use iptables too much either.

thanks

-tomas

Quoted 19 lines · Martin A. Brown

Tomas,

I'm glad to be of help.

: if i want to allow hosts from network A to reach and talk to hosts on : network C, but _not_ hosts on network B, is this best controlled by : iptables? since i now probably need to specify the route to network B : in that very table, i cannot deny network A hosts to talk to network B : with ip, or can i?

I'd suggest you use iptables and a prohibit route:

http://plorf.net/linux-ip/html/tools-ip-route.htm#EX-TOOLS-IP-ROUTE-ADD-FROM

Here's an example:

# ip route add prohibit x.x.x.x/24 from y.y.y.y/24
Quoted 14 lines

I would be inclined to block packets at the packet filter as well.

# iptables -t filter -A FORWARD -d x.x.x.x/24 -s y.y.y.y/24 -j REJECT

Good luck,

-Martin

Signature · 1 line
Martin A. Brown --- SecurePipe, Inc. --- [email protected]

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/