Re: NETWORK ROUTES
My problem with the both of routers is that I cannot configure it. If I
would be able to configure, I would not have problems....
----- Original Message -----
From: "Jean-Francois Dive" <jef@linuxbe.org>
To: "Ángel Carrasco" <falkom@arrakis.es>
Cc: "Jeremy C. Reed" <reed@wcug.wwu.edu>; "Ángel Carrasco"
<acarrasco@escomposlinux.org>; "Debian ISP List"
<debian-isp@lists.debian.org>
Sent: Friday, October 25, 2002 4:49 AM
Subject: Re: NETWORK ROUTES
> 2 possibilities
>
> remove the from statement to match all traffic and so make the route
> to the outside available.
>
> Simply (and i bet this is the best solution), use a default route pointing
> to .240.241., and use 16.16.1 as default gateway on your office router..
>
> JeF
> On Thu, Oct 24, 2002 at 10:23:55PM +0200, Ángel Carrasco wrote:
> > Ok:
> >
> > My office network is: 172.16.16.0/24 and his IP is: 172.16.16.1.
> > My web network is: 172.16.8.0/24 and his IP is: 172.16.8.1
> > My service network is: 172.16.4.0/24 and his IP is: 172.16.4.1
> > My public network is:213.250.143.240/28 and his IP is: 213.250.143.242.
> >
> > The public router is 213.250.143.241 (and only works with the range
> > 213.250.143.240/28)
> > The office router is 172.16.16.254 (and only works with the range
> > 172.16.16.0/24)
> >
> > The static default route is 172.16.16.254
> >
> > This is my route -n
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 213.250.143.240 0.0.0.0 255.255.255.240 U 0 0 0
> > eth0 172.16.4.0 0.0.0.0 255.255.255.0 U 0 0
> > 0 eth1 172.16.16.0 0.0.0.0 255.255.255.0 U 0 0
> > 0 eth3 172.16.8.0 0.0.0.0 255.255.255.0 U 0 0
> > 0 eth2 0.0.0.0 172.16.16.254 0.0.0.0 UG 0 0
> > 0 eth3
> >
> > And my dinamic route to using the public network is:
> > ip rule add from 213.250.143.242 table publica
> > ip route add from default via 213.250.143.241 dev eth0 table publica
> > ip route flush cache
> >
> >
> > And the problem is when I try to use 213.250.143.242 in my internals
> > networks doesnt run because the information goes by 213.250.143.241 and
> > not
> > in the normal routes.
> >
> > -----Mensaje original-----
> > De: Jeremy C. Reed [mailto:reed@wcug.wwu.edu]
> > Enviado el: jueves, 24 de octubre de 2002 19:01
> > Para: Ángel Carrasco
> > CC: Debian ISP List
> > Asunto: Re: NETWORK ROUTES
> >
> >
> > On Thu, 24 Oct 2002, Ángel Carrasco wrote:
> >
> > > All runs good but my problem is when I try to use the IP of my first
card
> > in
> > > my internals networks
> > > doesn't work because, all information doesn't go by internals
networks, it
> > > goes by the big network.
> >
> > Show us your interface setup and your routes.
> >
> > ifconfig -a
> >
> > route
> >
> >
> > Jeremy C. Reed
> > ....................................................
> > BSD software, documentation, resources, news...
> > http://bsd.reedmedia.net/
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-isp-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmaster@lists.debian.org
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-isp-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
> --
>
> -> Jean-Francois Dive
> --> jef@linuxbe.org
>
> There is no such thing as randomness. Only order of infinite
> complexity. - _The Holographic Universe_, Michael Talbot
>
Reply to: