Posts by Banny

    Its nothing more than the fact, that once iv done it that's it, time to try something else.


    It doesn't look that difficult anyway, 220MB isn't fast (ofc it is, but not compared to what is available) virgin do 1GB lines now, but I would imagine you would need a mortgage with that bill.

    Thats what I did every other time, as I couldn't ftp to the box from my main pc. Prolly means ive been doing something I didn't need to everytime, well thats another lesson learnt.


    Going to do it from scratch then see if I can do it the correct (or at least better/more correct) way.

    Ive included the content of my proftd.conf below and I know Ill have missed something daft......


    #
    # /etc/proftpd/proftpd.conf -- This is a basic ProFTPD configuration file.
    # To really apply changes reload proftpd after modifications.
    #


    # Includes DSO modules
    Include /etc/proftpd/modules.conf


    # Set off to disable IPv6 support which is annoying on IPv4 only boxes.
    UseIPv6 on
    # If set on you can experience a longer connection delay in many cases.
    IdentLookups off


    ServerName "Debian"
    ServerType standalone
    DeferWelcome off


    MultilineRFC2228 on
    DefaultServer on
    ShowSymlinks on


    TimeoutNoTransfer 600
    TimeoutStalled 600
    TimeoutIdle 1200


    DisplayLogin welcome.msg
    DisplayChdir .message true
    ListOptions "-l"


    DenyFilter \*.*/


    # Use this to jail all users in their homes
    DefaultRoot ~


    # Users require a valid shell listed in /etc/shells to login.
    # Use this directive to release that constrain.
    RequireValidShell off


    # Port 21 is the standard FTP port.
    Port 21


    # In some cases you have to specify passive ports range to by-pass
    # firewall limitations. Ephemeral ports can be used for that, but
    # feel free to use a more narrow range.
    PassivePorts 49152 65534


    # If your host was NATted, this option is useful in order to
    # allow passive tranfers to work. You have to use your public
    # address and opening the passive ports used on your firewall as well.
    # MasqueradeAddress 1.2.3.4


    # This is useful for masquerading address with dynamic IPs:
    # refresh any configured MasqueradeAddress directives every 8 hours
    <IfModule mod_dynmasq.c>
    # DynMasqRefresh 28800
    </IfModule>


    # To prevent DoS attacks, set the maximum number of child processes
    # to 30. If you need to allow more than 30 concurrent connections
    # at once, simply increase this value. Note that this ONLY works
    # in standalone mode, in inetd mode you should use an inetd server
    # that allows you to limit maximum number of processes per service
    # (such as xinetd)
    MaxInstances 30


    # Set the user and group that the server normally runs at.
    User proftpd
    Group nogroup


    # Umask 022 is a good standard umask to prevent new files and dirs
    # (second parm) from being group and world writable.
    Umask 022 022
    # Normally, we want files to be overwriteable.
    AllowOverwrite on


    # Uncomment this if you are using NIS or LDAP via NSS to retrieve passwords:
    # PersistentPasswd off


    # This is required to use both PAM-based authentication and local passwords
    # AuthOrder mod_auth_pam.c* mod_auth_unix.c


    # Be warned: use of this directive impacts CPU average load!
    # Uncomment this if you like to see progress and transfer rate with ftpwho
    # in downloads. That is not needed for uploads rates.
    #
    # UseSendFile off


    TransferLog /var/log/proftpd/xferlog
    SystemLog /var/log/proftpd/proftpd.log


    <IfModule mod_quotatab.c>
    QuotaEngine off
    </IfModule>


    <IfModule mod_ratio.c>
    Ratios off
    </IfModule>
    <IfModule mod_tls.c>
    TLSEngine on
    TLSLog /var/log/proftpd-tls.log
    TLSProtocol TLSv1


    # Are clients required to use FTP over TLS when talking to this server?
    TLSRequired off


    TLSRSACertificateFile /etc/proftpd/ftpd-rsa.pem
    TLSRSACertificateKeyFile /etc/proftpd/ftpd-rsa-key.pem


    # Authenticate clients that want to use FTP over TLS?
    TLSVerifyClient off
    </IfModule>


    # Delay engine reduces impact of the so-called Timing Attack described in
    # http://security.lss.hr/index.php?page=details&ID=LSS-2004-10-02
    # It is on by default.
    <IfModule mod_delay.c>
    DelayEngine on
    </IfModule>

    Seems hard to get people to participate in these parts, but anyway trying another obvious one.


    What music do people listen to, a lot of people say I have a strange taste in music, ill list a few to get you going


    REM
    Massive Attack
    Pink Flloyd
    Linkin Park
    Rihanna
    Lady Gaga
    Eminem


    right through to your more chavvy stuff like house, hard house, Itallian house, scouse house, techno, hardcore - and no I do not object to mc's.

    Two points, to make -


    As has been said several times, this is where the trust (the most important security) factor comes in.


    and not because of this thread in particular, but because of the need to clarify our position every now and then -


    The staff of this forum, do not promote card sharing, this site is merely to provide information to hobbyist, how you use (or misuse) that information is down to you as an individual and is done so at your own risk.

    That would depend on the setup their end


    Peers - people you share with and they share back
    shares are the actual channels


    1 box = 1 line, except if its a twin tuner (or more) and needs two

    all superhubs are owned by vm and even places that sell them are being clamped down on lol


    do what i did, flashed the second router lol the dir 615


    True, but they are still obtainable, ive got a couple here for an upcoming project.

    if you flash the router with a non vm flash ( for superhub) and a fault comes back out, you will be billed £250 for the router


    Which is why you dont flash your router and get an alternative, or another vm superhub and flash that.

    I think I do, but my opinion seems to differ from yours, yours is more likely to be right but id set it up like this -


    The group number for cachex can be anything but must be unique, both of you can use same number as that relates to your config only.


    I wouldn't put an additional user for cachex, as long as you have a reader which you do and set cachex to 3 for the relevant users (in this example both)


    Thats how I read it at least for a 2 user setup.


    So...


    (ME)
    readers:-
    reader a = local = group 1
    reader b = share = group 2
    reader c = share = group 3
    reader d = cachex3 = can be any but must be unique e.g. 4

    users:-
    user a = me = group 1,2,3,4
    user b = me2 = group 1,2,3,4


    *set cachex flag = 3 for both users



    (FREIND)
    readers:-
    reader a = local = group 1
    reader b = share = group 2
    reader c = cachex3 = (same again, say 4 for convenience)


    users:-
    user a = me = group 1,2, 4
    user b = me2 = group 1,2, 4




    we both want to exchange cache on the local cards only.
    so should it be like this?


    (ME)
    readers:-
    reader a = local = group 1
    reader b = share = group 2
    reader c = share = group 3
    reader d = cachex3 = group 1


    users:-
    user a = me = group 1,2,3,4
    user b = me2 = group 1,2,3,4


    (FREIND)
    readers:-
    reader a = local = group 1
    reader b = share = group 2
    reader c = cachex3 = group 1


    users:-
    user a = me = group 1,2,20
    user b = me2 = group 1,2,20
    user c = cachex3 = group 20


    In the reader setup for cachex you assign which groups you want it to cache from.


    Im sure you more likely to be right, though, so gunna see if I can work out why

    I have for others, either picked up a cheap router or 2nd hand superhub flashed it with dd-wrt and changed the mac address so that for all intents and purposes its the same router as far as Virmin are aware, and should you need an engineer visit at any point.