In article <cl8gb1$18g$1@ctb-nnrp2.saix.net>, Steven Hook wrote:
>
>"Moe Trin" <ibuprofin@painkiller.example.tld> wrote in message
>news:slrncn8nb0.t4s.ibuprofin@atlantis.phx.az.us...
 
[vbcol=seagreen]
>I spoke to my boss about it and he sais he thinks all that routing as
>handeled by the cisco router,

Look at one of the hosts on the LAN _other than_ the host with the
dialin. Does it have a route for packets to use 192.168.10.219 as the
route to 192.168.15.0/24, or is stuff all sent to the CISCO.  A Linux
format routing table should look like this:

Kernel IP routing table
Destination   Gateway        Genmask         Flags Metric Ref  Use Iface
192.168.10.0  0.0.0.0        255.255.255.0   U     0      0  95017 eth0
192.168.15.0  192.168.10.219 255.255.255.0   UG    0      0    240 eth0
127.0.0.0     0.0.0.0        255.0.0.0       U     0      0    420 lo
0.0.0.0       IP.OF.CISCO    0.0.0.0         UG    0      0     55 eth0

when the hosts know how to use the dialin box as gateway back to the
remote hosts, OR it would look like this:

Kernel IP routing table
Destination   Gateway        Genmask         Flags Metric Ref  Use Iface
192.168.10.0  0.0.0.0        255.255.255.0   U     0      0  95017 eth0
127.0.0.0     0.0.0.0        255.0.0.0       U     0      0    420 lo
0.0.0.0       IP.OF.CISCO    0.0.0.0         UG    0      0     55 eth0

if you are depending on the cisco to reroute everything. IF the cisco has
an entry in it's routing table telling how to use 192.168.10.219 as the
route to 192.168.15.0/24, things may work, although you are wasting
bandwidth on the wire and CPU cycles in the CISCO.  If the cisco does
not know how to use 192.168.10.219 as the gateway, then there is no way
for the packets to get back to the dialin host.  The preferred configuration
would be the top one, where each host knows to use 192.168.10.219 as the
route to 192.168.15.0/24.

>I'm not too sure of that myself but all o' this is a bit above my head,
>so I've gotten him to come check it out! I'll fill y'all in on what it was
>when he's fixed it.

In your spare time (yes, I know), grab a copy of the Linux Network
Administrator's Guide. The dead tree version is from O'Reilly as ISBN
1-56592-400-2 (US$40, 506 pgs), but you can also get it as a file from
the Linux Documentation Project (http://tldp.org/guides.html). You
want the nag2, not the earlier 'network-guide'.

./docs/linux-doc-project/nag2:
total 3952
-rw-rw-r-- 1 gferg    ldp        705493 Jan  5  2001 nag2.html.tar.gz
-rw-rw-r-- 1 gferg    ldp       1604859 Feb 27  2001 nag2.pdf
-rw-rw-r-- 1 gferg    ldp       1069355 Feb 27  2001 nag2.ps.gz
-rw-rw-r-- 1 gferg    ldp        635097 Jan  5  2001 nag2.sgml.tar.gz

>Thank you SO much for all the help!

My pleasure!

Old guy

[ Post a follow-up to this message ]