search for: 6969

Already try the pre realease 0.3. The rtpeer.rb is working. But I don''t know why is take quite a while to listen only port 6969. The after that start to scan port 6881,6882..etc. After that manage to download the file normally. As usual I run everything in one PC. Azureus, ABC, and rubytorrent. The example on "doc\api.txt" still doesn''t work for me. I am very hapy the rtpeer.rb is working regards Eko

...ver launched inside docker container. Not sure it's iptables bug but same thing for http/https works fine. How to reproduce On host machine: # modprobe nf_conntrack_tftp # sudo iptables -t nat -A PREROUTING -m mac --mac-source <REMOTE DEVICE MAC> -p udp --dport 69 -j REDIRECT --to-port 6969 # echo TEST > /var/tftpboot/hello.txt # docker run -p 6969:69/udp -v /var/tftpboot:/var/tftpboot pghalliday/tftp On device with <REMOTE DEVICE MAC>: # tftp -g -r hello.txt <my ip> Expect: file is downloaded Actual results: "tftp: timeout" System: 4.15.0-52-generic #56...

This patch fixes a typo in MetaInfo.from_stream. Alexander. -------------- next part -------------- Index: rubytorrent/metainfo.rb =================================================================== RCS file: /var/cvs/rubytorrent/rubytorrent/rubytorrent/metainfo.rb,v retrieving revision 1.8 diff -u -r1.8 metainfo.rb --- rubytorrent/metainfo.rb 7 Feb 2005 19:52:53 -0000 1.8 +++

...onf => 9999 my extensions.conf: exten => 9999,1,MeetMe(9999) But : == Parsing '/etc/asterisk/meetme.conf': Found Jun 16 10:33:22 WARNING[12100]: chan_zap.c:916 zt_open: Unable to open '/dev/zap/pseudo': No such file or directory Jun 16 10:33:22 ERROR[12100]: chan_zap.c:6969 chandup: Unable to dup channel: No such file or directory Jun 16 10:33:22 WARNING[12100]: app_meetme.c:227 build_conf: Unable to open pseudo channel - trying device Jun 16 10:33:22 WARNING[12100]: app_meetme.c:230 build_conf: Unable to open pseudo device -- Playing 'conf-invalid' (langu...

Hello everyone. Let me first begin by explaining what I'm trying to do... I have a calling card that has an access number and requires a PIN to be entered and then the number you want to dial, like normal calling cards. So what I have done is assign a local DID which when called, initiates a Dial to the access number of the calling card. Now, I'm having a hard time figuring out how to

...gt;65536, "length"=>76}, "creation date"=>1107759320, "created by"=> "RubyTorrent make-metainfo (http://rubytorrent.rubyforge.org)", "comment"=>"Blah!", "announce"=>"http://localhost:6969"}, @s= #<RubyTorrent::TypedStruct:0x10a3140 @array= {:announce_list=>true, :creation_date=>false, :info=>false, :comment=>false, :announce=>false, :created_by=>false, :encoding=>false}, @coerce= {:announce_list=...

