Page 2 of 2
Re: FTP not working anymore
Posted: 13 Feb 2011, 06:30
by theWebalyst
While trying the above I note the following in my /etc/proftpd/proftpd.conf
Code: Select all
ServerName "Bubba"
ServerType standalone
DeferWelcome off
I'm curious as to why this is "Bubba" rather than "b3" (the lookup that actually fails)?
Anyway, with ReverseDNS off and my /etc/hosts back to normal...
Code: Select all
# /etc/init.d/proftpd restart
Stopping ftp server: proftpd.
Starting ftp server: proftpd - warning: unable to determine IP address of 'b3'
- error: no valid servers configured
- Fatal: error processing configuration file '/etc/proftpd/proftpd.conf'
failed!
Strangely, no change! I thought this would work but it doesn't, so back to the /etc/hosts hack for now.
Mark
Re: FTP not working anymore
Posted: 13 Feb 2011, 06:40
by Ubi
Re: FTP not working anymore
Posted: 13 Feb 2011, 07:46
by theWebalyst
Thanks Ubi for the suggestion.
For me the /etc/hosts fix is adequate as my IP only changes if I reboot the modem which is very rare. My interest is in trying to identify the cause, as my b3 is very standard (hardly anything added and nothing that makes me suspicious). This is the first time I have tried FTP on my b3 (on bubba|2 it was working fine) so I'm hypothesising that its a systemic issure rather than something I've done to break it.
Anyway, I hope we can identify the cause of the problem. Is there a clue in the difference between bubba|2 and b3?
Mark
Re: FTP not working anymore
Posted: 13 Feb 2011, 09:35
by Cheeseboy
I'm curious as to why this is "Bubba" rather than "b3" (the lookup that actually fails)?
I think this is only relevant to the message you get when connecting:
Code: Select all
niklas@muttan:~$ ftp b3
Connected to b3.localdomain.
220 ProFTPD 1.3.3a Server (Bubba) [::ffff:192.168.10.1]
Name (b3:niklas)
Is there a clue in the difference between bubba|2 and b3?
No, not that I can think of. Both has worked fine for me as FTP servers.
But I have a domain registered and pointing to my public IP address.
Oh, I just remembered, I have also added this line to /etc/bubba/dhclient.conf:
Code: Select all
prepend domain-name-servers 192.168.10.1;
This was in order to get b3 itself listed first in resolv.conf, so that dnsmasq will identify any machines that I connect to my network. It produces a lot of warnings in syslog (see below), but it was the only way I could get the b3 to behave like a proper dhcp/dns solution. I had a similar hack on the Bubba|2, but the file was somewhere else then...
Code: Select all
Feb 13 06:49:30 b3 dnsmasq[1551]: ignoring nameserver 192.168.10.1 - local interface