vstpd.conf
by dhottinger＠harrisonburg.k12.va.us
Im having a devil of a time getting vsftpd configured for auth. with
an ldap backend on Fedora Core 5. I keep getting a 530 530 Login
incorrect.
Unable to make a connection. Please try again.
The server has a username incorrect message.
Anonymous works fine. I have standard vsftpd.conf here is the snippet:
anonymous_enable=No
#
# 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
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_local_user=YES
#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=vsftp
userlist_enable=YES
#enable for standalone mode
listen=YES
tcp_wrappers=YES
User authentication is against an ldap server. That seems to be
working fine. AFP users can connect ok. I read about an issue with
the pam module, but that doesnt seem to be the case. I keep beating
this thing around and around with no joy so far.
--
Dwayne Hottinger
Network Administrator
Harrisonburg City Public Schools
15 years, 9 months
Kernel numbers
by Jeff Stevens
What does it mean to see an rpm with a kernel of 2.6.10-1.741_FC3, when
we go to a site like http://www.kernel.org and see the latest kernel is
at 2.6.10? If one wanted to compile their own kernel from this site,
would they be losing fixes/etc. from the "-1.741_FC3" portion?
Thanks, still learning here...
--
Jeffrey Stevens
gpg --keyserver pgp.mit.edu --recv-keys D2E5A4E8
Key fingerprint: 1C86 8717 E485 FA4D B9EF 96E2 A1AC 4B00 D2E5 A4E8
15 years, 10 months
tar backup on tape doesn't work
by Budiono
Hi all,
I 'm just install a scsi card BusLogic BT-958 and HP DAT 40, on my
fedora core 6 system. I usually backup my system, using tar.
My problem is backup doesn't running well.
And this is my backup script:
#tar -b 1024 -cvf /dev/st0 /usr/local/src/my_home/yahoomail | bzip2 -9 >
/var/log/Backup.log.bz2
Backup only run a while, and archive some files in directory and then stop.
[root@mis-s155 ~]# tar -b 1024 -cvf /dev/st0
/usr/local/src/my_home/yahoomail | bzip2 -9 > /var/tmp/Backup.log.bz2
tar: Removing leading `/' from member names
tar: /dev/st0: Cannot write: Device or resource busy
tar: Error is not recoverable: exiting now
But when I put out -b parameter on tar. It run a while and not backup
directory at all
The backup script I used was running well when I'm using redhat 9.0 system.
I attach some message from my system
scsi: ***** BusLogic SCSI Driver Version 2.1.16 of 18 July 2002 *****
scsi: Copyright 1995-1998 by Leonard N. Zubkoff <lnz(a)dandelion.com>
scsi5: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
scsi5: Firmware Version: 5.06I, I/O Address: 0xDC00, IRQ Channel:
225/Level
scsi5: PCI Bus: 2, Device: 3, Address: 0xFEAFF000, Host Adapter SCSI ID: 7
scsi5: Parity Checking: Enabled, Extended Translation: Enabled
scsi5: Synchronous Negotiation: Fast, Wide Negotiation: Enabled
scsi5: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
scsi5: Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
scsi5: Driver Queue Depth: 211, Host Adapter Queue Depth: 192
scsi5: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
scsi5: SCSI Bus Termination: Both Enabled, SCAM: Disabled
scsi5: *** BusLogic BT-958 Initialized Successfully ***
scsi5 : BusLogic BT-958
Vendor: HP Model: C5683A Rev: YP61
Type: Sequential-Access ANSI SCSI revision: 03
scsi 5:0:3:0: Attached scsi generic sg1 type 1
st: Version 20050830, fixed bufsize 32768, s/g segs 256
st 5:0:3:0: Attached scsi tape st0
st0: try direct i/o: yes (alignment 512 B)
[root@mis-s155 ~]# mt -f /dev/st0 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x26 (DDS-4 or QIC-4GB).
Soft error count since last status=0
General status bits on (1010000):
ONLINE IM_REP_EN
I very appeciate for any solution and comment.
Thank you
Budiono
15 years, 11 months
Re: Port forwarding
by Andy
Hi,
Jari Marikainen wrote:
> I would like to forward incoming traffic from internet to
> "<195.198.111.x> port 80" to "<some other ip on the internet> port 80"
> in FC3 on the same interface.
I would try the DNAT/SNAT iptables targets, along the lines of:
iptables -t nat -A PREROUTING -p tcp --dport 80 -d 195.198.111.x \
-j DNAT --to-destination 65.114.4.69
iptables -t nat -A POSTROUTING -p tcp --dport 80 -d 65.114.4.69 \
-j SNAT --to-source <your external IP address on this machine>
The second line makes the real server send it's replies through the same
path (otherwise it will reply directly to the client)
You have to enable/allow forwarding for everything to work.
hth,
/Andy
15 years, 11 months
ssh and port 22 problem, cont.
by Gerhard Magnus
Greetings!
I've made some progress on troubleshooting this "ssh & port 22 problem".
Here was my original post:
When I try to connect from a remote machine to my one at home
using ssh I get the error message "ssh: connect to host 64.146.133.1 port
22: Connection refused" -- but using ssh in the outgoing direction (i.e.
from home to the remote location) works fine.
Here's what's happened since:
I have two machines (PuteA and PuteB) sharing an ActionTec DSL modem. The IP
I was using was that of my "Gateway" ISP (64.146.133.1) -- an error. But
when I used the correct, static IP address of the ActionTec
(64.146.133.52) I got this message:
ssh: connect to host 64.146.133.52 port22: Connection refused
I thought I had port forwarding (for port 22) set correctly on the modem. For
troubleshooting, my ISP advised me to run "tcpdump -n host 192.168.0.2" on
PuteA, where 192.168.0.2 is the "internal" IP of PuteA. Then I logged on
to the remote location from PuteB and tried to ssh from there to PuteA
using the static IP address. The ssh from the remote location timed out
with the same "port 22: connection refused" message. The tcpdump on Pute
A gave this message:
> tcpdump: listening on eth0
> 17:27:33.662753 arp who-has 192.168.0.2 tell 192.168.0.1
where 182.168.0.1 is the "internal" IP of the modem. (Sorry if I have
this terminology wrong.)
My ISP says the problem is the firewall on PuteA and that he doesn't do linux
firewalls.
Here are my replies to the people who responded to my first post:
(1) "Do you have the firewall configured to deny incoming packets to port
22?"
How do I check this?
(2) "You need to check that sshd is running on your system."
Yes. I comes up with each boot. Also "service sshd status" gives
"sshd (pid 787) is running".
(3) "sshd uses /etc/hosts.allow and /etc/hosts.deny. Check that they are
configured to allow your remote machine in."
Both files have only commented lines.
(4) "Also, if your /etc/ssh/sshd_config file has VerifyReverseMapping
turned on, you will get kicked out if your remote address does not work
with a reverse dns lookup."
There's a "VerifyReverseMapping no" line in the file but it's been commented
out.
(5) "Just to be sure: when you are at home machine, try 'ssh localhost'.
If this works, you probably need to check your firewall."
It seems to work -- I ssh to the machine itself.
(6) "This is common on every system I have ever loaded with FC2. Your
iptables are blocking the connection. You can do one of the following:
iptables -A INPUT -m tcp -p tcp --dport 22 - j ACCEPT"
I tried this. The ssh to PuteA from the remote location still times out.
(7) "Oh yes I also took out the REDHAT firewall entrie as I dont have a
clue as to how to work with it."
I've fiddled endlessly with this "system tool" at each of the three levels
of security as well as using the "customize" option to set eth0 as a
trusted device and to allow incoming ssh. It doesn't show the settings
that actually exist.
(8) "If your fedora box is connected directly to a DSL modem, you should
be able to find your IP address by running ifconfig from the command
line and looking for 'inet addr:' (probably under 'eth0')."
eth0 Link encap:Ethernet HWaddr 00:40:05:81:60:8E
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2184 errors:0 dropped:0 overruns:0 frame:0
TX packets:2005 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1122075 (1.0 Mb) TX bytes:190214 (185.7 Kb)
Interrupt:5 Base address:0x3000
Could this be the problem -- the "inet addr" of 192.168.0.4? As far as I
can tell, the modem is 192.168.0.1, PuteA is 192.168.0.2, and PuteB is
192.168.0.3. I haven't set anything as 192.168.0.4.
(9) "nmap 64.146.133.52"
(The 1598 ports scanned but not shown below are in state: closed)
Port State Service
23/tcp open telnet
53/tcp open domain
80/tcp open http
Shouldn't ssh be here? And what's telnet doing open? The books have me
scared to death of this... hackers, crackers, script kiddies, etc.
Thanks for the help!
Jerry Magnus
16 years
Yum repair
by Timothy Murphy
I upgraded FC-6 to F-7 on an Athlon64 machine,
and the process hung several (3 I think) times during installation.
Each time I re-started the machine,
the number of packages was greatly reduced: 950 ... 400 ... 50.
The system works fine,
but it is pretty clear all the packages were not properly installed.
Eg when I ran "yum update" after the installation
only 30 or so packages were downloaded,
while on other systems the number was 300-400.
Is there any way of checking that everything has been downloaded?
Or is there even a command like "yum --force install"
to force a re-installation of a particular package?
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
16 years, 1 month
keyspan usb serial and fc6 help
by matt pieklik
I had my keyspan USB serial adapter 19HS working with FC5, but now
that I have upgraded to FC6 it is no longer fully functional. It is
detected, and I get one way communication through it when I use
minicom. I am able to send but not receive, I determined this by
connecting two machine via serial.
Is this a problem with the USB serial adapter, or do I not have the
associated serial port configured correctly?
Here is the output from the startup:
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver libusual
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usb usb1: configuration #1 chosen from 1 choice
usb usb2: configuration #1 chosen from 1 choice
usb usb3: configuration #1 chosen from 1 choice
usb usb4: configuration #1 chosen from 1 choice
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 2 choices
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan - (without firmware)
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan 1 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan 2 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan 4 port adapter
usb 2-2: Keyspan 1 port adapter converter now attached to ttyUSB0
usbcore: registered new interface driver keyspan
drivers/usb/serial/keyspan.c: v1.1.4:Keyspan USB to Serial Converter Driver
Thanks for any help.
Matt
16 years, 1 month
/tmp running out of space
by Anne Wilson
/tmp is filling up rapidly. I'm guessing that it would be safe enough to
delete everything dated previous to the last bootup. Am I right?
Anne
16 years, 2 months
