Subject: Re: Wierd routing problem....
From: John Nelson (john@computation.com)
Date: Sun Jan 06 2002 - 20:38:56 MST
Subject:
Re: Wierd routing problem....
From:
John Nelson <john@computation.com>
Date:
Sun, 6 Jan 2002 21:23:35 -0500 (EST)
To:
<yellowdog-general@lists.yellowdoglinux.com>
Avinash,
I'm using 7.1 on both server and clients. The IP for the DNS server is in
resolv.conf. I'm not using NAT (I haven't done anything special to
configure or enable NAT). The server is directly connected to the
Internet.
Do I need a route that bridges PPP and ETH0 and wouldn't that be done
automatically by PPP?
As for telnet server, I believe that I installed that. That's a good
point though and I'll recheck all the xinitd setups. Also, outgoing
traffic from YDL doesn't see domain names. All the clients are afflicted
with that problem.
-- John
On Sun, 6 Jan 2002, Avinash Gupta wrote:
>> Date: Sun, 6 Jan 2002 09:40:36 -0500
>> From: Avinash Gupta <agupta@mediaone.net>
>> Reply-To: yellowdog-general@lists.yellowdoglinux.com
>> To: yellowdog-general@lists.yellowdoglinux.com
>> Subject: Re: Wierd routing problem....
>>
>> Have you put your DNS servers in /etc/resolv.conf for the client machines (or
>> maybe you are using DHCP)? Also, what is your network configuration i.e. are
>> you using NAT? What machine is directly connected to the internet?
>>
>> The telnet server is not installed by default on YDL machines (security
>> vulnerabilities). If you still want it, refer to the link below:
>>
>> http://lists.yellowdoglinux.com/yellowdog-updates/August01/0027.html
>>
>> You may want to try ssh instead of telnet ... it's much more secure.
>>
>> -- Avinash Gupta (agupta@mediaone.net)
>>
>>
>> On Sunday 06 January 2002 01:31, you wrote:
>
>>> > Ooopps... maybe I'll be keeping the monitor and keyboard for a while.
>>> > I'm trying to telnet into the YDL machine gunanine from my DNS server and
>>> > the YDL machine claims the following:
>>> >
>>> > [root@adenine ~]# telnet guanine
>>> > Trying 192.168.0.24...
>>> > telnet: connect to address 192.168.0.24: No route to host
>>> >
>>> > Now that's wierd because the server (adenine) has the following route
>>> > table, which does seem to define a route to any machine on my internal
>>> > network 192.168.0.*...
>>> >
>>> > [root@adenine john]# route
>>> > Kernel IP routing table
>>> > Destination Gateway Genmask Flags Metric Ref Use
>>> > Iface 168.121.1.1 * 255.255.255.255 UH 0 0
>>> > 0 ppp0 192.168.0.0 * 255.255.255.0 U 0 0
>>> > 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0
>>> > 0 lo default 168.121.1.1 0.0.0.0 UG 0 0
>>> > 0 ppp0
>>> >
>>> > There is unfortunately an additional problem getting to the Internet from
>>> > client machines through this server. Although the server can resolve
>>> > names, none of the clients are able to get to Internet domains (e.g.
>>> > dell.com). AIM is also unable to get to the Internet from the clients.
>>> >
>>> > Sigh... any ideas? Oh... ipchains is turned off.
>>> >
>>> > -- John
>>
This archive was generated by hypermail 2a24 : Sun Jan 06 2002 - 20:53:17 MST