|
Awaiting sources... after buddy IP search??? Trying to share a few files with a friend -- using LimeWire DIRECT CONNECT -- via IP address: we both can see and browse each other 's shared file list -- AOK! But, when we try to download anything we see in that list, we each have this problem, same on both ends: Queued... then Connecting... then Awaiting sources... forever!!! :confused: :( :confused: :mad: :confused: Please help? What's causing this?? How can we fix it???
|
Has anybody out there been successful with LimeWire DIRECT CONNECT via IP address, while using a DSL modem with built-in FIREWALL? {Specifically: SBC Yahoo! DSL with a 2wire (tm) brand modem} and if so, how did you configure it, please? I am using Windows 2000 Pro. My firewall is set to forward port 6346 to my PC for LimeWire. My firewall IP is 67.124.__.___ My machine IP is 172.16.__.___ -- Connection Type: Ethernet IP Address: 172.16.__.__ IP Address Allocation: DHCP IP Address Type: Private (NAT) -- My LimeWire connection says TURBOCHARGED... sharing 47 files. I have seen many UPLOADS completing in the past... -- while using LimeWire 4.0.x, 4.2.x, ... otherwise, SAME PC, same DSL modem, etc... -- but since upgrading to LimeWire 4.8.1 today, NO uploads have started or completed yet, and I have been connected for two hours, or more. Something seems fishy... UPDATE: Three more hours later, a few dozen guest uploads have been done -- I guess it DOES take awhile for a leaf node to get hooked into the LimeWire/Gnutella ultrapeer network ... Help? Is there any hope to get our IP file transfers going? What to do? |
STILL no joy... Fabion -- Thanks for your response, and the suggestions... good to know it works for someone! Well -- all our parental controls are turned off... Our ISP {SBC Yahoo! DSL} and our DSL modem/firewall vendor {2Wire.net} don't give out much documentation, it seems... But, I did find out -- from some SHAREAZA documentation on the web -- how to set up firewall port forwarding -- just by poking around... SO, our port 6346 firewall handling is all set up, and seems to be working AOK -- evidence: there have been a few dozen successful P2P GUEST uploads completed via LimeWire PRO... after waiting over FOUR hours for the ultrapeers to detect my node... But -- still no joy with LimeWirePRO Direct Connect -- via IP address -- with my friend... WHY???
|
Any LimeWire experts out there willing to try doing a Direct Connect to my IP address for troubleshooting??? |
Just 30 seconds ago I successfully direct connected to you! Audioslave, dave mathews, Serenade, Ciara ft Lil Jon, etc. Sounds like the issue is with your friend's set ups. It is almost impossible to direct connect (DC) if one of you are firewalled (ie: don't have your firewalls properly configured to allow LW full access.) It might also be a modem or router issue. Get your friend to do this test: Bug Report instructions & sample image If it's False then they're firewalled. You should do the test also! I noticed your files are all red under Location column which suggests you're firewalled. Configure firewalls here: http://www.limewire.com/english/content/firewalls.shtml More on DC here: How to Direct Connect, Browse & Chat |
Lord of the Rings -- Thanks!!! I've got "Received incoming this session = TRUE" ... :D Woo hoo !!! I'm running Win2k PRO. With a NAT firewall in my DSL modem/router/WiFi box, why should I run any software firewall, isn't that redundant and excessive??? The only firewall I'm running here is in my SBC home network "2Wire (tm)" DSL/WiFi Modem/Router box -- supplied by my ISP... and it has a NAT firewall, and I've set up port 6346 for my LimeWire usage... lots of this terminology seems misleading for us non-experts... I'm FIREWALLED, since there IS a firewall in my DSL box, yes? ... but as far as LimeWire is concerned, I am NOT firewalled... since I have forwarded port 6346 properly... yes??? I'll ask Dave (the friend who wants to share files) to try the test on his side in a few hours -- and report back here... fortunately, we both have the same ISP, and the same DSL modem/router... and we both stepped through the port 6346 setup together yesterday... so I am ANTICIPATING he will get the SAME result as I just did... unless he is running some extra software firewall... tbd! WHAT THEN??? {i.e. What can we try next, if we both have "Received incoming this session = TRUE" ... but we STILL cannot mutually share our files???} :confused: |
STILL no joy... Here is an update: Tools... Options... Bug Reports... View Example... We now both have this result: Received incoming this session: true We can search each other by IP address, and see the list of files to share... He was able to download only ONE small .mid file from me, AOK! I still could not download anything from him, results: Queued... then Connecting... then Awaiting sources... Just a minute after the first successful DL, he tried to DL a larger file from me, then he also got that result: Awaiting sources... And yet, we both checked and could still see: Received incoming this session: true WTF??? What next??? :confused: :( :confused: :( :confused: We are going to stay connected for a few hours and try again... |
k when I dc'd you I searched under one address but got another under the Location column & they were all in red. There was also another member-mod who dc'd you with same results but neither of us were able to downld from you. Basically what it means is that your devices don't seem to be set up properly! That's realy odd to search under one address but to find you under another address. Very odd & means you're not set up properly. Odd again that if that be the case that we could browse you at all. You manually port forwarded right? You MUST have a static ip for this to work properly. There's definitely something odd about the way you're set up. |
What's the secret to config for DC via DHCP/NAT? Thanks again, Lord of the Rings for your reply. I think we have set up properly (our port 6346 configs look ok.) Look for the AHA below... it explains a possible bug in LimeWire? What's DC? OH, Direct Connect... Both my friend and I use the standard PacBell / SBC Yahoo! DSL / home networking service... Most DSL home networks use DHCP and NAT, not static IP, right? (That's what the standard, popular SBC Yahoo! DSL home networking package offers... DHCP and NAT...) That can work, yes??? How do we get LimeWire PRO Direct Connect to work here??? :confused: The 2Wire (tm) DSL box: We've each set up our 2Wire DSL modem / WiFi / NAT Router / Firewall box supplied by the ISP (SBC) to forward from a public IP addr (like 67.124.60.__) outside the firewall to a PC (at 172.16.1.__) inside the firewall, via TCP port 6346 forwarding. Does that sound OK? I'm doing normal LimeWire searches and downloads AOK, I'm seeing incoming searches AOK, I'm seeing public uploads completing AOK... Right now -- I'm seeing connections with five ultrapeers AOK -- but... there should be MORE than five with LimeWire PRO, yes??? :confused: SOMETIMES, after more than six hours, I've seen like six or more ultrapeers...) :confused: Whenever I reboot my 2Wire box, I'd expect my IP address will change. Otherwise, it seems stable, but I'm not sure how long the DHCP lease time is... probably a few days. Our 2Wire DSL modem/ NAT router's config takes care of mapping port 6346 from the Public IP addr to the Private IP addr automatically, even after a reboot of the 2Wire box. This seems to be a standard, typical home DSL setup, right? IF SO... why are we having LimeWire problems with DIRECT CONNECT and host chat? What's the secret config to make this work? SITUATION: When I setup for DIRECT CONNECT with his host via his public IP addr, it always succeeds. (Both ways, vice versa.) We can each see the list of files on the other host. When we try to do a LimeWire host chat, or BROWSE, it fails. When I try using LimeWire DC to download anything from his host, it fails. (Awaiting sources...) But, one time last nite, he was able to DL one small file from my host, then a minute later, trying with a larger file, the DL failed... AWAITING SOURCES... :confused: Weird??? AHA!!! LimeWire uses his public IP addr (64.168.20.__:6346) when searching his host via DC -- BUT, when trying to CHAT, or BROWSE, {or DL?} LimeWire is using his PRIVATE IP addr (172.16.1.__:6346) AHA!!! -- Could THAT be causing all these problems... hmmm... a LimeWire BUG??? :eek: If it's not a bug in LW, then what's the solution? I could try contacting the second level support for 2Wire (my DSL modem/ NAT router/ firewall box) and see what they say about all this, now that we have some more info to give them... I do not think the ISP support will help us solve any P2P issues... Any other suggestions? Is this a LimeWire bug, or a config issue? Does anyone here know how to config a 2WIRE (tm) DSL box that uses DHCP/NAT for LimeWire Direct Connect? I thought I had done everything right... I'll attach my screen shots from my 2Wire config... if that may help? IS THERE ANY SETUP CHECKLIST for a DHCP/NAT firewall config??? :confused: |
Seems like a bug??? See AHA! in post above... How does this info get to the developer or 2nd level support for a review? It's been 48 hours since I sent a help request to LimeWire PRO support... no reply yet... what's up with that? Can anyone please explain the difference between the FORUM here, and the PRO support? Are there different resources available for help? |
QUESTION: Does LimeWire use TCP, or UDP? That is part of my 2Wire firewall setup... I specified TCP... |
Thanks for explaining that. Here's the user guide for my firewall.... next I will attach some screen shots from my config... hopefully it will reveal what is wrong and what needs to be done to get LimeWire DIRECT CONNECT, and host-chat working... http://support.2wire.com/cgi-bin/two...ted=1054337698 |
1 Attachment(s) We are set up for TCP port 6346 ... what else do we need??? See attached... |
1 Attachment(s) My 2Wire firewall APPLICATION settings... |
1 Attachment(s) My 2Wire firewall advanced settings... 1 of 2 |
1 Attachment(s) My 2Wire firewall advanced settings... 2 of 2 |
1 Attachment(s) Just in case there are any hints here... |
So... anybody have any more hints or clues??? What to try next? What UDP parameters (if any) does LimeWire need??? When I try to add UDP into my firewall settings for LimeWire, the 2Wire config asks for a PORT#. Does UDP and TCP both use the same port number? = 6346 ? |
1 Attachment(s) Ready to try port 6346 with UDP... does this look ok? |
ONE MORE TRY? Will one of the moderators please try to DIRECT CONNECT with my IP and see if you can browse and also download? Please let me know. I've just now enabled port 6346 for both TCP and UDP also ... |
My LW suddenly had some probs so I had to close down. Will be a while before it's up & going. Another member will try. Your public ip is different to yesterday. Your private ip should not be showing to others when using LW which is what's happening. Your setup is not per normal I would argue. So does your ip address show up on your DC search window? Is this your public or private address & is it the same everytime. We'll wait for the other member & until my LW fires up. Oh forgot to reopen lol. :D How many hosts depends. If you're operating as an ultrapeer then you'll have more. |
Fabion DC'd with you & i did also (my downld window hadn't even loaded yet.) I notice you have no chat enabled .. there's no chat icon which is needed for chatting & helps DC work better. that's one of your issues. I still have a snapshot of yesterday & your files are no longer in red & they now show your public address & not your private address. Fabion successfully downlded a file from you on the 3rd attempt (1st 2 went immediately to need more sources as it was yesterday. And had to re-search DC.) I'm not ready to downld yet. * Fabion tells me he is seeing you in red text like happened yesterday & with your private ip. Hmm strange. |
1 Attachment(s) This is what I saw yesterday & today. Notice there's no Chat icon! I am now downlding one of your files at about 13 KB/s! |
I still don't see any chat icon nor is the option available despite several dc searches. I also browsed. odd! |
I started to downld again from you & found I could open a chat window but only from the downld window not from the search results & your chat icon is still not showing. Odd! lol :D Have you checked to see if there's a chat window message waiting for you? But apparently Fabion does see a chat icon. Hmm can't work that one out. lol :D What's even more odd is that one of my DC searches came up the same as yesterday with your results in red & with your 172. address. I notice your connection type changed from modem>cable. |
I just got back from the gym and saw your msgs and chat windows... I left my LimeWire connected. No config changes done here since I posted my last message... now over 3 hours ago. I have been on DSL here for two years now. Not dialup... all these variable results are very puzzling... |
You forwarded a port on your device is that right? So your are not using a static ip right? If you did the normal steps are: 1. Set up a static ip which is very important for it to work. 2. Forward (open) a port for your modem or router. 3. Set LW up for manual port forward under Tools>Option>Advanced>Frirewalls. Or did I misunderstand you? |
What a difference a day makes ... or... a little TCP/IP knowledge is dangerous! 1 Attachment(s) Yesterday: only TCP port 6346 was being forwarded by my firewall. (MY BAD!) Today: both TCP and UDP port 6346 is being forwarded. (Yeah, I fixed it!? Maybe...) SO, the firewall uses NAT (Network Address Translation) and port numbers to map an external, dynamic, PUBLIC IP addr to an internal, STATIC, PRIVATE IP addr. The internal LAN addr starts with 172.... My external, public IP addr changes only if I reboot my DSL modem. It may look like 64... or 67... or ... but never 172... My ISP assigns that addr via DHCP when I reboot my DSL modem. LimeWire remote peer should always use the EXTERNAL addr like 67.124.63.161:6346 and never the internal addr like 172.1*.**.**:6346. SOMETIMES, LimeWire remote peers use the INTERNAL 172... addr, while others are using the EXTERNAL 64... addr. this a bug in LimeWire, or a config problem, or a design problem for a future version of LimeWire so it can support NAT routers/ Firewalls??? More details below... later... |
First, your modem is probably UPnP configurable, meaning that LW can open the port automatically, hence why incomings: true. Second, if you are opening ports, don't forget to open both TCP and UDP as those two protocols are used by LW. Just be sure that UDP is allowed and that should help a lot. SBC could also throttle the P2P traffic, did you called them to ask if they were limiting the Gnutella traffic? Also: the fact that the cha window shows your lan address (172.x.x.x.) is probably a bug, Tell the user sberlin (LW dev) about that. Chat isn't a priority at LW, that's why the function of it is poor and buggy, you would prefer chatting via MSN or AIM. |
Thanks! Yes, UPnP is configured in my DSL box. LW chat is rather nice, lightweight, simple, and clean. AND it shows you the IP addr so you can relate things within LW such as browsing a host whilst chatting... yes? I find it very usable... Meanwhile, the idea that my ISP is doing some throttling could explain the cause of variable results from hour to hour and day to day... hmmm.... yeah... maybe... worth checking on that! There is more than one thing going on here... bugs, config errors, and ISP details... more detailed analysis and reports later! |
Thanks to all for the help! The LimeWire / 2Wire(tm) Home Portal Network / SBC Yahoo! DSL / plot thickens! The mists are clearing... and we may see some light at the end of the tunnel now.... ;) :D :) When my friend has time later today -- he will re-config his firewall + his LimeWire -- with all our new discoveries, and then we will then test, and report back here to concisely document the whole picture... stay tuned! I'll collect and summarize the configs and the results later today, and post here. - Geo |
Dear SBerlin, RE:[list=1][*]Using LimeWire PRO 4.8.1 with [*] SBC-Yahoo!-DSL ISP package, which includes: [*] 2Wire(tm) DSL-Home-Portal-Network (DSL modem / NAT-firewall-router box)...[/list=1]We've been trying to get LimeWire Direct Connect, Search, Download, and Chat etc... working for a few days now... The ongoing story is documented here -- within this very thread... We may have found a small bug or two with LimeWire PRO 4.8.1. I'll take time to concisely document the whole picture... back here later. Stay tuned! Meanwhile...
-- Geo |
Updated firewall configs, LimeWire configs, still NO JOY... Last nite, fabion and I were each able to do DC and DL files from each other! Today, my friend and I have double checked and reconfigured everything we can think of... tried again... still NO JOY! The setup of each 2Wire local gateway: Using 6346 port forwarding: TCP and UDP setup AOK. UPnP enabled. Friends Public IP: 64.172.45.___ Friends Private IP: 172.1*.**.**, inside firewall. My Public IP: 64.172.181.___ My Private IP: 172.1*.**.**, coincidentally same IP in my LAN as friend's in other LAN. (Coincidentally, we use the same ISP = SBC.) The setup of each LimeWire PRO: Options... Advanced... Firewall config: Port= 6346 UPnP enabled. No proxy. The results: We can use Direct Connect and see each other's shared files list AOK! Speed shows Cable/DSL. Four stars. Both sides. AOK! Received incoming this session = true (on both sides, AOK!) We both have 5 ultrapeers, connected for more than 20 minutes. Remaining problems: Try to DOWNLOAD, result: Queued... then: Connecting... then: Waiting for sources... then: Need More Sources... (BOO!) Click on a file in the list, do a Browse host, result: 172.1*.**.**:6346 (BUG?) Cannot do a Host chat, it's grayed out. (Why?) What to try next?
|
Thanks for the detailed info, GeoFan. That does indeed look like a bug in that LimeWire is responding with its private IP address even though it is clearly able to accept incoming connections (both sides say 'true'), so downloading from the search results don't work. As a workaround, if you know how to manually configure your routers for port forwarding, try changing the 'Firewall Config' info to 'Manual Forward' and the port that the router is listening on. In the 'Listening Port' area, make sure that that port is set to the port the router is forwarding to. Generally, it's easiest if both are the same number. For example, LimeWire can be listening on port 6666 -- the router can get requests on port 6666 and forward them to internal IP address at port 6666. Actually -- it looks like you already set up your routers. However, that might be what's causing it to fail. If UPnP on your router works, LimeWire will set it up itself -- but because there's already a setting on the router, UPnP fails and LimeWire doesn't know what's going on. If you remove the settings from the router, that'll let LimeWire handle everything, and may fix it. |
sberlin...thanks for the hints!!! It seems to me like your last paragraph is suggesting that we go back to square one, where this all began, which did not work, so we started mucking around with the 2Wire (DSL firewall) settings...??? Meanwhile... Things are not symmetric... Fabion and I can Browse, CHAT, DL happily. My friend Dave and I ... Direct Connect file list AOK, nothing else works... what's up with that? I think fabion runs an ultrapeer... Yesterday, DC DL worked ONCE (Dave pulled ONE small file from me) but then every try failed every time after that... seems VERY STRANGE!!! |
Buddy (Dave) and me (Geo) have same 2Wire box, same ISP (SBC), Dave runs WinXP, Geo runs Win2kPRO... otherwise, same configs for both of us... For Direct Connect ... {Dave :: Geo} and {Geo :: Dave} --- about 1% of our Direct Connect Download attempts are successful... the other 99% of our Direct Connect Download attempts go like this: Queued.... Connecting.... then A or B... Where :: A=Need more sources... B=Awaiting sources... Same hosts... but random results = A or B... WTF??? What is the DIFFFERENCE between those results??? --- Meanwhile, if we search for some unique files on each other's shared files, it NEVER finds them... Bizarre... However, For fabion<>Geo and Geo<>fabion -- 99% are successful. Bizarre... --- Why is it working Geo<>fabion and also OK for fabion<>Geo... yet, Geo<>Dave and Dave<>Geo = NOGO?? -- SBC <> AKA = AOK! SBC <> SBC = NOGO! WTF? I'm thinking... the clues to a solution may be here somewhere?! LimeWire bug??? ISP problem??? Firewall config issue??? |
I notice you use Shareaza also. Have you considered there might also be an issue b/w using both. Raza will change your magnet default for a start. The last time I tried to DC & downld from you yeterday (for me) I noticed there was a chat icon beside the downld but again, only on the downld window & not the search results. |
LOTR, thanks. I use Shareaza very rarely, mainly for BitTORRENTS, and I have yet to try running it concurrently with LW. Shareaza uses more networks than LimeWire, so it can find files that LimeWire cannot find sometimes... Generally, I think LimeWire is faster for popular files. And, of course, LimeWire runs on more platforms: Windows, Mac, Linux... IF we cannot get LimeWire DC running by tomorrow, we may have to switch to Shareaza, tho... and then try for a refund on LimeWire PRO... :rolleyes: :D IN general, open source will eventually overcome proprietary software!!! Can you alert sberlin on the chat icon stuff? Sberlin does not accept PM or email from users. - Geo |
SBerlin does "NOT" like me contacting him. If he sees your post then he'll see it otherwise ... ??? He is subscribed to the thread I presume so I think he is already aware. As for refund you can view this: http://www.limewire.com/english/content/refund.shtml |
I am STILL WAITING to hear back from LimeWire PRO support on all this... I've sent them three emails in the past four days... they seem to be a BLACK HOLE?! I think there should be an official bug report procedure, but I have not found it yet... after all, LW is not freeware -- it costs $40 per year! (With over a million users... not all paying, tho.) They get to use volunteers here, but they have no 2nd level, back-end support, it seems... odd? I'm impressed with the helpfulness of the volunteers, but where are the experts? We are shooting in the dark, here, and I am getting frustrated with LW!!! DO the BETA testers get better support??? I'm guessing that PRO Support is just for the accounting department... user license issues... I just sent an email to bugs@limewire.com so we will see... |
Did you follow the steps I outlined in my post? What were the results? |
1 Attachment(s) Sorry, sberlin, I see now... I was unclear before about what it was that you are asking us to try... is this it: in Options... Advanced... Firewall config... REMOVE UPnP and then use Manual port forward? Is that what you want us to try??? PLEASE CLARIFY. Quote:
Please explain: do you want us to REMOVE ALL THE 2wire FIREWALL/router SETTINGS, going back to square one on the 2Wire DSL box? That did NOT work before... I'll have to wait till tonite, to test again with Dave... I have put out requests on other forums for anyone with a SBC-Yahoo!-DSL and with a 2Wire DSL box... MEANWHILE, sberlin, is there a BETA version of LW that we can test?? I guess that only makes sense if some bugs have been fixed in this area, or if there is any debug code to test, or more statistics to help, or access to expert help... |
We are preparing a beta. There may be a bug in LimeWire 4.8.1, there may also be a bug in your setup. Please remove any configuration you have done on your router, on both sides, and tell both LimeWire's to use UPnP. See if that works. If it does, great. If not, tell one side to use 'Manual Port Forward' and set the listening port & forwarding port to the same number (like 6666). Then set up that side's router to forward from requests at 6666 to your internal IP address. See if that works. If it does, great. If not, tell the other side to use to use 'Manual Port Forward' and set the listening port & forwarding port to the same number (like 6666). Then set up that side's router to forward from requests at 6666 to your internal IP address. See if that works. If it does, great. If not, we may have a bug. I cannot help further unless I know what happens at each step. Telling me, "I tried this before" won't help. |
OK, we will take it step by step and report our results. SO, is UPnP an alternative scheme to TCP/UDP port forwarding? If/when Dave will cooperate, or if I find a willing tinkerer with SBC DSL+2Wire DSL modem...[list=1][*] Reset DSL modem/firewall to factory defaults, also switch to UPnP in LimeWire, do same for both ends.[*] Test LimeWire Direct Connect Downloads... [*] IF nogo, then on side A: setup manual port forwarding, also setup 2Wire DSL box for TCP/UDP port forwarding, then test.[*] IF still nogo, do same for side B, test.[*] Report all results for each step.[/list=1] OK? Is it ok to use port 6346 (it works AOK for me with others...) or do we need to switch to another port like 6969? Why does the port number matter? ISP throttling maybe? Does not seem to matter for me <> fabion... it's working fine between us... exept the private IP number stuff and chat icon stuff noted already (LW bug). Thanks for your help, sberlin. Let us know when we can test a beta. THE oddest thing here is it worked one time. Then immediately after that, it failed... (Dave<>Geo DC DL) Dave is getting frustrated, wants to try Shareaza... :rolleyes: but we already have a lot of time invested in LimeWire... I want to keep trying, as long as we can get some expert support to tell us what to try... otherwise we are just shooting in the dark... :) :cool: :D :confused: |
Ready to test DC DL, anyone??? sberlin :: I have reset my DSL modem/NAT router to defaults: no more TCP/UDP port forwarding, per your request. I have set LimeWire to UPnP. Ordinary LimeWire DOWNLOADS + UPLOADS seem AOK. PROBLEM: Received incoming this session = false !? So, there may be no hope... ?! Now, I just need someone willing to test DC DL... My buddy Dave is not available till Sunday. I hope to find someone who can duplicate the SBC (ISP) and 2Wire (modem/firewall) config, and test before then. Otherwise further tests for that ISP are on hold till Sunday. |
It seems possible that you are authenticating yourself on startup against your friend running as an ultrapeer (or someone else on SBC Yahoo) and this ISP uses one set of IPs internally whereas the broader internet sees you as a different IP. Could be a multi-IP nat issue and if so, we have never really addressed that issue in LimeWire. Basically the same as having a large corporate network and then the public internet. |
Quote:
|
By authenticate, I mean the communications that you receive back from the ultrapeers that you connect to. Your TCP connection to an ultrapeer reports back the IP address that it sees you as. If you connect to an ultrapeer behind some nat on a private network, it would report one IP address. If you connect to an ultrapeer through a nat, the IP address could be different. So, the question is, does SBC Yahoo have this type of configuration. If it is common, then LimeWire needs to improve its handling of this. I've wanted better private network support for a while. |
Note that this is only an actual problem if the last Gnutella connection it made (like UP->Leaf, Leaf->UP, or UP->UP) was to someone else on your private network. Chances of that consistently being the case are rather small. *We should, though, prevent LW from accepting a 'Remote-IP' address from someone else who has the same class A address. |
Is there any way to make both work and coexist? Like "I'm either at this IP or this IP". |
| All times are GMT -7. The time now is 03:56 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.