Hi Briand,
>> Just to clear things up, take a look at the vsftpd.conf(5) man page:
>>
>> listen_ipv6
>>Like the listen parameter, except vsftpd will listen on an IPv6
>> socket instead of an IPv4 one. Note that a socket listening on the
>> IPv6 "any" address (::) will accept both IP
On Sun, 05 Jul 2015 16:24:05 -0400
Louis Wust wrote:
> Just to clear things up, take a look at the vsftpd.conf(5) man page:
>
> listen_ipv6
> Like the listen parameter, except vsftpd will listen on an IPv6
> socket instead of an IPv4 one. Note that a socket listening on the
> IPv6
Just to clear things up, take a look at the vsftpd.conf(5) man page:
listen_ipv6
Like the listen parameter, except vsftpd will listen on an IPv6
socket instead of an IPv4 one. Note that a socket listening on the
IPv6 "any" address (::) will accept both IPv6 and IPv4 connections
b
On Sun, 5 Jul 2015 08:55:28 +0200
Petter Adsen wrote:
> Maybe machine2 has no ip6tables rules, or rules that allow the access,
> and machine1 blocks it? Or maybe only machine2 has IPv6 enabled?
>
machine2 is a very recent install directly from jessie.
machine1 is also jessie, but dist-upgrade
On Sat, 4 Jul 2015 15:45:05 -0700
wrote:
> On Sat, 04 Jul 2015 13:55:36 +1000
> Alexis wrote:
>
> >
> > bri...@aracnet.com writes:
> >
> > > just to recap. machine 1 :firewall. i can ftp into machine 2
> > > machine 2: no firewall. i cannot ftp into machine 1
> > >
> > > i tried the iptable
On Sat, 04 Jul 2015 13:55:36 +1000
Alexis wrote:
>
> bri...@aracnet.com writes:
>
> > just to recap. machine 1 :firewall. i can ftp into machine 2
> > machine 2: no firewall. i cannot ftp into machine 1
> >
> > i tried the iptables commands as you explained above, and still
> > get connectio
On Sat, 04 Jul 2015 13:55:36 +1000
Alexis wrote:
>
> bri...@aracnet.com writes:
>
> > just to recap. machine 1 :firewall. i can ftp into machine 2
> > machine 2: no firewall. i cannot ftp into machine 1
> >
> > i tried the iptables commands as you explained above, and still
> > get connectio
bri...@aracnet.com writes:
just to recap. machine 1 :firewall. i can ftp into machine 2
machine 2: no firewall. i cannot ftp into machine 1
i tried the iptables commands as you explained above, and still
get connection refused.
here's the really interesting part.
when logged in on machin
On Fri, 03 Jul 2015 15:55:53 -0400
Louis Wust wrote:
what a terrific reply !
> I think you are asking two netfilter/iptables questions here:
> 1) How to "clear" an iptables configuration so all traffic is allowed?
> 2) How to allow FTP traffic through netfilter/iptables?
>
> Let's address eac
I think you are asking two netfilter/iptables questions here:
1) How to "clear" an iptables configuration so all traffic is allowed?
2) How to allow FTP traffic through netfilter/iptables?
Let's address each question in turn.
#
1. Allowing all traffic, for debugging purposes
#
On Wed,
i've set up vsftpd on a couple of machines
one has a firewall, and one does not.
ftp's to the machine without the firewall work fine.
ftp's to the the machine with the firewall, still from the internal network, do
not.
easy to test, right ? simply disable the firewall and see if it works.
i
11 matches
Mail list logo