Skip to contentSkip to conversation

Routing problem !!!

LARTC Vaquer0 2 participants 3 messages Nov 27, 2003 – Dec 1, 2003

lore
Share & tools
lore

Vaquer0

author
#0 lore raw

Can anybody help me ?

This is my configuration:

eth0: 10.0.0.2/16
eth1: 10.0.0.1 (inet gateway)

#ip ru l :

0:      from all lookup local
32765:  from 10.0.0.2 lookup tabla1
32766:  from all lookup main
32767:  from all lookup default

#ip r l t tabla1

10.0.0.0/16 dev eth0 scope link src 10.0.0.2
127.0.0.0/8 dev lo scope link
default via 10.0.0.1 dev eth0

#ip r l t main

10.0.0.0/16 dev eth0 scope link

#ip r l t local

broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
broadcast 10.0.0.0 dev eth0 proto kernel scope link src 10.0.0.2 local 10.0.0.2 dev eth0 proto kernel scope host src 10.0.0.2 broadcast 10.0.255.255 dev eth0 proto kernel scope link src 10.0.0.2 broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1 local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1 local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1

why can't i connect to inet ??

thanks

Signature · 5 lines
Vaquer0 <[email protected]>

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

: This is my configuration:
:
:
: eth0: 10.0.0.2/16
: eth1: 10.0.0.1 (inet gateway)
:
: #ip ru l :
:

 : 0:      from all lookup local
 : 32765:  from 10.0.0.2 lookup tabla1
 : 32766:  from all lookup main
 : 32767:  from all lookup default

:
:
: #ip r l t tabla1
:
:
: 10.0.0.0/16 dev eth0 scope link src 10.0.0.2
: 127.0.0.0/8 dev lo scope link
: default via 10.0.0.1 dev eth0
:
: #ip r l t main
:
: 10.0.0.0/16 dev eth0 scope link

[ local routing table snipped ]

: why can't i connect to inet ??

Probably because your router doesn't have a way to send packets to 10.0.0.1 even if the source address on the outbound packet is 10.0.0.2. Add one more route to tabla1:

  # ip route add 10.0.0.1 dev eth1 table tabla1
  # ip route change default via 10.0.0.1 dev eth1 table tabla1

Once you can ping 10.0.0.1 from your policy routing device, then you should be able to hit the Internet from the same device.

You didn't explain anything about what applications or functions this box hosts, so there's nothing more to say here.

-Martin

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

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

Martin, as you can see in my last post i have route to 10.0.0.1 in the main routing table , so i have ping to the gateway but i can't connect to inet.

: #ip r l t main

Quoted 3 lines

:
: 10.0.0.0/16 dev eth0 scope link

The only way to connect to inet is adding:

ip r a default via 10.0.0.1 t main

If i add the default gw in table main , i can connect to inet but i'd like to do this in other table.

Can you help me ?

thanks.

Quoted 43 lines · Martin A. Brown

: This is my configuration:
:
:
: eth0: 10.0.0.2/16
: eth1: 10.0.0.1 (inet gateway)
:
: #ip ru l :
:

 : 0:      from all lookup local
 : 32765:  from 10.0.0.2 lookup tabla1
 : 32766:  from all lookup main
 : 32767:  from all lookup default

:
:
: #ip r l t tabla1
:
:
: 10.0.0.0/16 dev eth0 scope link src 10.0.0.2
: 127.0.0.0/8 dev lo scope link
: default via 10.0.0.1 dev eth0
:
: #ip r l t main
:
: 10.0.0.0/16 dev eth0 scope link

[ local routing table snipped ]

: why can't i connect to inet ??

Probably because your router doesn't have a way to send packets to 10.0.0.1 even if the source address on the outbound packet is 10.0.0.2. Add one more route to tabla1:

  # ip route add 10.0.0.1 dev eth1 table tabla1
  # ip route change default via 10.0.0.1 dev eth1 table tabla1

Once you can ping 10.0.0.1 from your policy routing device, then you should be able to hit the Internet from the same device.

You didn't explain anything about what applications or functions this box hosts, so there's nothing more to say here.

-Martin

Signature · 5 lines
Vaquer0 <[email protected]>

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