Jump to content
SAU Community

Recommended Posts

  • Replies 57
  • Created
  • Last Reply

Top Posters In This Topic

Yer the firewall is off.

I'm behind a router with the ports 6881-6999 open.

As I said its only your tracker that it appears to do it with.. Be buggered if I know.. ;)

Whats this NAT checking disabled bit that is displayed on the stats screen?

Yer who knows.. Computers suck. ;)

I've been fiddling a little tried a few different settings and it just won't connect with a greeny. I've put the modem in to bridge mode, still nothing :D

EDIT: Doesn't matter i've dropped the modem back to its std. PPOA with NAT enabled, sygate firewall on and set the bittornado to use the ports between 6881-6889 with it using its UPnP to automatically forward the required ports. It appears to now be maxing out my upstream. Still no greeny though.

Its a constant connection just not optimal. :D

for green u need someone else to connect to you, which may take a while from when u first jump on.

anyway if ur a seed, then other users with a NAT, if they want the files, will fix their end, so that u can connect to them. only if two users are yellow lighting that they wont be able to connect to each other.

check ur options of ur bt client, and make sure its actually using the ports u have opened. i use azureus

yeah i am. it wouldnt be a problem with the tracker, that nat thing on the tracker is just disabling a nat test it could do (so it doesnt let people with nats connect), nothing more

It appears I may be behind a transparent proxy.

May have to give Node a call and find out for sure as they state they do not use proxy's.

http://btfaq.com/natcheck.pl

This is not reporting my IP address correctly.

The issue I am having only occurs with PHPBT trackers.

The problem has been narrowed down to the use of a PHP tracker and my transparent proxy that internode run. :D

Basically the PHP trackers are unable to sniff out the real IP address.

The other standard trackers are able to sniff this is why I connect everywhere else with a greeny. Until I come across another PHP tracker. ;)

EDIT: Problem found. :D

The PHP tracker Ash is running is on port 80.

hence there is no :6969 in the http://www.ash.veritel.com.au/PHPBTTracker...er/announce.php

If it was running on any port other than 80 it would look like

http://www.ash.veritel.com.au:6969/...er/announce.php

Transparent proxy's work on port 80, this is why no one can connect to me as it is reporting my IP address as the proxy's IP address.

in azureus there is an option to supply ur real ip in the config->server section. check ur client for a similar option, and then supply it ur real ip, and see if that helps.

Ash do you have the GTR manual, not the engine manual and where can i get from if you do

Thanks

BTW....i managed to get the r32 manual(all that i was after) last night Very very slowly.

Edit: No Worries got it all now.....R32 Service manual, R32 Gtr Manual and R32 Wiring digram.

  • 1 month later...

yeah, no-one has it anymore...

Do you know of anywhere else that is hosting it.

I don't have an R33 but I am looking to incorporate the four manuals and make it easier to navigate for everyone.

I am in the process of getting an R34 Manual translated through a friend in Japan.

it would kinda be pointless without the 33 one also.

I'm also chasing a R32 GTS-T manual if anyone has it and is able to host it, I would be able to download it within a day (would only take me 30 mins once I started)

FTP or HTTP prefered. Otherwise I'd have to use dialup (Can't use torrents at work)

Cheers

Chris

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Have a look at that (shitty) pic I posted. You can see AN -4 braided line coming to a -4 to 1/8 BSPT adapter, into a 1/8 BSPT T piece. The Haltech pressure sender is screwed into the long arm of the sender and factory sender (pre your pic) into the T side. You can also see the cable tie holding the whole contraption in place. Is it better than mounting the sender direct to your engine fitting......yes because it removes that vibration as the engine revs out 50 times every lap and that factory sender is pretty big. Is it necessary for you......well I've got no idea, I just don't like something important failing twice so over-engineer it to the moon!
    • Yup. You can get creative and make a sort of "bracket" with cable ties. Put 2 around the sender with a third passing underneath them strapped down against the sender. Then that third one is able to be passed through some hole at right angles to the orientation of the sender. Or some variation on the theme. Yes.... ummm, with caveats? I mean, the sender is BSP and you would likely have AN stuff on the hose, so yes, there would be the adapter you mention. But the block end will either be 1/8 NPT if that thread is still OK in there, or you can drill and tap it out to 1/4 BSP or NPT and use appropriate adapter there. As it stands, your mention of 1/8 BSPT male seems... wrong for the 1/8 NPT female it has to go into. The hose will be better, because even with the bush, the mass of the sender will be "hanging" off a hard threaded connection and will add some stress/strain to that. It might fail in the future. The hose eliminates almost all such risk - but adds in several more threaded connections to leak from! It really should be tapered, but it looks very long in that photo with no taper visible. If you have it in hand you should be able to see if it tapered or not. There technically is no possibility of a mechanical seal with a parallel male in a parallel female, so it is hard to believe that it is parallel male, but weirder things have happened. Maybe it's meant to seat on some surface when screwed in on the original installation? Anyway, at that thread size, parallel in parallel, with tape and goop, will seal just fine.
    • How do you propose I cable tie this: To something securely? Is it really just a case of finding a couple of holes and ziptying it there so it never goes flying or starts dangling around, more or less? Then run a 1/8 BSP Female to [hose adapter of choice?/AN?] and then the opposing fitting at the bush-into-oil-block end? being the hose-into-realistically likely a 1/8 BSPT male) Is this going to provide any real benefit over using a stainless/steel 1/4 to 1/8 BSPT reducing bush? I am making the assumption the OEM sender is BSPT not BSPP/BSP
    • I fashioned a ramp out of a couple of pieces of 140x35 lumber, to get the bumper up slightly, and then one of these is what I use
    • I wouldn't worry about dissimilar metal corrosion, should you just buy/make a steel replacement. There will be thread tape and sealant compound between the metals. The few little spots where they touch each other will be deep inside the joint, unable to get wet. And the alloy block is much much larger than a small steel fitting, so there is plenty of "sacrificial" capacity there. Any bush you put in there will be dissimilar anyway. Either steel or brass. Maybe stainless. All of them are different to the other parts in the chain. But what I said above still applies.
×
×
  • Create New...