Thanks for the information on fixing my minor problem.
I went back and had a look at the /etc/resolv.conf
file, it look something like this:
search peregian
nameserver 192.168.0.1
peregian and ip address is the name I gave to the
D-Link 624 router wireless access point.
I edited the
I have a triple booting machine (Windows, Redhat and
Debian) box.
Lately I installed a Netcomm 1300 adsl/router and a
D-Link DI-614 access point/router.
With Windows and Redhat I have no problem accessing
the internet, and the configuration the modem and the
access point.
But the real problem
On Tue, Sep 30, 2003 at 12:59:37AM -0700, Craig wrote:
But the real problem is the routing with debian, I can
ping the adsl/router modem but cannot ping either a
internet site or the DI-624 access point/router.
Does cannot ping mean that your dns lookup fails, there's no response to
the ping,
- Original Message -
From: Craig [EMAIL PROTECTED]
Any suggestions?
send us your /etc/network/interfaces file.
and /etc/resolv.conf
those two files should an internet connection make
dave
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info:
Craig wrote:
But the real problem is the routing with debian, I can
ping the adsl/router modem but cannot ping either a
internet site or the DI-624 access point/router.
ping www.some.com.au ? OR ping 192.168.x.y ?
If former, try later to check that it is not a dns issue.
If later, try
At Fri, 26 Jul 2002 10:14:34 +1000, Alan L Tyree wrote:
what does /etc/nsswitch.conf say?
bigdog:
hosts: files nisplus nis dns
sage:
hosts: files dns dns
(assuming you aren't actually using nis)
try something like this:
hosts: files [SUCCESS=return] dns
(you will
On Fri, 2002-07-26 at 08:59, Alan L Tyree wrote:
All of this seems to me to suggest a problem with ssh configuation
rather than a routing problem.
Try running your ssh server in the foreground and in debug mode. This
will give you a good trace of what's going on. It could be something
At Wed, 24 Jul 2002 16:36:48 +1000, John Ferlito wrote:
kermit:/usr/src# hostname -s kermit kermit:/usr/src# hostname -d
inodes.org kermit:/usr/src# hostname -f kermit.inodes.org
kermit:/usr/src#
the domains comes from etc/hosts in etc/hosts you should have
192.168.1.x kermit.inodes.org kermit
Thanks to everybody that replied on this. None of the suggestions have
fixed the problem yet, but I have more information.
Recall the problem was:
sage -- bigdog -- ISP
When bigdog is *not* connected, ssh takes about 45 seconds to
connect. When bigdog is connected, connection is quick.
On Fri, 2002-07-26 at 08:59, Alan L Tyree wrote:
ssh -v -v bigdog: shows that the system hangs for most of the 45
seconds on the line
ssh_connect: getuid 500 getuid 0 anon 1
SSH is trying to resolve the computer name from the IP on the incoming
side. It is hitting DNS and not
what does /etc/nsswitch.conf say?
- Original Message -
From: Alan L Tyree [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, July 26, 2002 9:23 AM
Subject: Re: [SLUG] Routing problem (I think)
SNIP
On all machines:
/etc/hosts:
127.0.0.1 localhost
ssh -v -v bigdog: shows that the system hangs for most of the 45
seconds on the line
ssh_connect: getuid 500 getuid 0 anon 1
All of this seems to me to suggest a problem with ssh configuation
rather than a routing problem.
There is also an option to the ssh server that will display what
what does /etc/nsswitch.conf say?
SNIP
Hmmm:
bigdog:
hosts: files nisplus nis dns
sage:
hosts: files dns dns
--
--
Alan L Tyree[EMAIL PROTECTED]
http://www.law.usyd.edu.au/~alant
Tel: +61 2 4782 2670
Mobile: +61 419
Do you have bigdog in your /etc/hosts file on sage?
/etc/hosts on sage should look something like this
127.0.0.1 localhost
192.168.1.1 biogdog.my.home bigdog
{assuming bigdog's IP address is 192.168.1.1, of course}
Yep. On all machines.
The only thing that I have
On Wed, Jul 24, 2002 at 04:27:54PM +1000, Alan L Tyree wrote:
Do you have bigdog in your /etc/hosts file on sage?
/etc/hosts on sage should look something like this
127.0.0.1 localhost
192.168.1.1biogdog.my.home bigdog
{assuming bigdog's IP address is
The only thing that I have noticed that is strange is:
[alant@sage alant]$ domainname
(none)
[alant@sage alant]$ hostname
sage.my.home
The command domainname refers to a NIS domain, not the DNS command. The
hostname command is what you want and is given the correct info.
What
Hi,
The only thing that I have noticed that is strange is:
[alant@sage alant]$ domainname
(none)
The man page says that this command is used to set the NIS/YP domain
name. You might want to check out the dnsdomainname command..
Cheers,
Matt.
--
SLUG - Sydney Linux User's Group -
On Wed, Jul 24, 2002 at 04:27:54PM +1000, Alan L Tyree wrote:
Do you have bigdog in your /etc/hosts file on sage?
/etc/hosts on sage should look something like this
127.0.0.1 localhost
192.168.1.1 biogdog.my.home bigdog
{assuming bigdog's IP
Hi,
The only thing that I have noticed that is strange is:
[alant@sage alant]$ domainname
(none)
The man page says that this command is used to set the NIS/YP domain
name. You might want to check out the dnsdomainname command..
Cheers,
Matt.
Right. I hadn't noticed that. And
The only thing that I have noticed that is strange is:
[alant@sage alant]$ domainname
(none)
[alant@sage alant]$ hostname
sage.my.home
The command domainname refers to a NIS domain, not the DNS command. The
hostname command is what you want and is given the correct
On Wed, 24 Jul 2002, Alan L Tyree wrote:
I am pretty new to networking. I have three machines. One, bigdog, is
acting as a gateway/firewall.
I am working from sage. The routing table is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
I am pretty new to networking. I have three machines. One, bigdog, is
acting as a gateway/firewall.
I am working from sage. The routing table is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.1.0 * 255.255.255.0
On Wed, 2002-07-24 at 08:56, Alan L Tyree wrote:
I am pretty new to networking. I have three machines. One, bigdog, is
acting as a gateway/firewall.
I am working from sage. The routing table is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Snip
I presume that there is an attempt to do a DNS lookup. My host.conf
file specifies:
order hosts, bind
Sounds a reasonable assumption. To test it, put an entry in /etc/hosts
for the machine you're ssh'ing from.
Not sure I understand. My present hosts file is:
# Do not remove
On Wed, 2002-07-24 at 09:21, Alan L Tyree wrote:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.1.1 sage.my.homesage
192.168.1.2 bigdog.my.home bigdog
192.168.1.3
On Wed, 24 Jul 2002, Alan L Tyree wrote:
Not sure I understand. My present hosts file is:
snip
Shouldn't that do the trick?
As long as it's on both machines, I would have thought so.
Assuming, of course, that DNS _is_ the problem.
-- Jessica Mayo.
(Everything with a Grin :)
--
SLUG - Sydney
in the foreground
then from your other box, ssh to this other box and see what sshd spits out.
HTH
Chris
-Original Message-
From: Tony Green [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 24 July 2002 9:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [SLUG] Routing problem (I think)
On Wed, 2002-07-24
On Wed, 24 Jul 2002, Alan L Tyree wrote:
I am pretty new to networking. I have three machines. One, bigdog, is
acting as a gateway/firewall.
I am working from sage. The routing table is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
I know you've solved this another way but you might be interested in
knowing why it worked out that way.
I've answered this by inserting lines with [G]
On Mon, 24 Sep 2001, Tom Massey wrote:
Hi all.
I'm having some difficulty with routing under Red Hat 7. Basic situation:
Me and few
On Tue, Sep 25, 2001 at 07:43:37PM +1000, Grant Parnell wrote:
I know you've solved this another way but you might be interested in
knowing why it worked out that way.
I've answered this by inserting lines with [G]
Thanks for the info, interesting stuff. Would you believe that the problem
Thanks for the suggestions to put things onto separate subnets. This seems to
be the answer (haven't been able to change things yet, all the machines are
actually in the US and I haven't got in touch with the guy who has physical
access). I can only assume that the setup worked originally because
That made sense before your box was rebooted: you had host addresses
pointing to the interfaces and only one network address for another nic,
which is correct, after reboot, the kernel added the route for the network
when the card went up..
JeF
On Mon, 24 Sep 2001, Tom Massey wrote:
Thanks
Hi all.
I'm having some difficulty with routing under Red Hat 7. Basic situation:
Me and few friends have a machine running RH7 that we're playing with
networking stuff on, different configurations just for the hell of it
basically. At the moment the machine contains 4 NICs - eth0 to a cable
Hi,
As soon as you assigned a netwotk to a NIC, it's entry is automatically
addes to the routing table. I dont get why you assigne the same network
addresses to different interface (routing wont be easy for the box :)
What you have to to is to change the addresses on eth2/3/1 to have
separate
On Thu, Feb 01, 2001 at 11:47:12PM +1100, David Kempe wrote:
Actually now i dig into it, that address space is owned by SUN.
That may be the cause of the problem then
hrmmm would that be right?
No.
The boxes with the 192.9 addresses won't be able to get to
the real 192.9 addresses that
Hey sluggers,
I have a strange routing problem atm and am wanting a few pointers.
Lets say the machine in question has 5 NICs connected to 5 subnets. Also a
modem. Thats 6 interfaces in total.
Now everything seems normal in ifconfig and route. All the routes are there,
the subnet masks are normal
Actually now i dig into it, that address space is owned by SUN.
That may be the cause of the problem then
hrmmm would that be right?
dave@sumo:~$ whois 192.9.0.0
Sun Microsystems, Inc (NETBLK-SUN)
Mail Stop UNWK14-301 901 San Antonio Road
Palo Alto, CA 94303
US
Netname: SMI-NETS
something silly, I just can't
see it...hence the request for help.
alister
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Jeff Waugh
Sent: Monday, 16 October 2000 3:37 PM
To: [EMAIL PROTECTED]
Subject: Re: [SLUG] Routing problem...perhaps
Alister
Alister Waller said something along the lines of:
Surely that would be on the Linux machine that the other linux machine dials
into...on machine R in my example below.
The proxyarp setting is required on the gateway, not the remote machine.
man pppd reads thus:
proxyarp
Alister Waller said something along the lines of:
R:can ping G's ppp IP address
cannot ping G's eth0 IP address.error: destination host unreachable
cannot ping W at all. error: destination host unreachable
G:can ping W's IP address
Can ping G's
40 matches
Mail list logo
