Bill Kenworthy <[EMAIL PROTECTED]> wrote:
> I presume you have masq etc set up? Then try "route" and see what is
> the default gateway device. On my machine, on bootup it could only find
> eth0 (internal), and made that the permanent gateway, and not ppp0, so
> it looped.
>
> BillK
>
<rant mode>
(Blast, I hate Ishmail sometimes! I was 2 words away from finishing
the reply, and got my fingers in the wrong place, and Ishmail DUMPED
everything! Crud crud crud! Oh, well, here goes again)
</rant mode>
I finally got the time to try and see if the linux box was correctly
routing, and it appears to be fine, as I can ping the linux router's
ethernet card just fine from a dialin client (also linux ;-).
Or, put another way, I have verified that packets from the linux
RAS can travel from the RAS client to the (windows-only) network
segment, but that no reply comes back.
Add that to the fact that, when the windows machine I'm trying to
reach (at, for example, 172.27.4.1) does the following:
c:\windows> ping 172.27.5.1
Pinging 172.27.5.1 with 32 bytes of data:
Reply from 157.130.224.69: Destination host unreachable.
Request timed out.
That pretty much says to me that I need to tell the windows machines
about the new route.
So, how do I do that?
(I'd like to do it 'automatically' and not have to manually set the
routing tables in the windows machines!)
rc
Rusty Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
Voice: (480) 345-3621 SnailMail: Schlumberger ATE
FAX: (480) 345-8793 7855 S. River Parkway, Suite 116
Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825
