Minix 3.15 on VMWare - Issues with FTP client.

638 views
Skip to first unread message

Karthik Urs

unread,
Jan 17, 2010, 2:33:36 AM1/17/10
to minix3
Hi,

I have installed VMWare on my Windows XP. I have installed Minix 3.15
on the virtual machine. I want to FTP from windows to minix using
filezilla (or any other FTP client). I am unable to FTP.

I am, however, able to FTP to minix 2.04. Here are some points which
might help you guys to help me :)

1. I tried using Network Adapter on VMWare as NAT as well as bridged.
No luck.

2. I have enable root password. I have also created another user
account. Am not able to telnet with either of these.

3. I have started ftp service with the command - intr -d tcpd ftp
in.ftpd &. This worked on minix 2.04. Not on 3.15

4. serv.access which I edited on minix 2.04 is missing on 3.15. I am
not sure if the file was removed as a part of new release. I even
tried making a new file. No luck.

5. The IP address on minix and on windows are in same subnet.


I am having no issues with FTPing from windows to Minix 2.04. But I
tried the above steps and nothing seems to work. I know one can live
without that, but I am too keen on making this work. It makes my job
loads easier.

Any help on this would be greatly appreciated.

Erik van der Kouwe

unread,
Jan 17, 2010, 6:39:29 AM1/17/10
to minix3
Hi,

Although I agree that it should be possible to make this work, an
alternative solution could be to run the server on the Windows side.
You can enable the IIS FTP server or get FileZilla server or something
similar. It may be a bit less convenient, but it is easy to set up and
better than nothing.

With kind regards,
Erik

Karthik Urs

unread,
Jan 17, 2010, 2:41:48 PM1/17/10
to minix3
Hey Erik,

I could try that but to be honest, I like working on windows more.
Moreover, I work on two different installations on VMWare
simultaneously. So, I prefer working on windows and then transferring
'em to both the machines.

And what can you make out of this message on Filezilla?

Status: Connection established, waiting for welcome message...
Error: Could not connect to server

When I had this issue on Minix 2.04, I had to edit /etc/serv.access
Can you point me to a file on Minix 3.15 which might have replaced
this file from 2.0?

Erik van der Kouwe

unread,
Jan 17, 2010, 3:21:23 PM1/17/10
to minix3
Hi,

Maybe you didn't start the FTP server then? Rename /etc/
rc.daemons.dist to /etc/rc.daemons and throw out the lines you don't
need. Reboot afterwards. I'm still not sure if you can get it to work,
but it may be a step in the right direction.

With kind regards,
Erik

With kind regards,
Erik

> > > Any help on this would be greatly appreciated.- Hide quoted text -
>
> - Show quoted text -

Karthik Urs

unread,
Jan 17, 2010, 4:12:03 PM1/17/10
to minix3
Erik,

I have already done that. Also tried starting the service manually.

I guess its an issue with firewall. Thanks for the time. I will try
getting it up and running..

Regards,
Karthik

Erik van der Kouwe

unread,
Jan 17, 2010, 4:31:49 PM1/17/10
to minix3
Hi,

AFAIK MINIX has no firewall and VMWare should not implement one
either.

With kind regards,
Erik

Karthik Urs

unread,
Jan 17, 2010, 8:46:03 PM1/17/10
to minix3
Erik,

You are right. I was referring to it in a more generic sense
(serv.access acts like a firewall for tcp oriented connections as ,
IMO, tcpd looks up at serv.access). My mistake.


And strange thing, my problems are solved.

I chucked VMWare workstation and started using VMWare player. Just
enabling the service was enough this time. Strangely enough, this
didn't work earlier and that's why I had to switch to VMWare
workstation in first place. FTP works fine when image is loaded on
VMWare player.


Thanks,
Karthik

Antoine Leca

unread,
Jan 18, 2010, 4:00:37 AM1/18/10
to min...@googlegroups.com
Karthik Urs wrote:
> 1. I tried using Network Adapter on VMWare as NAT as well as bridged.

If you have an external infrastructure (DHCP), bridged is the easiest to
setup in Minix, and it should work this way. If you does not, NAT also
should work but it is a bit more complex (more servers are involved), so
there are more pitfalls; OTOH (particularly if you know 2.0.4) you might
configure the network manually (with ifconfig , add_route, %nameserver
and so on.)


> 3. I have started ftp service with the command - intr -d tcpd ftp
> in.ftpd &. This worked on minix 2.04. Not on 3.15

How do you know it does not work?
Did you try to use ftp locally (in the Minix VM, using 127.0.0.1)?
It should work; and if it does not, you won't succeed at loging in
externally!
The more obvious cause to that is a blocked inet server; I remember the
loopback cna be blocked when there are no active "adaptor" (hence the
default psip1); I guess you are not stuck this way, but check this.


> 4. serv.access which I edited on minix 2.04 is missing on 3.15.

