[plug] Still not able to route to adsl

raven at themaw.net raven at themaw.net
Sun May 2 13:41:42 WST 2004


On Sun, 2 May 2004, bob wrote:

> On Sunday 02 May 2004 11:28, raven at themaw.net wrote:
> > On Sun, 2 May 2004, bob wrote:
> > > On Sunday 02 May 2004 00:27, raven at themaw.net wrote:
> > > > What is in the routing table in the NB?
> > >
> > > Route Table
> > >
> > > Destination	Netmask	Gateway	Interface
> > > 0.0.0.0	0.0.0.0	202.72.191.x	ppp1
> > > 192.168.0.0	255.255.255.0	192.168.1.x	br0
> > > 192.168.0.x	255.255.255.255	192.168.1.x	br0
> > > 192.168.1.0	255.255.255.0	192.168.1.1	br0
> > > 192.168.1.x	255.255.255.255	192.168.1.1	br0
> > > 127.0.0.1	255.0.0.0	127.0.0.1	lo0
> > > 202.72.191.x	255.255.255.255	202.72.133.x	ppp1
> >
> > So anything destined for 192.168.[01] networks is sent to br0.
> > And anything else goes to ppp1. Except packets destined for 127.0.0.1.
> >
> > Correct?
> 
> Yes. (for certain values of yes :)

I've still got a problem understanding what this routing table does.

Why are there a routes to 192.168.1. The NB belongs to that network right?
It looks like anything going to 192.168.1.x is being sent to 192.168.1.1, 
the NB ?????

I'm not sure you need those routes at all. 192.168.1 is a directly 
connected network. ARP rules there.

> 
> > And you are NATing "only" on the NB1300 at this point in your
> > investigation right?
> 
> Currently both the ADSL is NATing, however I have tried having one or the 
> other do the job without too much luck. (even had both NATing at one point)
> 
> > > Manually Configured Routes
> > >
> > > #	Destination	Netmask	Gateway
> > > 1	192.168.0.x	255.255.255.255	192.168.1.x
> > > 2	192.168.0.0	255.255.255.0	192.168.1.x
> > > 3	192.168.1.x	255.255.255.255	192.168.1.1
> > >
> > > (All 192.168.1.x are the same addr)
> >
> > Why have you got host routes here at all.
> 
> Umm... belt and braces :).
> 
> > Why have these routes been repeated. They are in the route table above.
> 
> I think the " Manually Configured Routes" just indicates what has be hand 
> set. When you hit "add" the new route appears in the main routing table as 
> well as the manual config
> 
> > So what is the setup of the Gateway/firewall or was that it above and
> > I've misunderstood?
> 
> No, you are correct. The above is for the NB1300 
> 
> The Gateway/Firewall has this routing when I try using the ADSL as the 
> default route
> 
> Kernel IP routing table
> Destination     Gateway         Genmask       Flags Metric Ref    Use Iface
> fetch           *               255.255.255.255 UH    0      0        0 eth1
> adslnet         *               255.255.255.0   U     0      0        0 eth1
> localnet        *               255.255.255.0   U     0      0        0 eth0
> default         fetch    0.0.0.0         UG    0      0        0 eth1
> 
> fetch is the ADSL dev 192.168.1.1
> adslnet is 192.168.1/24
> localnet is 192.168.0/24
> 
> localnet hosts have default routes pointing to the Gateway/Firewall's eth0 
> IP#

So.

anything destined for localnet goes out eth0.
anything destined for adslnet goes out eth1.
everything else goes out eth1.

Looks OK.

Ian




More information about the plug mailing list