LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Network 2 computers with crossover cable uisng IPv6 (https://www.linuxquestions.org/questions/linux-networking-3/network-2-computers-with-crossover-cable-uisng-ipv6-389448/)

q14526 12-05-2005 09:39 AM
Network 2 computers with crossover cable uisng IPv6
 
Hi,
I am new to networking, my work project is to test and learn about IPv6, I have to connect 2 computers via crossover cable and perform ftp and telnet from one to the other using IPv6.
Yes, I have search and read all about IPv6 on google and this forum for the last 2 weeks.
I set up 2 PCs with Fedora 4.

1. AS a start up, using the Newbie's Guide To Small Home LAN (it is fantastic! guide)I can ping and ftp between 2 PCs but was not be able to telnet (using IPv4)(Error: connection refused). Can someone tell me what I am missing ?

2. My real need is setup so that it is using IPv6 standard.
Is there equivalent of address 192.168.xxx.xxx in IPv6 as in IPv4 ?

if "ech077" (author of the Newbie's guide to small home LAN) can add to his IPv4 guide that would be a very educational publication for every newbie in the world.

Can some one please tell me how to network 2 computers with crossover cable using IPv6?
:confused:
Thank you all for your time.

cuiq 12-05-2005 10:20 AM
Here's the tut. Which by the way is located in the tutorial section of this very site.

http://www.linuxquestions.org/linux/...Small_Home_LAN

There are others listed under networking for your further perusal.



Peace V

q14526 12-05-2005 12:44 PM
Hi cuiq,
Thank for the reply. But as I said I've already read and used this guide (and many many more articles). This guide is only for IPv4. I need help to do the same thing for IPv6.
I appreciate your reply. Please give help on IPv6.

Thanks.

cuiq 12-05-2005 01:44 PM
Sorry :o for not reading your post throughly.

cuiq 12-05-2005 01:57 PM
found this book, which does not seem to list a difference in setup between ipv4 ipv6 other than that ipv6 became available in the 2.4 kernel and above.

"6. Kernel configuration
6.1. If using iptables

Iptables is actually a user interface tool and depends on the kernel implementation called netfilter. Netfilter includes support only for IPv4 and IPv6, and does not filter any other protocols. Hence if your system should run something like IPX, remember that the protocols other than IPv4 and IPv5 are not going to be filtered according to the iptables rules. User kerne 2.4.18 or above, if possible to have all the new features of netfilter.

Install the iptables software on your system (apt-get install iptables). Once you know that your kernel is configured with netfilter support, you need not worry about it at all. Just remember that iptables need the kernel support from netfilter.

Check if your kernel is configured for supporting iptables. Though most distributions include this support by default, do this quick test as root.

bash# modprobe ip_tables
bash# lsmod | grep ip_tables

If any of the above commands give an error or ip_tables doesn't show up in module listing, you must enable these options in the kernel configuration using make menuconfig or make xmenuconfig

*

Code maturity-level options for development and/or incomplete code/drivers
*

Network packet filtering in Networking options.
*

IP: Netfilter Configuration iin Networking options

select all these options as modules."


http://newbiedoc.sourceforge.net/net...CONFIGIPTABLES


Peace V

q14526 12-06-2005 08:44 AM
Network 2 PCs using crossover cable for IPv6
 
Hi cuiq,

Once again I appreciate your response.
Yes, I do have ip_tables module running. But I am not sure what I have to do with it.
Here is what I have done so far (all PCs instaled with FC4 Server, all options):
PC#1: inet 192.168.10.1 brd 192.168.10.255 scope global eth0:1
inet6 2001::c0a8:a01/64 scope global
inet6 fec0::c0a8:a01/64 scope site
inet6 fe80::2d0:b7ff:fe58:6bb6/64 scope link

PC#2: inet 192.168.10.2 brd 192.168.10.255 scope global eth0:1
inet6 2001::c0a8:a02/64 scope global
inet6 fec0::c0a8:a02/64 scope site
inet6 fe80::2d0:b7ff:fe57:eca0/64 scope link

1. The inet addresses is setup for crossover cable using IPv4: ping and ftp work but NOT telnet
with error "connection refused". Do you know why?
2. The inet6 local link addresses which begin with fe80 are setup by FC4: ping6 works but ftp and
telnet NOT work (error: unknown host and connection refused respectedly)
3. The inet6 local site addresses which begin with fec0 are added by me: ping6 works but ftp and
telnet NOT work (error: unknown host and connection refused respectedly)
4. The inet6 local global addresses which begin with 2001 are added by me: ping6 works but ftp
and telnet NOT work (error: unknown host and connection refused respectedly)

So I have all types of IPv6 addresses exist (or added to)in my setup but only ping6 is working. Could you please tell me what I am missing.

Is there any way I can get in touch with ech077 (author of the Newbie's guide to small home LAN)?

Best regards.

cuiq 12-06-2005 10:12 AM
echo77 can be reached at

neenad AT gmail dot com

This is in the "CONTACT ME" section of the tutorial.

Peace V

q14526 12-06-2005 03:19 PM
Hi cuiq,
I hope that my request to contact with echo77 did not offend you. I am desperate to do my work.
I apologize for that inappropriate question. I have not send him/her any email yet.

I have solved one issue: telnet from PC1 to PC2 using IPv4
FC4 installation did not install telnet-server.rpm and xinetd.rpm
These 2 RPMs must be downloaded from rpmfind.net and run rpm command.
Then I must edit /etc/xinetd.d/telnet: set disable = NO
and edit /etc/xinetd.d/eklogin: set disable = YES
and then restart xinetd. Now I can telnet from one to the other system (IPv4 only).

Now I will have to do more reading on how to do the same with IPv6 over crossover cable.
I suspect it have something to do with the first 2 byte block of the IPv6 (either global or site) address (as 192.168.xxx.xxx in IPv4).

Once again, I apologize for my question. Please help me if you can.

Best regards.

jcliburn 12-06-2005 09:33 PM
Try ssh.

ssh -6 <ipv6 address>

If this doesn't work, pick a machine (doesn't matter which one) and as root, edit /etc/radvd.conf. Make it look something like this.

Code:
interface eth0
{
        AdvSendAdvert on;
        MinRtrAdvInterval 30;
        MaxRtrAdvInterval 100;
        prefix fec0::/64
        {
                AdvOnLink on;
                AdvAutonomous on;
                AdvRouterAddr on;
        };

};
Then execute
Code:
# radvd -d 4 &
Your hosts should autoconfigure with IPv6 site-local (fec0::/64) addresses. Then try ssh -6.

jcliburn 12-07-2005 02:03 PM
I forgot to mention that I don't think the Fedora version of telnetd (telnet-server-0.17-35.i386.rpm) is IPv6 compatible. However, vsftpd (vsftpd-2.0.3-1.i386.rpm) *is* IPv6 compatible, at least if run outside xinetd. I haven't been successful running it inside xinetd, but I haven't tried very hard either.

As you can see below, I start telnetd and vsftpd, then use netstat to view listening ports. telnetd is listening for an IPv4 (only) connection, while vsftpd (and sshd) are listening for IPv6 connections.

Code:
[root@petrel local]# /usr/sbin/in.telnetd -debug &
[1] 9378
[root@petrel local]# /usr/sbin/vsftpd &
[2] 9379
[root@petrel local]# netstat --protocol=inet,inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address              Foreign Address            State      PID/Program name
tcp        0      0 0.0.0.0:23                  0.0.0.0:*                  LISTEN      9378/in.telnetd
tcp        0      0 :::21                      :::*                        LISTEN      9379/vsftpd
tcp        0      0 :::22                      :::*                        LISTEN      1790/sshd
1709/portmap

q14526 12-07-2005 02:05 PM
Hi jcliburn,
The ssh -6 <ipv6Addr> command works. There seems to be a disconnection between the Network Configuration GUI and setting IP address in a console.

In a console, we can just add an address using "ip -6 addr add feco::x:y:z" and never have to enter subnet mask.

I have tried to use Network Configuration GUI, create a new device profile with address fec0::c0a8:a01 (with or without /64) and subnet mask is ffff:ffff:ffff:ffff:0000:0000:0000:0000, when I activate that profile, it fails because subnet mask is wrong and error: some other host already uses this address(no other profile is activated). I have played around this device profile setting all this morning but can not get to a good understanding of this network configuration tool.

My questions are:
1. Should I install radvd anyway ? (FC4 did not installed it)
2. Should I just add ipv6 address using console and ignore the Network Configuration GUI which is activated for ipv4 device address 198.162.10.x ?
3. What is the correct subnet mask for fec0::c0a8:a0x/64 (crossover cable)?

Thank you very much for you help.

Best regards.

jcliburn 12-07-2005 02:37 PM
The easiest thing to do is install and run radvd, that way you don't have to worry about manually configuring your interfaces.

I've never tried to use the NetworkManager GUI for configuring IPv6 addresses, so I can't help you there.

For site-local addresses (fec0/10), I think the subnet mask *might* be 0000:0000:0000:ffff:0000:0000:0000:0000 (according to _Unix Network Programming, Volume 1, 3rd edition_ at page 881), but again, I use autoconfiguration and don't (thus far) have to worry about subnet masks.

cuiq 12-07-2005 05:55 PM
I'm not offended. This forum is about getting and receiving help. If I can't help you, then I should be willing to direct you to the help you need.

I hope the others were able to help you resolve your issue.



Peace V

q14526 12-09-2005 02:53 PM
Hi jcliburn and cuiq,
I have done as you said:
1. Installed and run radvd and use the GUI just to deactivate/activate one of the 2 device profile (either DHCP to my work network or using crossover cable for my IPv6 experiment).
2. I also install and run vsftpd-2.0.3-1.i386.rpm

Here is my "netstat --protocol=inet, inet6 -pnl" screen log:
---------------------------------------------------------------------------------
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 1441/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1423/portmap
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 31695/vsftpd
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 13690/xinetd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 9901/cupsd
tcp 0 0 127.0.0.1:5335 0.0.0.0:* LISTEN 1726/mDNSResponder
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1841/sendmail: acce
tcp 0 0 :::22 :::* LISTEN 1809/sshd
udp 0 0 0.0.0.0:32768 0.0.0.0:* 1441/rpc.statd
udp 0 0 0.0.0.0:769 0.0.0.0:* 1441/rpc.statd
udp 0 0 0.0.0.0:68 0.0.0.0:* 31511/dhclient
udp 110400 0 0.0.0.0:5353 0.0.0.0:* 1726/mDNSResponder
udp 0 0 0.0.0.0:111 0.0.0.0:* 1423/portmap
udp 0 0 0.0.0.0:631 0.0.0.0:* 9901/cupsd
---------------------------------------------------------------------------------

and here is my ip addr show:

---------------------------------------------------------------------------------
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:d0:b7:57:ec:a0 brd ff:ff:ff:ff:ff:ff
inet 13.231.135.18/22 brd 13.231.135.255 scope global eth0
inet 192.168.10.1/24 brd 192.168.10.255 scope global eth0:1
inet6 fec0::c0a8:a01/64 scope site
valid_lft forever preferred_lft forever
inet6 fe80::2d0:b7ff:fe57:eca0/64 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
---------------------------------------------------------------------------------

So far only ssh is working with IPv6 "fec0" address.
Questions:
1. From the netstat log, why only sshd listen to IPv6 address (double colon)?
Your vsftpd does but why my vsftpd does not ? It is the same release as you said. What did I do wrong
2. Is that true that Fedora telnet-0.17-35 and telnet-server-0.17-35 will not work with IPv6 ?
3. Run /usr/sbin/in.telnetd & ---> error= bind:Address already in use -> Exit 1
4. Run /usr/sbin/vsftpd & ---> error=500 OPPS: could not bind listening IPv4 socket

So many things are not working, what should I do. Please help.

Best regards.

jcliburn 12-09-2005 07:02 PM
Okay, I can't get vsftpd to work within xinetd; I get the same error you do. However, I can get it to work standalone, which is the recommended method in the vsftpd manpage.

To run vsftpd as a standalone daemon, add the following line to the bottom of /etc/vsftpd.conf

listen=YES

Then start vsftpd from the command line

vsftpd &

Now for telnetd, I can't get it to work standalone, but I can get it to work IPv6 within xinetd. (Go figure...)

Make your /etc/xinetd.d/telnet file look like this
Code:
service telnet
{
        flags          = IPv6
        socket_type    = stream
        wait            = no
        user            = root
        server          = /usr/sbin/in.telnetd
        log_on_failure  += USERID
        disable        = no
}
Then execute

/sbin/service xinetd restart

Hope this helps.

Here's my output from the server (hostname petrel).

Code:
[root@petrel ~]# netstat --proto=inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address              Foreign Address            State      PID/Program name
tcp        0      0 :::21                      :::*                        LISTEN      3344/vsftpd
tcp        0      0 :::22                      :::*                        LISTEN      1628/sshd
tcp        0      0 :::23                      :::*                        LISTEN      3006/xinetd

[root@petrel ~]# /sbin/ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:B0:D0:82:6D:DA
          inet addr:192.168.1.6  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fec0::2b0:d0ff:fe82:6dda/64 Scope:Site
          inet6 addr: fe80::2b0:d0ff:fe82:6dda/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9505 errors:0 dropped:0 overruns:1 frame:0
          TX packets:6050 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:891381 (870.4 KiB)  TX bytes:1304916 (1.2 MiB)
          Interrupt:5 Base address:0xec80
Here's some sample sessions from the client (hostname osprey).

Code:
[jcliburn@osprey ~]$ telnet fec0::2b0:d0ff:fe82:6dda
Trying fec0::2b0:d0ff:fe82:6dda...
Connected to fec0::2b0:d0ff:fe82:6dda.
Escape character is '^]'.
Fedora Core release 4 (Stentz)
Kernel 2.6.14-1.1644_FC4 on an i686
login: jcliburn
Password:
Last login: Fri Dec  9 18:50:11 from 0.0.0.0
[jcliburn@petrel ~]$

[jcliburn@osprey ~]$ ftp fec0::2b0:d0ff:fe82:6dda
Connected to fec0::2b0:d0ff:fe82:6dda (fec0::2b0:d0ff:fe82:6dda).
220 (vsFTPd 2.0.3)
Name (fec0::2b0:d0ff:fe82:6dda:jcliburn):
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bye
221 Goodbye.
[jcliburn@osprey ~]$

jcliburn 12-09-2005 08:02 PM
I found the solution to the vsftpd OOPS. Turns out there are two vsftpd.conf files: one in /etc and another in /etc/vsftpd. Try this.

Code:
mv /etc/vsftpd.conf /etc/vsftpd.conf.orig
Then edit /etc/vsftpd/vsftpd.conf and comment out the last two lines. (You can probably leave the tcp_wrappers line if you've got tcp_wrappers configured correctly.)

Code:
#listen_ipv6=YES
#tcp_wrappers=YES
Next, edit /etc/xinetd.d/vsftpd and make it look like this.

Code:
service ftp
{
        flags                  = IPv6
        socket_type            = stream
        wait                    = no
        user                    = root
        server                  = /usr/sbin/vsftpd
#      server_args            += local_enable=YES
#      server_args            +=
#      log_on_success          += DURATION USERID
#      log_on_failure          += USERID
        nice                    = 10
        disable                = no
}
Then restart xinetd.
Code:
/sbin/service xinetd restart
I can now ftp and telnet IPv4 and IPv6 to the server.

Code:
[jcliburn@osprey ~]$ ftp petrel
Connected to petrel (192.168.1.6).
220 (vsFTPd 2.0.3)
Name (petrel:jcliburn):
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bye
221 Goodbye.

[jcliburn@osprey ~]$ ftp petrel6
Connected to petrel6 (fec0::2b0:d0ff:fe82:6dda).
220 (vsFTPd 2.0.3)
Name (petrel6:jcliburn):
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bye
221 Goodbye.

[jcliburn@osprey ~]$ telnet petrel
Trying 192.168.1.6...
Connected to petrel.
Escape character is '^]'.
Fedora Core release 4 (Stentz)
Kernel 2.6.14-1.1644_FC4 on an i686
login: jcliburn
Password:
Last login: Fri Dec  9 18:50:27 from 0.0.0.0
[jcliburn@petrel ~]$

[jcliburn@osprey ~]$ telnet petrel6
Trying fec0::2b0:d0ff:fe82:6dda...
Connected to petrel6.
Escape character is '^]'.
Fedora Core release 4 (Stentz)
Kernel 2.6.14-1.1644_FC4 on an i686
login: jcliburn
Password:
Last login: Fri Dec  9 20:00:40 from osprey
[jcliburn@petrel ~]$
Hope this helps.

jcliburn 12-09-2005 08:30 PM
Okay, so the more I think about it, the more I convince myself that *I* put the errant vsftpd.conf in /etc. I can't find anything else that might've put it there. But the bottom line is this: the proper file is /etc/vsftpd/vsftpd.conf, and you need to turn off the "listen" option in that file to allow vsftpd to work within xinetd.

If you want vsftpd to run standalone, then set "listen=yes". From what I can tell, for better or worse, that's the way the option is set in the vsftpd rpm.

q14526 12-13-2005 02:05 PM
Hi jcliburn,
I am sorry to bother you again. I have not be able to get the ftp to work with IPv6 after 2 days of using your instruction, also working and searching all over the web to make sure that I have exaust my ability to solve my problem. Please help me.
Here is my status, using your instruction:
I am able to get telnet work with IPv4 and IPv6 address.
I can only get the ftp to work with IPv4 address (error = unknown host).

1. There is no vsftp file any where in my system including /etc/xinetd.d/
2. I created myself the vsftp file as your list in /etc/xinetd.d/ and I am able to start vsftp without the OOPs error.
3. I did edit the /etc/vsftpd/vsftpd.conf : commented out listen and tcp_wrappers as you said
4. The netstat always show that only ssh reply to IPv6 address but not vsftp and xinetd as shown in your system. I think this is a clue for what I am missing and why ftp does not work for IPv6.

Question: what do you mean by running vsftpd *inside* xinetd or *outside* xinetd ?
Do you mean *start* xinetd (inside) and *stop* xinetd (outside) ?
I tried start vsftpd with *started* or *stopped* xinetd (using command "service xinetd start" or "stop")then run ftp but all I got is "unknown host" error.
It must be some flags setting missing that cause the vsftpd and xinetd do not listen to IPv6 address as your (netstat).

Could you please look at this log and point out what I am missing? Please understand that I did doing the best, spend last 2 days to work on this problem but could not figure it out and I appreciate your help.

I am looking forward to hear from you soon.

Best regards.

--------------------------------------------------------------------------
[root@localhost /]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:D0:B7:57:EC:A0
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fec0::2d0:b7ff:fe57:eca0/64 Scope:Site
inet6 addr: fe80::2d0:b7ff:fe57:eca0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:208519 errors:0 dropped:0 overruns:0 frame:0
TX packets:4626 errors:4 dropped:0 overruns:0 carrier:4
collisions:1528 txqueuelen:1000
RX bytes:36458277 (34.7 MiB) TX bytes:412913 (403.2 KiB)
--------------------------------------------------------------------------
[root@localhost /]# ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:d0:b7:57:ec:a0 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 brd 192.168.10.255 scope global eth0
inet6 fec0::2d0:b7ff:fe57:eca0/64 scope site
valid_lft forever preferred_lft forever
inet6 fe80::2d0:b7ff:fe57:eca0/64 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
--------------------------------------------------------------------------
[root@localhost /]# netstat --proto=inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 :::22 :::* LISTEN 1809/sshd <<<<<<<=========

--------------------------------------------------------------------------

[root@localhost /]# ftp fec0::2d0:b7ff:fe58:6bb6
ftp: fec0::2d0:b7ff:fe58:6bb6: unknown host
ftp> quit
[root@localhost /]# ftp fe80::2d0:b7ff:fe58:6bb6
ftp: fe80::2d0:b7ff:fe58:6bb6: unknown host
ftp> quit
--------------------------------------------------------------------------

jcliburn 12-13-2005 07:01 PM
Quote:
Originally Posted by q14526
Hi jcliburn,
1. There is no vsftp file any where in my system including /etc/xinetd.d/
2. I created myself the vsftp file as your list in /etc/xinetd.d/ and I am able to start vsftp without the OOPs error.
3. I did edit the /etc/vsftpd/vsftpd.conf : commented out listen and tcp_wrappers as you said
4. The netstat always show that only ssh reply to IPv6 address but not vsftp and xinetd as shown in your system. I think this is a clue for what I am missing and why ftp does not work for IPv6.
What does the following command show?
Code:
[root@petrel ~]# yum list installed xinetd vsftpd telnet-server
Installed Packages
telnet-server.i386                      1:0.17-35              installed
vsftpd.i386                              2.0.3-1                installed
xinetd.i386                              2:2.3.13-6            installed
Quote:
Question: what do you mean by running vsftpd *inside* xinetd or *outside* xinetd ?
There are two ways to run vsftpd: (1) standalone, where you explicitly configure vsftpd to listen for connections with no help from xinetd (by setting the "listen=yes" flag in vsftpd.conf); or (2) under the control of xinetd, where you hand over control of vsftpd to xinetd, and xinetd listens for connections. By "outside" xinetd, I mean (1). By "inside" xinetd, I mean (2).


Quote:
[root@localhost /]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:D0:B7:57:EC:A0
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fec0::2d0:b7ff:fe57:eca0/64 Scope:Site
inet6 addr: fe80::2d0:b7ff:fe57:eca0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:208519 errors:0 dropped:0 overruns:0 frame:0
TX packets:4626 errors:4 dropped:0 overruns:0 carrier:4
collisions:1528 txqueuelen:1000
RX bytes:36458277 (34.7 MiB) TX bytes:412913 (403.2 KiB)
--------------------------------------------------------------------------

[root@localhost /]# ftp fec0::2d0:b7ff:fe58:6bb6
ftp: fec0::2d0:b7ff:fe58:6bb6: unknown host
ftp> quit
The IP address you fed to the ftp command (fec0::2d0:b7ff:fe58:6bb6) doesn't match the IPv6 address listed in the above ifconfig output (fec0::2d0:b7ff:fe57:eca0).

Quote:
[root@localhost /]# ftp fe80::2d0:b7ff:fe58:6bb6
ftp: fe80::2d0:b7ff:fe58:6bb6: unknown host
ftp> quit
Trying to connect ftp to a link-local address (fe80::*) will never work; it's an invalid argument.

I'll post all my related config files in a few minutes.

jcliburn 12-13-2005 07:18 PM
These config files enable the use of vsftpd and telnetd under the control of xinetd. I don't use either telnet or ftp, so if the config files are configured stupidly and/or insecurely, I don't care. I intend to disable the services when this is over.

First, remove or rename /etc/vsftpd.conf if it exists.

Second, disable the firewall on the server machine (or configure it to allow connections on ports 21 and 23).

The following files are on the server machine (hostname petrel), not the client (hostname osprey).

/etc/vsftpd/vsftpd.conf
Code:
[root@petrel ~]# cat /etc/vsftpd/vsftpd.conf
# Example config file /etc/vsftpd/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
# Allow anonymous FTP? (Beware - allowed by default if you comment this out).
anonymous_enable=YES
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format
xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that turning on ascii_download_enable enables malicious remote parties
# to consume your I/O resources, by issuing the command "SIZE /big/file" in
# ASCII mode.
# These ASCII options are split into upload and download because you may wish
# to enable ASCII uploads (to prevent uploaded scripts etc. from breaking),
# without the DoS risk of SIZE and ASCII downloads. ASCII mangling should be
# on the client anyway..
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd/banned_emails
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
#chroot_list_enable=YES
# (default follows)
#chroot_list_file=/etc/vsftpd/chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES

pam_service_name=vsftpd
userlist_enable=YES
#enable for standalone mode
#listen_ipv6=YES
#tcp_wrappers=YES
/etc/xinetd.conf
Code:
[root@petrel ~]# cat /etc/xinetd.conf
#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/

defaults
{
        instances              = 60
        log_type                = SYSLOG authpriv
        log_on_success          = HOST PID
        log_on_failure          = HOST
        cps                    = 25 30
}

includedir /etc/xinetd.d
/etc/xinetd.d/vsftpd
Code:
[root@petrel ~]# cat /etc/xinetd.d/vsftpd
# default: on
# description:
#  The vsftpd FTP server serves FTP connections. It uses
#  normal, unencrypted usernames and passwords for authentication.
# vsftpd is designed to be secure.
service ftp
{
        flags                  = IPv6
        socket_type            = stream
        wait                    = no
        user                    = root
        server                  = /usr/sbin/vsftpd
#      server_args            += local_enable=YES
#      server_args            +=
#      log_on_success          += DURATION USERID
#      log_on_failure          += USERID
        nice                    = 10
        disable                = no
}
/etc/xinetd.d/telnet
Code:
[root@petrel ~]# cat /etc/xinetd.d/telnet
# default: on
# description: The telnet server serves telnet sessions; it uses \
#      unencrypted username/password pairs for authentication.
service telnet
{
        flags          = IPv6
        socket_type    = stream
        wait            = no
        user            = root
        server          = /usr/sbin/in.telnetd
        log_on_failure  += USERID
        disable        = no
}
Restart xinetd
Code:
[root@petrel ~]# service xinetd restart
Stopping xinetd:                                          [  OK  ]
Starting xinetd:                                          [  OK  ]
Verify xinetd listening IPv6 on ftp (port 21) and telnet (port 23).
Code:
[root@petrel ~]# netstat --inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address              Foreign Address           
tcp        0      0 :::21                      :::*                        LISTEN      4139/xinetd
tcp        0      0 :::22                      :::*                        LISTEN      1628/sshd
tcp        0      0 :::23                      :::*                        LISTEN      4139/xinetd
The server's interface config.
Code:
[root@petrel ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:B0:D0:82:6D:DA
          inet addr:192.168.1.6  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fec0::2b0:d0ff:fe82:6dda/64 Scope:Site
          inet6 addr: fe80::2b0:d0ff:fe82:6dda/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6441 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6107 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:647578 (632.4 KiB)  TX bytes:542633 (529.9 KiB)
          Interrupt:5 Base address:0xec80
An ftp session.
Code:
[jcliburn@osprey ~]$ ftp fec0::2b0:d0ff:fe82:6dda
Connected to fec0::2b0:d0ff:fe82:6dda (fec0::2b0:d0ff:fe82:6dda).
220 (vsFTPd 2.0.3)
Name (fec0::2b0:d0ff:fe82:6dda:jcliburn):
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bye
221 Goodbye.
[jcliburn@osprey ~]$

q14526 12-14-2005 08:51 AM
Hi jcliburn,
Thank you very much for your time and for your much need response.
1. There is no vsftpd.conf in my /etc
2. My /etc/vsftpd/vsftpd.conf, /etc/xinetd.conf, /etc/xinetd.d/vsftpd and /etc/xinetd.d/telnet files are compared to be identical as your sample files.
3. xinetd, vsftpd start OK just as you show
4. Again, "netstat --inet6 -pnl" command does not show anything else but "sshd"
5. The reason you see my ftp command does not match with listed IPv6 address because I am ftp to the other machine. I tried to ftp itself (ftp fec0::2d0:b7ff:fe57:eca0) but still it returned "unknown host".
6. I think even both of my PCs installed and setup as server (the same way) the "netstat --inet6 -pnl" command should show exactly as yours.
7. You said "The following files are on the server machine (hostname petrel), not the client (hostname osprey)": I assume that the client will not have vsftpd, xinetd started. May be it was my dum idea but I stopped both services on one machine and I still got the same unknown host error. Is that OK for both machines setup identical as server ? In anycase, the netstat command must show just as what you have.
8.Should I start from scratch by reinstall FC4 one as server and one as workstation ?

Once again, I'm really appreciate your help and your time.

Best regards.

These are logs from my 2 PCs, both have the same FC4 installation as Server with most if not all options were selected and with *no* firewall:

This PC#1:

[root@localhost ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:D0:B7:57:EC:A0
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fec0::c0a8:a01/64 Scope:Site
inet6 addr: fec0::2d0:b7ff:fe57:eca0/64 Scope:Site
inet6 addr: fe80::2d0:b7ff:fe57:eca0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:210889 errors:0 dropped:0 overruns:0 frame:0
TX packets:4940 errors:4 dropped:0 overruns:0 carrier:4
collisions:1530 txqueuelen:1000
RX bytes:36754270 (35.0 MiB) TX bytes:440413 (430.0 KiB)
---------------------------------------------------------------------------
[root@localhost ~]# yum list installed xinetd vsftpd telnet-server
Installed Packages
telnet-server.i386 1:0.17-35 installed
vsftpd.i386 2.0.3-1 installed
xinetd.i386 2:2.3.13-6 installed
---------------------------------------------------------------------------
[root@localhost ~]# netstat --inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 :::22 :::* LISTEN 1809/sshd
===========================================================================

This is PC#2:

[root@localhost /]# yum list installed xinetd vsftpd telnet-server
Installed Packages
telnet-server.i386 1:0.17-35 installed
vsftpd.i386 2.0.3-1 installed
xinetd.i386 2:2.3.13-6 installed
---------------------------------------------------------------------------
[root@localhost /]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:D0:B7:58:6B:B6
inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fec0::c0a8:a02/64 Scope:Site
inet6 addr: fec0::2d0:b7ff:fe58:6bb6/64 Scope:Site
inet6 addr: fe80::2d0:b7ff:fe58:6bb6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:206071 errors:0 dropped:0 overruns:0 frame:0
TX packets:6725 errors:6 dropped:0 overruns:0 carrier:6
collisions:2763 txqueuelen:1000
RX bytes:38283545 (36.5 MiB) TX bytes:623209 (608.6 KiB)
---------------------------------------------------------------------------
[root@localhost /]# netstat --inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 :::22 :::* LISTEN 2225/sshd

===========================================================================

jcliburn 12-14-2005 10:58 AM
Quote:
Is that OK for both machines setup identical as server ?
Yes, it's okay.

Quote:
Should I start from scratch by reinstall FC4 one as server and one as workstation ?
No, it shouldn't be necessary.

Please execute the following commands on the server machine and post their results here.
Code:
# service xinetd restart
# netstat --proto=inet,inet6 -pnl
# hostname
# cat /etc/hosts
# cat /etc/sysconfig/network
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
Please execute the following commands on the client machine (the from which you'll execute the "ftp" command) and post their results here.
Code:
# which ftp
# hostname
# cat /etc/hosts
I find it exceedingly odd that your ftp client thinks an IPv6 address is a hostname.

Which, if any, of your hosts is running radvd?

Do you have ethereal-gnome installed?

q14526 12-15-2005 08:06 AM
Hi jcliburn,

I think you ask the absolute right questions. Some how the one I call Server(or PC#2) after I excecuted again "service xinetd restart" as you said I see that there are 2 instances of xinetd and both listen to IPv6 address (exactly as in your system), while the PC#1 which I call Client has none other than sshd listen to IPv6 address. I do not recall what I did differently from one machine to the other and why it is like that. Ofcourse the ftp still failed.
I then execute "service xinetd restart" on the Client, now I see that there is one, but only one, xinetd listen to IPv6 address. The ftp still failed.

In my work environment, is my embedded Linux box(network printer, or target system) a client or server ? These 2 systems are supposed to be identical so that I can telnet, ftp to and from either one (Any developer can telnet or ftp in or out from one to the other)
What can I do now? Please help me.

Best regards.
Quang

Here is the screen logs for 2 machines.
=======================================================================
CLIENT (PC#1)
=======================================================================
[root@localhost /]# which ftp
/usr/kerberos/bin/ftp

[root@localhost /]# hostname
localhost.localdomain

[root@localhost /]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost

[root@localhost /]# netstat --proto=inet,inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 1441/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1423/portmap
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 19217/xinetd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 31192/cupsd
tcp 0 0 127.0.0.1:5335 0.0.0.0:* LISTEN 1726/mDNSResponder
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1841/sendmail: acce
tcp 0 0 :::22 :::* LISTEN 1809/sshd
udp 0 0 0.0.0.0:32768 0.0.0.0:* 1441/rpc.statd
udp 0 0 0.0.0.0:769 0.0.0.0:* 1441/rpc.statd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1726/mDNSResponder
udp 0 0 0.0.0.0:111 0.0.0.0:* 1423/portmap
udp 0 0 0.0.0.0:631 0.0.0.0:* 31192/cupsd

=======================================================================
SERVER (PC#2)
=======================================================================
[root@localhost /]# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]

[root@localhost /]# netstat --proto=inet,inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 1831/rpc.statd
tcp 0 0 0.0.0.0:612 0.0.0.0:* LISTEN 2132/rpc.mountd
tcp 0 0 0.0.0.0:32774 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1787/portmap
tcp 0 0 0.0.0.0:1008 0.0.0.0:* LISTEN 2100/rpc.rquotad
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 18884/cupsd
tcp 0 0 127.0.0.1:5335 0.0.0.0:* LISTEN 2162/mDNSResponder
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2251/sendmail: acce
tcp 0 0 :::21 :::* LISTEN 15067/xinetd
tcp 0 0 :::22 :::* LISTEN 2225/sshd
tcp 0 0 :::23 :::* LISTEN 15067/xinetd
udp 0 0 0.0.0.0:32768 0.0.0.0:* 1831/rpc.statd
udp 0 0 0.0.0.0:2049 0.0.0.0:* -
udp 0 0 0.0.0.0:32822 0.0.0.0:* -
udp 0 0 0.0.0.0:735 0.0.0.0:* 1831/rpc.statd
udp 0 0 0.0.0.0:609 0.0.0.0:* 2132/rpc.mountd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 2162/mDNSResponder
udp 0 0 0.0.0.0:1005 0.0.0.0:* 2100/rpc.rquotad
udp 0 0 0.0.0.0:111 0.0.0.0:* 1787/portmap
udp 0 0 0.0.0.0:631 0.0.0.0:* 18884/cupsd
[root@localhost /]#

[root@localhost /]# hostname
localhost.localdomain

[root@localhost /]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost

[root@localhost /]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=localhost.localdomain

[root@localhost /]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:D0:B7:58:6B:B6
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=yes
NETMASK=255.255.255.0
IPADDR=192.168.10.2
[root@localhost /]#

=======================================================================
Client: Execute "service xinetd restart"
=======================================================================
[root@localhost /]# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]

[root@localhost /]# netstat --proto=inet,inet6 -pnl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 1441/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1423/portmap
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 31269/xinetd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 31192/cupsd
tcp 0 0 127.0.0.1:5335 0.0.0.0:* LISTEN 1726/mDNSResponder
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1841/sendmail: acce
tcp 0 0 :::21 :::* LISTEN 31269/xinetd
tcp 0 0 :::22 :::* LISTEN 1809/sshd
udp 0 0 0.0.0.0:32768 0.0.0.0:* 1441/rpc.statd
udp 0 0 0.0.0.0:769 0.0.0.0:* 1441/rpc.statd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1726/mDNSResponder
udp 0 0 0.0.0.0:111 0.0.0.0:* 1423/portmap
udp 0 0 0.0.0.0:631 0.0.0.0:* 31192/cupsd

[root@localhost /]# hostname
localhost.localdomain

[root@localhost /]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost

[root@localhost /]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=localhost.localdomain
[root@localhost /]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:D0:B7:57:EC:A0
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=yes
IPADDR=192.168.10.1
NETMASK=255.255.255.0
[root@localhost /]#

jcliburn 12-15-2005 08:42 AM
You're using the wrong ftp client. Use /usr/bin/ftp. (I think that's where it is. Find it with the command "whereis ftp".)

As a matter of fact, you should remove /usr/kerberos/bin from your default path if you're not using any kerberized services.

Quote:
In my work environment, is my embedded Linux box(network printer, or target system) a client or server ?
What is deemed a client or server is determined by the particular action you're trying to perform. The server provides a service; the client attempts to use that service. If you're trying to ftp from one host to another, the server is the host running the ftp daemon and listening for connections; the client is the host from which you execute the ftp command. Any host, whether or not it's called a "server," can provide a service if it's configured to do so.

For the sake of simplifying your troubleshooting efforts with this particular problem, I recommend you pick one machine and use that as your server. Focus your attention on getting the daemons correctly configured on that machine. Use the other machine as your client and initiate your ftp, telnet, ssh, whatever commands from that machine. Once you get everything working correctly, duplicate the configuration on the other machine if your intent ultimately is to have two ftp/telnet servers for your staff.

I'm at work right now, and I don't have access to my Fedora machines at home, but I'll look into your results more when I get home this evening.

q14526 12-15-2005 03:21 PM
Hi jcliburn,
You are right on. Here is the steps that I did on my client:

1. Activate the device profile for crossover cable (I was using the DHCP profile for send my logs file back to my workstation). I don't know the command how to deactivate or activate a current ethernet device from console so I have to do it with Fedora GUI.

2. Add back IPv6 addresses fec0::c0a8:a01 and fec0::2d0:b7ff:fe57:eca0

3. I don't know where to change the PATH so I rename the usr/kerberos to usr/kerberos.notused hopefully it will continue search in /usr/bin (it is in the PATH)but it did not look further than /usr/kerberos, it say command not found so I have to use full path.
I see the following files specify /usr/kerberos path: eklogin, gssftp, klogin and kshell. Which one should I change to /usr/bin, should I change all of them ?

4. I run "service xinetd restart" then
5. I run "service vsftpd restart"

I do not know if the above order of running xinetd and vsftpd is important or not but now the netstat command does show 2 instance of xinetd listening to IPv6 address

Run /usr/bin/ftp fec0::c0a8:a01 and it works! but has to be full path
Also /usr/bin/telnet fec0::c0a8:a01 work too!

I forgot to answer one of your previous question regarding ethereal-gnome, I really don't know what it is and if it was installed with Server option in FC4 installation, I don't know.

Why all the sudden on my *client* machine show 2 instances of xinetd listening to IPv6 address?
It was not like that this morning, can the above order of running xinetd and vsftpd is the reason?

I repeat the above steps on my *server* machine, the netstat show the same 2 instances of xinetd. and now I can ftp to/from either one.
Those are couple more questions for you. I hope that I know how to use this knowledge to set up the real system using Red Hat 9 (2.4.20).

Thank you very very much for your help. I appreciate the time you put in to help me.
I am looking forward to hear from you soon.

Best regards.

jcliburn 12-15-2005 07:10 PM
Quote:
I don't know where to change the PATH so I rename the usr/kerberos
To remove /usr/kerberos/bin from your path, comment out the entire contents of /etc/profile.d/krb5.sh and /etc/profile.d/krb5.csh, or remove the files altogether. Renaming them won't do it, since /etc/profile (the script) reads the contents of each file in the /etc/profile.d directory and incorporates them into the login environment.

Quote:
4. I run "service xinetd restart" then
5. I run "service vsftpd restart"
You should execute only "service xinetd restart"; not "service xinetd restart" AND "service vsftpd restart". You should not enable vsftpd in xinetd, then turn around and start vsftpd from the command line. Do one or the other; not both. If you enable vsftpd in /etc/xinetd.d/vsftpd, then you need only start xinetd; do not also start vsftpd from the command line. Xinetd will handle ftp connections for you. Xinetd starts programs that provide Internet services. Instead of having such servers (like vsftpd, telnetd, and others) started at system initialization time, and be dormant until a connection request arrives, xinetd is the only daemon process started and it listens on all service ports for the services listed in its configuration file. When a request comes in, xinetd starts the appropriate server. Because of the way it operates, xinetd is also referred to as a super-server.

Quote:
I forgot to answer one of your previous question regarding ethereal-gnome, I really don't know what it is and if it was installed with Server option in FC4 installation, I don't know.
Ethereal is a network packet capture tool that you can use to examine network traffic moving to and from your machine. Ethereal (or, specifically, /usr/sbin/tethereal) is a command-line, text-based packet capture tool. Ethereal-gnome is a GUI-based front end for ethereal. Either of them are very useful for troubleshooting problems involving communication between hosts. So is tcpdump. You should familiarize yourself with them.

Quote:
Why all the sudden on my *client* machine show 2 instances of xinetd listening to IPv6 address?
I can't explain why your PC1 suddenly began working, I'm just glad it did.

Good luck.

Jay

q14526 12-16-2005 09:42 AM
Hi jcliburn and cuiq,

Thank you so much for your kindness and patience. It will be a long time but I hope I will be as good as you on linux because my company has get rid of all lynx, sunOS, precise, etc... to use Linux. Now I have to use those knowledge to setup my real system but I know where to get help.

I wish you all a merry Christmas, a happy new year and good health (so you can help others!).
I wish I can send you guy, at the minimum, a thank you card.

Once again, thank you very much.

Best regards.
:)


All times are GMT -5. The time now is 12:24 PM.