AFAIR it was not active by defect on 2.0.x either. Anyway, it there is
no serv.access, tcpd runs the normal (unchecked) way and it works OK.
In fact, if you are having problems, /disabling/ serv.access is probably
a good idea to start with... When it works, you can then improve the
security by re-enabling it.


> 5. The IP address on minix and on windows are in same subnet.

The 3.1.x ftpd server insists knowing its client by name, the numeric IP
is not sufficient. So either you have a DNS server with gives a name to
the hosting address, or you should fix this in /etc/hosts (and have a
network setup quite a bit more complex.)

Antoine

Karthik Urs

unread,
Jan 18, 2010, 1:47:31 PM1/18/10
to min...@googlegroups.com
Hey Antoine,

Your post is enlightening. I am not familiar with Minix at all. In fact, I only installed it day before. Thanks for a detailed explanation.

How do you know it does not work?
Did you try to use ftp locally (in the Minix VM, using 127.0.0.1)? 

Well, I thought starting the service must listen to the connections and accept them. I didn't try FTPing locally. I will do it and check once.

n fact, if you are having problems, /disabling/ serv.access is probably
a good idea to start with... When it works, you can then improve the
security by re-enabling it.

Of course. But my concern was whether or not some other file was used instead of serv.access in Minix 3.X.

I might sound naive at times (or most of the times ;)) I am getting to know minix still.. :)

Thanks for the exhaustive reply though. It helped. 

Regards,
Karthik

--
You received this message because you are subscribed to the Google Groups "minix3" group.
To post to this group, send email to min...@googlegroups.com.
To unsubscribe from this group, send email to minix3+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/minix3?hl=en.




Rahmat M. Samik-Ibrahim

unread,
Jan 19, 2010, 12:04:46 PM1/19/10
to min...@googlegroups.com
Karthik Urs wrote:

> I have installed VMWare on my Windows XP. I have installed Minix 3.15
> on the virtual machine. I want to FTP from windows to minix using
> filezilla (or any other FTP client). I am unable to FTP.

1) Just in case... Is the network on? I.e. can you run "ifconfig"?
The output should be something like:
$ ifconfig
/dev/ip: address 192.168.112.128 netmask 255.255.255.0 mtu 1500

2) Have you tried to enable the rc.daemons script?
Just rename/copy /etc/rc.daemons.dists to /etc/rc.daemons and reboot.
Basically it will execute:
daemonize talkd
daemonize tcpd shell in.rshd
daemonize tcpd login in.rlogind
daemonize tcpd telnet in.telnetd
daemonize tcpd ftp in.ftpd

wish you luck!

--
http://RahmatM.Samik-Ibrahim.vLSM.org/ -- VauLSMorg

Greg King

unread,
Jan 20, 2010, 2:14:47 PM1/20/10
to minix3
On Jan 18, 4:00 am, Antoine Leca wrote:
> Karthik Urs wrote:
> ...
> > 5. The IP address on Minix and on Windows are in the same subnet.
>
> The 3.1.x ftpd server insists on knowing its client by name -- the numeric IP
> is not sufficient! So, either you must have a DNS server which gives a name to
> the hosting address, or you should fix it in "/etc/hosts".

Wow! Wow! Double wow!! That fixed all of my problems! Before I saw
that, I could connect only some of the time. Even when I did get in,
Minix's FTP server took a long time to respond to the connection
request. But, now that I have attached a name to the host machine's
IP address (in "/etc/hosts"), ftpd connects _immediately_ -- every
time!

Such a small piece of information -- and yet, so vital !!

It _really needs_ to be mentioned in ftpd's manual -- perhaps, in a
NOTES section. If I had seen it there, then I could have saved myself
a "boatload" of aggravation!

Erik van der Kouwe

unread,
Jan 20, 2010, 3:02:18 PM1/20/10
to minix3
Hi,

> It _really needs_ to be mentioned in ftpd's manual -- perhaps, in a
> NOTES section.  If I had seen it there, then I could have saved myself
> a "boatload" of aggravation!

Good idea. Could you propose a text to be added in the man-page? I'd
gladly add it.

Thanks,
Erik

Antoine LECA

unread,
Feb 25, 2013, 3:42:12 AM2/25/13
to min...@googlegroups.com
muhammad holil wrote:
> i start the ftp with this command
>
> intr -d tcpd ftp ftpd.in &
>
> the when i try to connect to it

There are a number of requirement for the old FTP server to work; you
need the directories in place, you need to have non-root users enabled,
you need to have both machines (the server and the client) known by name
(just IP addresses are not enough) so use /etc/hosts!
For anonymous connections, there are even more requirements, but there
the documentation will help you, both the manual and setup.anonftp.

Basically all the details are in the source; you can also start the
server alone on a console (not through tcpd) and recompile the server
with DEBUG, it will print informations on screen about what is happening
which should guide you.

Happy hacking!


Antoine
Reply all
Reply to author
Forward
0 new messages