...: matrix [1:25, 1:22277] 1050 1222 1411 1504 1722 ... ..- attr(*, "class")= chr "matrix" $ visual :`data.frame': 8 obs. of 3 variables: ..$ x : num [1:8] 0 1 3 2 3 4 2 1 ..$ y : num [1:8] 1 2 0 1 3 3 2 4 ..$ qerror: num [1:8] 6472 8396 7574 7856 6969 ... $ qerror : num 6e+08 $ init : chr "linear" $ alpha : chr "inverse" $ neigh : chr "bubble" $ topol : chr "hexa" $ alpha0 : num [1:2] 1 0.5 $ radius0 : num [1:2] 5 3 $ rlen : num [1:2] 16 80 $ xdim : num 5 $ ydim : nu...

...FM100 average explanatory.variables$FM100[i]<-mean(FM100[(index-9):index,columnID]) } rm(FM100) print("FM100 variables created") What's in each variable: > numberFires [1] 73 > index_yr 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 .... [index: 346] 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 > index_day [1] 235 > index [1] 7189 > FM100[(index-9):index,columnID] [1] 14.6560 14.3190 13.7730 12.0370 11.1230 10.9360 11....

...TING -i eth1 -p tcp --dport 27960 -j DNAT -- to 192.168.0.13:27960 iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 2037 -j DNAT --to 192.168.0.13:2037 iptables -t nat -A PREROUTING -i eth1 -p udp --dport 2037 -j DNAT --to 192.168.0.13:2037 iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 6969 -j DNAT --to 192.168.0.2:6969 _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

I have a new CentOS 7.4 (recently upgraded to 7.5) system that I have been struggling with in configuring vsftpd for FTPS Implicit (port 990). (The latest instructions I've used are at: https://www.unixmen.com/configure-vsftpd-ssltls-centos-7/) Using Filezilla client, I get: Error: GnuTLS error -15: An unexpected TLS packet was received. Error: Could not connect to

...get subsequently overwriten, as you see in the diagnostic output: [1] "M_ind" int [1:12023] 6952 6953 6954 6957 6958 6959 6962 6963 6964 6965 ... [1] "Q1_ind" int [1:331] 1 2 3 4 5 6 7 8 9 10 ... [1] "Q2_ind" int [1:331] 6952 6957 6962 6963 6964 6965 6966 6967 6968 6969 ... [1] "MS_ind" int [1:3] 15237 15238 15239 [1] "---------------" [1] "M_ind" int [1:3] 15237 15238 15239 [1] "Q1_ind" int [1:3] 15237 15238 15239 [1] "Q2_ind" int [1:3] 15237 15238 15239 [1] "MS_ind" int [1:3] 15237 15238 15239...

Before you jump ahead, yes I do have chan_zap.so loaded.. Call Flow: Asterisk 1 --IAX2--> Asterisk 2 ---> PRI -- Accepting AUTHENTICATED call from 22.22.22.22: > requested format = ulaw, > requested prefs = (), > actual format = ulaw, > host prefs = (ulaw|alaw|gsm), > priority = mine -- Executing

...9;yum > install bittorrent' - > a gui version is also available - 'yum install > bittorrent-gui' > > Then execute btdownloadcurses.py <url to .torrent > file> in a shell. (or > btdownloadgui.py for the gui) You may need to open > ports 6881-6889 and > 6969 if you have tight firewall restrictions. > > The .torrent files are also available on all caosity > mirrors. > > Once again - please leave your downloader running > after the download is > complete (with ports 6881-6889 open) as your > downloader will become part > of t...

...restrictions ... And for now i would not even know whether dovecot has equivalents, nor how to apply this correctly. These are all very capable and highly configurable applications. dovecot for example, i track the source for a couple of years, comes with 568 files changed, 26488 insertions(+), 6969 deletions(-) for my last update (v2.3.10.1 to v2.3.11.3). This is a lot. Thank you. And Ciao! and good night from Germany, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(B...

On 10/13/2017 11:49 AM, Yves Bellefeuille wrote: > Johnny Hughes wrote: > >> How to set up that repository is discussed here: >> >> https://wiki.centos.org/SpecialInterestGroup/AltArch/i386 > > Will torrents be available for the installation ISOs? > Looking at the previous releases, we have not produced torrent files for the i386 releases. We have only done

...sencrypt/live/example.com/fullchain.pem rsa_private_key_file=/etc/letsencrypt/live/example.com/privkey.pem ssl_enable=YES force_local_logins_ssl=NO force_local_data_ssl=NO ssl_tlsv1=YES ssl_sslv2=YES ssl_sslv3=YES # limit pasv ports to range that iptables can check pasv_min_port=6900 pasv_max_port=6969 # added 20120213 to deal with FileZilla 3.5.3 stricter cipher list # see http://forum.filezilla-project.org/viewtopic.php?f=2&t=23275 ssl_ciphers=HIGH dual_log_enable=YES allow_writeable_chroot=YES user_sub_token=$USER

Added an article about shorewall to our site. See it at: http://www.dyersinc.com/linux_stuff.htm Thanks again! Sincerely, Jim Hubbard - Project Manager, V.P. E-mail: jimh@dyersinc.com Dyer''s, Inc. 233 S. Hamilton St., P.O. Box 707 Eden, NC 27288 (336)623-6969 phone (336)627-9898 fax Visit us online at www.dyersinc.com

Hi, Is the tracker for the 5.3-release working properly? The only torrent I see actually downloading is CentOS-5.3-i386-bin-1to6. The other three for the i386 DVD and ditto for x86_64 (cd+dvd) are just sitting there. The availability and the number of connected peers in the swarm for each torrent is rather high though. Do torrent downloads work from a single tracker at centos.org, or are those

...ad the new .torrent file for the ISO set that you are hosting on Bit Torrent ( URL's provided ) 2) shut down the BitTorrent Client 3) replace the old .torrent file with the new .torrent 4) restart the BitTorrent Client The Tracker URL for the new torrents should be at http://torrent.centos.org:6969/<torrentname> . After you have run the update, make sure that the URL has changed to this link. You might want to keep in mind that this process does not require you to download the entire ISO Set again. It will continue to share the files already on your machine. Many thanks to everyone wh...

..., but none of the sites have the file. The Linux RPM files are there though. Just thought you'd like to know, if you don't already. MB -- Mike Brown (mbrown at adacgeo.com) (Soon to be: Michael.L.Brown at Philips.com) ADAC, Madison, WI (Philips Radiation Oncology Systems) Desk: 608-288-6969 Fax: 608-298-2101 You design it, I'll build it!