From: maxim wexler <blissfix@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems with domainname
Date: Sat, 25 Mar 2006 18:57:10 -0800 (PST) [thread overview]
Message-ID: <20060326025710.14200.qmail@web31705.mail.mud.yahoo.com> (raw)
In-Reply-To: <20060325233937.GA12861@waltdnes.org>
--- Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Sat, Mar 25, 2006 at 02:11:01PM -0800, maxim
> wexler wrote
>
> > So both PCs have that line in their /hosts file
> now.
> > So I oughta be able to ftp gravity from one or the
> > other and get connected, right? But it doesn't
> work
> > :^(
> >
> > Does ftp work for you?
>
> There are several places where things can go
> wrong. Here are some
> boobytraps that I've found out about "the hard way".
> Put it this
> way... doing things right comes from experience...
> "experience" comes
> from doing things wrong<g>.
>
> - are you sure you're running ftpd on the target
> machine?
Well top and ps list ftp without the 'd' on the end
as running. And ftp starts with the ftp> prompt. If
that's what you mean.
>
> - check the logs on both machines to ensure that
> neither one is
> rejecting packets from the other by iptables
> rules
Nothing in the logs. Maybe I need a LAN specific
logger? All I got is syslog-ng on both machines.
There is this, which is identical on both machines
with different numbers of course:
sarawak heathen # tcpdump -v
tcpdump: listening on eth0, link-type EN10MB
(Ethernet), capture size 96 bytes
19:44:10.942027 arp who-has 192.168.0.3 tell
gravity.twi-31o2.org
19:44:12.515686 arp reply 192.168.0.3 is-at
00:e0:18:99:88:77 (oui Unknown)
19:44:10.942092 IP (tos 0x0, ttl 64, id 38827, offset
0, flags [DF], proto: TCP (6), length: 60)
gravity.twi-31o2.org.53486 > 192.168.0.3.ftp: S, cksum
0xa947 (correct), 3719721500:3719721500(0) win 5840
<mss 1460,sackOK,timestamp 648631 0,nop,wscale 2>
19:44:10.942110 IP (tos 0x0, ttl 64, id 127, offset
0, flags [DF], proto: TCP (6), length: 40)
192.168.0.3.ftp > gravity.twi-31o2.org.53486: R, cksum
0x0da3 (correct), 0:0(0) ack 3719721501 win 0
19:44:15.940760 arp who-has gravity.twi-31o2.org tell
192.168.0.3
19:44:15.940877 arp reply gravity.twi-31o2.org is-at
00:04:75:8a:cf:84 (oui Unknown)
You'll notice that last number *is* the hardware
address on the remote machine(see below). So there has
been some sort of communication between the two but
then it shuts off.
>
> - post the output of "grep -v ^# /etc/hosts" and
> "ifconfig eth0" and
> "route -n" from both machines
------------K6-2.6.15----------------------
lumberton ~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr
00:04:75:8A:CF:84
inet addr:192.168.0.2 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:10 errors:0 dropped:0 overruns:0
frame:0
TX packets:11 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:614 (614.0 b) TX bytes:702 (702.0
b)
Interrupt:9 Base address:0x4f80
lumberton ~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags
Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U
0 0 0 eth0
127.0.0.0 127.0.0.1 255.0.0.0 UG
0 0 0 lo
lumberton ~ # grep -v ^# /etc/hosts
127.0.0.1 localhost
192.168.0.3 gravity.twi-31o2.org gravity
lumberton ~ # emerge -pv ftp
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] net-ftp/ftp-0.17-r6 +ipv6 +ssl 0 kB
Total size of downloads: 0 kB
----------------Sempron-2.6.12------------------------
sarawak heathen # ifconfig eth0
eth0 Link encap:Ethernet HWaddr
00:E0:18:99:88:77
inet addr:192.168.0.3 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:19 errors:0 dropped:0 overruns:0
frame:0
TX packets:19 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:1182 (1.1 Kb) TX bytes:994 (994.0
b)
Interrupt:11 Base address:0x2000
sarawak heathen # route -n
Kernel IP routing table
Destination Gateway Genmask Flags
Metric Ref Use Iface
64.228.98.241 0.0.0.0 255.255.255.255 UH
0 0 0 ppp0
192.168.0.0 0.0.0.0 255.255.255.0 U
0 0 0 eth0
127.0.0.0 127.0.0.1 255.0.0.0 UG
0 0 0 lo
0.0.0.0 64.228.98.241 0.0.0.0 UG
0 0 0 ppp0
sarawak heathen # grep -v ^# /etc/hosts
127.0.0.1 sarawak localhost
192.168.0.2 gravity.twi-31o2.org gravity
::1 ip6-localhost ip6-loopback #hmm,
fe00::0 ip6-localnet #more
ff00::0 ip6-mcastprefix #stuff
ff02::1 ip6-allnodes #here
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
sarawak heathen # emerge -pv ftp
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] net-ftp/ftp-0.17-r6 +ipv6 +ssl 0 kB
Total size of downloads: 0 kB
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-26 3:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 4:16 [gentoo-user] Problems with domainname Felipe Ribeiro
2006-03-19 5:43 ` scwang
2006-03-19 15:11 ` JimD
2006-03-19 16:58 ` Felipe Ribeiro
2006-03-24 20:19 ` THUFIR HAWAT
2006-03-25 22:11 ` maxim wexler
2006-03-25 23:39 ` Walter Dnes
2006-03-26 2:57 ` maxim wexler [this message]
2006-03-26 3:49 ` Ryan Tandy
2006-03-26 21:00 ` maxim wexler
2006-03-26 5:09 ` Walter Dnes
2006-03-26 22:05 ` maxim wexler
2006-03-27 4:50 ` Walter Dnes
2006-03-28 3:04 ` maxim wexler
2006-03-29 6:12 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060326025710.14200.qmail@web31705.mail.mud.yahoo.com \
--to=blissfix@yahoo.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox