[freenet-support] Re: No inbound connections - can't see specified port listening?
>From: Bob >Subject: Re: No inbound connections - can't see specified port listening? >Newsgroups: gmane.network.freenet.support >Date: 2006-01-11 01:02:35 GMT (1 hour and 26 minutes ago) > > ...> writes: >-- big snip -- >> But I don't get incoming connections? Netstat doesn't show anything >> listening on port 443. Is this normal for freenet? >> > >No. It sounds like freenet is failing to bind the listenport, probably because >it's already in use, or manages to do so but then crashes during startup (can >happen e.g. with buggy JVMs or big datastores and the default heap size.) Even >with no connections at all freenet should "work" in that you should be able to >open the Web Interface page (right-click the system tray bunny.) If you can't >even do that a full 10 mins after starting it then one of the above has >>happened. > >What does the end of freenet.log say? IIRC you can access this via the system >tray bunny, or just find it in the main program directory. Random crashes >probably indicate that your datastore is huge and the heap size needs >increasing, or that you have a buggy Java version (not very likely, anything >1.4.2+ should be OK.) > >Bob > Hi, My freenet does run - I get outbound connections fine. I no longer get inbound connections however. Nothing on this machine indicates that the listen port is already bound - netstat not showing it anyway, and as far as I know there is no other software running that is listening to the internet connection (a scan of this machine from another does not show anything on port 443). I ran freenet for about 12 hours back on dial-up connection and get inbound connections fine - although it appears freenet is listening on port 64620 and not 443 as requested in .ini file from what I can make of output below. 'Netstat -anb' output is: TCP0.0.0.0:8481 0.0.0.0:0 LISTENING 3004 [javaw.exe] TCP0.0.0.0: 0.0.0.0:0 LISTENING 3004 [javaw.exe] TCP0.0.0.0:8891 0.0.0.0:0 LISTENING 3004 [javaw.exe] TCP0.0.0.0:64620 0.0.0.0:0 LISTENING 3004 [javaw.exe] Start of freenet.log has following if it gives clues to anyone: 11/01/2006 22:58:54 (freenet.node.Main, main, NORMAL): Starting Freenet (Fred) 0.5 node, build #5106 on JVM Sun Microsystems Inc.:Java HotSpot(TM) Client VM:1.5.0_01-b08 os.arch = x86 Loading native... Attempting to load freenet/support/CPUInformation/jcpuid-x86-windows.dll Written to H:\TEMP\jcpuid26520lib.tmp: 40960 INFO: Native CPUID library 'freenet/support/CPUInformation/jcpuid-x86-windows.dll' loaded from resource INFO: Optimized native BigInteger library 'net/i2p/util/jbigi-windows-pentium3.dll' loaded from resource 11/01/2006 22:58:58 (freenet.node.Main, main, NORMAL): loading node keys: node 11/01/2006 22:58:58 (freenet.node.Main, main, NORMAL): Read node file 11/01/2006 22:58:59 (freenet.node.Main, main, NORMAL): starting filesystem 11/01/2006 22:59:19 (freenet.node.Main, main, NORMAL): loading data store 11/01/2006 22:59:19 (freenet.node.Main, main, NORMAL): loading routing table 11/01/2006 22:59:21 (freenet.node.Main, main, NORMAL): From output: 49152.0 11/01/2006 22:59:21 (freenet.node.Main, main, NORMAL): Setting default initTransferRate to 49152.0 11/01/2006 22:59:29 (freenet.node.rt.NGRoutingTable, main, ERROR): Caught java.io.IOException: Value out of range: 360.05 deserializing a NodeEstimator for DataObjectRoutingMemory:tcp/:47115, sessions=1, presentations=3, ID=DSA(8010 28b9 634c 7110 b73d fd81 ffc5 e3dc e4ae 60cb), version=Fred,0.5,STABLE-1.51,5106:801028b9634c7110b73dfd81ffc5e3dce4ae60cb java.io.IOException: Value out of range: 360.05 at freenet.node.rt.BootstrappingDecayingRunningAverage.(BootstrappingDecayingRunningAverage.java:167) at freenet.node.rt.BootstrappingDecayingRunningAverageFactory.create(BootstrappingDecayingRunningAverageFactory.java:36) at freenet.node.rt.StandardNodeEstimator.(StandardNodeEstimator.java:525) at freenet.node.rt.StandardNodeEstimatorFactory.create(StandardNodeEstimatorFactory.java:95) at freenet.node.rt.NGRoutingTable.loadEstimators(NGRoutingTable.java:350) at freenet.node.rt.NGRoutingTable.(NGRoutingTable.java:315) at freenet.node.Main.main(Main.java:785) 11/01/2006 22:59:31 (freenet.node.Main, main, NORMAL): Created new NGRT 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): Loaded stats 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): loading temp bucket factory 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): loaded temp bucket factory 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): Loaded bucket factory 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): not seeding routing table 11/01/2006 22:59:34 (freenet.node.Main, main, NORMAL): starting node 11/01/2006 22:59:34 (freenet.node.Main, main, NORMAL): loading service: mainport
[freenet-support] Re: No inbound connections - can't see specified port listening?
On Wed, 2006-01-11 at 09:30 +1300, bryces at paradise.net.nz wrote: > > > > Hi, > > > > I'm using freenet build 5106 on a Windows XP pc. > > > > I use to connect over dial up modem and used dynamic dns for my address and > > had > > my listen port set to 13222. > > > > I now have a fixed ip address (still using dynamic dns) but pc is behind a > > router with only a few incoming ports open that I can't modify. > > > > So I modified my listen port to 443 (one of the open ports on router). > > > > But I never get incoming connections. > > > > If I run 'netstat -an' I do not see anything listening on port 443. Are you running Freenet using a privileged user like Administrator ? If not, I think that a normal user process cannot bind a port under 1024 (a system port) Consider that runnig Freenet as privileged user is normally a Real Bad Idea HTH > > > > Is this normal, or does this explain why I get no inbound connections? > > > > What do I have to do to get freenet to listen on port 443, other than having > > changed 'listenport=443' in freenet.ini and restart freenet? > > > > Regards, > > Bryce S. > > > > > > -------------- > > > > Message: 2 > > Date: Tue, 10 Jan 2006 21:12:09 +1300 > > From: "MailMe" > > Subject: Re: [freenet-support] No inbound connections - can't see > > specified port listening? > > To: support at freenetproject.org > > Message-ID: > > > > > >>At 11:25 a.m. 10/01/2006, Bruce wrote: > >>Hi, > >> > >>I'm using freenet build 5106 on a Windows XP pc. > >> > >>I use to connect over dial up modem and used dynamic dns for my address and > had my listen port set to 13222. > >>I now have a fixed ip address (still using dynamic dns) but pc is behind a > router with only a few incoming ports open that I can't modify. > >> > >>So I modified my listen port to 443 (one of the open ports on router). > >> > >>But I never get incoming connections. > >> > >>If I run 'netstat -an' I do not see anything listening on port 443. > >> > >>Is this normal, or does this explain why I get no inbound connections? > >> > >>What do I have to do to get freenet to listen on port 443, other than having > changed 'listenport=443' in freenet.ini and restart freenet? > > > > if you're using a router then you not only need to open the ports, you need > > to > pinhole or forward them to the local ip of the computer running freenet. the > fact that you can't open any ports suggests however you won't be able to > forward > any ports and it is quite unlikely there are any existing forwarded ports > going > to the right ip. you can look for a dmz option but your router sounds rather > crap so i doubt it will have any. if you have control over the router, it > would > be wise to consider an upgrade to a better router. given the proliferation of > p2p the vast majority of routers, including adsl routers do not have such > bizarre limitations as you router. in fact, better quality routers have pppoa > passthrough which is better then dmz and useful if you want to set up an > external router or if you have a properly firewalled single computer and don't > mind connecting directly. > > > > i see you are using paradise. perhaps this means you are using cable. if > > so, i > believe you just need a good router which should be able to connect directly > to > your cable modem. in fact, i think you should be able to connect directly > which > you might want to consider if you have a properly firewalled single computer. > this would not be an option if you have multiple computers. in this case, your > only option would be to invest in a better router. they're so cheap nowadays > there is no excuse for having such a lousy router. > > > > of course, if you have the know-how and a spare old computer, you could make > this into a dedicated router. > > > > if for some reason you're not willing, your only option would be to wait for > freenet 0.7 although you still shouldn't expect things to be as good as if you > had an open connection or to give up on freenet. > > > > finally i sent this before but it didn't seem to get through. since you're > from nz your upstream might be qutie low. i'm not sure whether cable is the > same > as the lousy telecom adsl but if it is this means its 128k upstream. so make > sure you set your upstream bandwidth limit to perhaps no more then 13kbytes/s, > probably less. also, be wary. the nature of freenet is
[freenet-support] Re: No inbound connections - can't see specified port listening?
> > Hi, > > I'm using freenet build 5106 on a Windows XP pc. > > I use to connect over dial up modem and used dynamic dns for my address and > had > my listen port set to 13222. > > I now have a fixed ip address (still using dynamic dns) but pc is behind a > router with only a few incoming ports open that I can't modify. > > So I modified my listen port to 443 (one of the open ports on router). > > But I never get incoming connections. > > If I run 'netstat -an' I do not see anything listening on port 443. > > Is this normal, or does this explain why I get no inbound connections? > > What do I have to do to get freenet to listen on port 443, other than having > changed 'listenport=443' in freenet.ini and restart freenet? > > Regards, > Bryce S. > > > -- > > Message: 2 > Date: Tue, 10 Jan 2006 21:12:09 +1300 > From: "MailMe" > Subject: Re: [freenet-support] No inbound connections - can't see > specified port listening? > To: support at freenetproject.org > Message-ID: > > >>At 11:25 a.m. 10/01/2006, Bruce wrote: >>Hi, >> >>I'm using freenet build 5106 on a Windows XP pc. >> >>I use to connect over dial up modem and used dynamic dns for my address and had my listen port set to 13222. >>I now have a fixed ip address (still using dynamic dns) but pc is behind a router with only a few incoming ports open that I can't modify. >> >>So I modified my listen port to 443 (one of the open ports on router). >> >>But I never get incoming connections. >> >>If I run 'netstat -an' I do not see anything listening on port 443. >> >>Is this normal, or does this explain why I get no inbound connections? >> >>What do I have to do to get freenet to listen on port 443, other than having changed 'listenport=443' in freenet.ini and restart freenet? > > if you're using a router then you not only need to open the ports, you need to pinhole or forward them to the local ip of the computer running freenet. the fact that you can't open any ports suggests however you won't be able to forward any ports and it is quite unlikely there are any existing forwarded ports going to the right ip. you can look for a dmz option but your router sounds rather crap so i doubt it will have any. if you have control over the router, it would be wise to consider an upgrade to a better router. given the proliferation of p2p the vast majority of routers, including adsl routers do not have such bizarre limitations as you router. in fact, better quality routers have pppoa passthrough which is better then dmz and useful if you want to set up an external router or if you have a properly firewalled single computer and don't mind connecting directly. > > i see you are using paradise. perhaps this means you are using cable. if so, i believe you just need a good router which should be able to connect directly to your cable modem. in fact, i think you should be able to connect directly which you might want to consider if you have a properly firewalled single computer. this would not be an option if you have multiple computers. in this case, your only option would be to invest in a better router. they're so cheap nowadays there is no excuse for having such a lousy router. > > of course, if you have the know-how and a spare old computer, you could make this into a dedicated router. > > if for some reason you're not willing, your only option would be to wait for freenet 0.7 although you still shouldn't expect things to be as good as if you had an open connection or to give up on freenet. > > finally i sent this before but it didn't seem to get through. since you're from nz your upstream might be qutie low. i'm not sure whether cable is the same as the lousy telecom adsl but if it is this means its 128k upstream. so make sure you set your upstream bandwidth limit to perhaps no more then 13kbytes/s, probably less. also, be wary. the nature of freenet is that it is always transferring data in & out. if as with many nzers, you only have 10gb, your quota may quickly disappear if you're not careful. you might want to limit you upstream and downstream further (if you have a 2mbit connection, it's probably a good idea to limit it just in case). watch your quota carefully. if you want to use freenet efficiently, you should consider adsl with one of the ihug plans with a 'high' data allowance, perhaps the 40gb/40gb one. > Hi, I don't need port forwarding - I have 'internet' address at pc (no NAT). Router is cisco 1600 connected to 2mbit/sec frame relay circuit. Router acts as initial filter of incoming traffic - the address I am using was a spare for another web server so it is configured at the router to only let in commonly used web server ports (eg. 21, 80, 443). But I don't get incoming connections? Netstat doesn't show anything listening on port 443. Is this normal for freenet? Many thanks, Bryce S.
[freenet-support] Re: No inbound connections - can't see specified port listening?
writes: -- big snip -- > But I don't get incoming connections? Netstat doesn't show anything > listening on port 443. Is this normal for freenet? > No. It sounds like freenet is failing to bind the listenport, probably because it's already in use, or manages to do so but then crashes during startup (can happen e.g. with buggy JVMs or big datastores and the default heap size.) Even with no connections at all freenet should "work" in that you should be able to open the Web Interface page (right-click the system tray bunny.) If you can't even do that a full 10 mins after starting it then one of the above has happened. What does the end of freenet.log say? IIRC you can access this via the system tray bunny, or just find it in the main program directory. Random crashes probably indicate that your datastore is huge and the heap size needs increasing, or that you have a buggy Java version (not very likely, anything 1.4.2+ should be OK.) Bob
Re: [freenet-support] Re: No inbound connections - can't see specified port listening?
On Wed, 2006-01-11 at 09:30 +1300, [EMAIL PROTECTED] wrote: Hi, I'm using freenet build 5106 on a Windows XP pc. I use to connect over dial up modem and used dynamic dns for my address and had my listen port set to 13222. I now have a fixed ip address (still using dynamic dns) but pc is behind a router with only a few incoming ports open that I can't modify. So I modified my listen port to 443 (one of the open ports on router). But I never get incoming connections. If I run 'netstat -an' I do not see anything listening on port 443. Are you running Freenet using a privileged user like Administrator ? If not, I think that a normal user process cannot bind a port under 1024 (a system port) Consider that runnig Freenet as privileged user is normally a Real Bad Idea HTH Is this normal, or does this explain why I get no inbound connections? What do I have to do to get freenet to listen on port 443, other than having changed 'listenport=443' in freenet.ini and restart freenet? Regards, Bryce S. -- Message: 2 Date: Tue, 10 Jan 2006 21:12:09 +1300 From: MailMe [EMAIL PROTECTED] Subject: Re: [freenet-support] No inbound connections - can't see specified port listening? To: support@freenetproject.org Message-ID: [EMAIL PROTECTED] At 11:25 a.m. 10/01/2006, Bruce wrote: Hi, I'm using freenet build 5106 on a Windows XP pc. I use to connect over dial up modem and used dynamic dns for my address and had my listen port set to 13222. I now have a fixed ip address (still using dynamic dns) but pc is behind a router with only a few incoming ports open that I can't modify. So I modified my listen port to 443 (one of the open ports on router). But I never get incoming connections. If I run 'netstat -an' I do not see anything listening on port 443. Is this normal, or does this explain why I get no inbound connections? What do I have to do to get freenet to listen on port 443, other than having changed 'listenport=443' in freenet.ini and restart freenet? if you're using a router then you not only need to open the ports, you need to pinhole or forward them to the local ip of the computer running freenet. the fact that you can't open any ports suggests however you won't be able to forward any ports and it is quite unlikely there are any existing forwarded ports going to the right ip. you can look for a dmz option but your router sounds rather crap so i doubt it will have any. if you have control over the router, it would be wise to consider an upgrade to a better router. given the proliferation of p2p the vast majority of routers, including adsl routers do not have such bizarre limitations as you router. in fact, better quality routers have pppoa passthrough which is better then dmz and useful if you want to set up an external router or if you have a properly firewalled single computer and don't mind connecting directly. i see you are using paradise. perhaps this means you are using cable. if so, i believe you just need a good router which should be able to connect directly to your cable modem. in fact, i think you should be able to connect directly which you might want to consider if you have a properly firewalled single computer. this would not be an option if you have multiple computers. in this case, your only option would be to invest in a better router. they're so cheap nowadays there is no excuse for having such a lousy router. of course, if you have the know-how and a spare old computer, you could make this into a dedicated router. if for some reason you're not willing, your only option would be to wait for freenet 0.7 although you still shouldn't expect things to be as good as if you had an open connection or to give up on freenet. finally i sent this before but it didn't seem to get through. since you're from nz your upstream might be qutie low. i'm not sure whether cable is the same as the lousy telecom adsl but if it is this means its 128k upstream. so make sure you set your upstream bandwidth limit to perhaps no more then 13kbytes/s, probably less. also, be wary. the nature of freenet is that it is always transferring data in out. if as with many nzers, you only have 10gb, your quota may quickly disappear if you're not careful. you might want to limit you upstream and downstream further (if you have a 2mbit connection, it's probably a good idea to limit it just in case). watch your quota carefully. if you want to use freenet efficiently, you should consider adsl with one of the ihug plans with a 'high' data allowance, perhaps the 40gb/40gb one. Hi, I don't need port forwarding - I have 'internet' address at pc (no NAT). Router is cisco 1600 connected to 2mbit/sec frame relay circuit. Router acts as initial filter of incoming traffic - the address I am using was a spare
[freenet-support] Re: No inbound connections - can't see specified port listening?
From: Bob [EMAIL PROTECTED] Subject: Re: No inbound connections - can't see specified port listening? Newsgroups: gmane.network.freenet.support Date: 2006-01-11 01:02:35 GMT (1 hour and 26 minutes ago) bryces at ... writes: -- big snip -- But I don't get incoming connections? Netstat doesn't show anything listening on port 443. Is this normal for freenet? No. It sounds like freenet is failing to bind the listenport, probably because it's already in use, or manages to do so but then crashes during startup (can happen e.g. with buggy JVMs or big datastores and the default heap size.) Even with no connections at all freenet should work in that you should be able to open the Web Interface page (right-click the system tray bunny.) If you can't even do that a full 10 mins after starting it then one of the above has happened. What does the end of freenet.log say? IIRC you can access this via the system tray bunny, or just find it in the main program directory. Random crashes probably indicate that your datastore is huge and the heap size needs increasing, or that you have a buggy Java version (not very likely, anything 1.4.2+ should be OK.) Bob Hi, My freenet does run - I get outbound connections fine. I no longer get inbound connections however. Nothing on this machine indicates that the listen port is already bound - netstat not showing it anyway, and as far as I know there is no other software running that is listening to the internet connection (a scan of this machine from another does not show anything on port 443). I ran freenet for about 12 hours back on dial-up connection and get inbound connections fine - although it appears freenet is listening on port 64620 and not 443 as requested in .ini file from what I can make of output below. 'Netstat -anb' output is: TCP0.0.0.0:8481 0.0.0.0:0 LISTENING 3004 [javaw.exe] TCP0.0.0.0: 0.0.0.0:0 LISTENING 3004 [javaw.exe] TCP0.0.0.0:8891 0.0.0.0:0 LISTENING 3004 [javaw.exe] TCP0.0.0.0:64620 0.0.0.0:0 LISTENING 3004 [javaw.exe] Start of freenet.log has following if it gives clues to anyone: 11/01/2006 22:58:54 (freenet.node.Main, main, NORMAL): Starting Freenet (Fred) 0.5 node, build #5106 on JVM Sun Microsystems Inc.:Java HotSpot(TM) Client VM:1.5.0_01-b08 os.arch = x86 Loading native... Attempting to load freenet/support/CPUInformation/jcpuid-x86-windows.dll Written to H:\TEMP\jcpuid26520lib.tmp: 40960 INFO: Native CPUID library 'freenet/support/CPUInformation/jcpuid-x86-windows.dll' loaded from resource INFO: Optimized native BigInteger library 'net/i2p/util/jbigi-windows-pentium3.dll' loaded from resource 11/01/2006 22:58:58 (freenet.node.Main, main, NORMAL): loading node keys: node 11/01/2006 22:58:58 (freenet.node.Main, main, NORMAL): Read node file 11/01/2006 22:58:59 (freenet.node.Main, main, NORMAL): starting filesystem 11/01/2006 22:59:19 (freenet.node.Main, main, NORMAL): loading data store 11/01/2006 22:59:19 (freenet.node.Main, main, NORMAL): loading routing table 11/01/2006 22:59:21 (freenet.node.Main, main, NORMAL): From output: 49152.0 11/01/2006 22:59:21 (freenet.node.Main, main, NORMAL): Setting default initTransferRate to 49152.0 11/01/2006 22:59:29 (freenet.node.rt.NGRoutingTable, main, ERROR): Caught java.io.IOException: Value out of range: 360.05 deserializing a NodeEstimator for DataObjectRoutingMemory:tcp/ip-address:47115, sessions=1, presentations=3, ID=DSA(8010 28b9 634c 7110 b73d fd81 ffc5 e3dc e4ae 60cb), version=Fred,0.5,STABLE-1.51,5106:801028b9634c7110b73dfd81ffc5e3dce4ae60cb java.io.IOException: Value out of range: 360.05 at freenet.node.rt.BootstrappingDecayingRunningAverage.init(BootstrappingDecayingRunningAverage.java:167) at freenet.node.rt.BootstrappingDecayingRunningAverageFactory.create(BootstrappingDecayingRunningAverageFactory.java:36) at freenet.node.rt.StandardNodeEstimator.init(StandardNodeEstimator.java:525) at freenet.node.rt.StandardNodeEstimatorFactory.create(StandardNodeEstimatorFactory.java:95) at freenet.node.rt.NGRoutingTable.loadEstimators(NGRoutingTable.java:350) at freenet.node.rt.NGRoutingTable.init(NGRoutingTable.java:315) at freenet.node.Main.main(Main.java:785) 11/01/2006 22:59:31 (freenet.node.Main, main, NORMAL): Created new NGRT 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): Loaded stats 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): loading temp bucket factory 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): loaded temp bucket factory 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): Loaded bucket factory 11/01/2006 22:59:32 (freenet.node.Main, main, NORMAL): not seeding routing table 11/01/2006 22:59:34 (freenet.node.Main, main, NORMAL): starting node 11/01/2006 22:59:34 (freenet.node.Main, main, NORMAL): loading
[freenet-support] Re: No inbound connections - can't see specified port listening?
Hi, I'm using freenet build 5106 on a Windows XP pc. I use to connect over dial up modem and used dynamic dns for my address and had my listen port set to 13222. I now have a fixed ip address (still using dynamic dns) but pc is behind a router with only a few incoming ports open that I can't modify. So I modified my listen port to 443 (one of the open ports on router). But I never get incoming connections. If I run 'netstat -an' I do not see anything listening on port 443. Is this normal, or does this explain why I get no inbound connections? What do I have to do to get freenet to listen on port 443, other than having changed 'listenport=443' in freenet.ini and restart freenet? Regards, Bryce S. -- Message: 2 Date: Tue, 10 Jan 2006 21:12:09 +1300 From: MailMe [EMAIL PROTECTED] Subject: Re: [freenet-support] No inbound connections - can't see specified port listening? To: support@freenetproject.org Message-ID: [EMAIL PROTECTED] At 11:25 a.m. 10/01/2006, Bruce wrote: Hi, I'm using freenet build 5106 on a Windows XP pc. I use to connect over dial up modem and used dynamic dns for my address and had my listen port set to 13222. I now have a fixed ip address (still using dynamic dns) but pc is behind a router with only a few incoming ports open that I can't modify. So I modified my listen port to 443 (one of the open ports on router). But I never get incoming connections. If I run 'netstat -an' I do not see anything listening on port 443. Is this normal, or does this explain why I get no inbound connections? What do I have to do to get freenet to listen on port 443, other than having changed 'listenport=443' in freenet.ini and restart freenet? if you're using a router then you not only need to open the ports, you need to pinhole or forward them to the local ip of the computer running freenet. the fact that you can't open any ports suggests however you won't be able to forward any ports and it is quite unlikely there are any existing forwarded ports going to the right ip. you can look for a dmz option but your router sounds rather crap so i doubt it will have any. if you have control over the router, it would be wise to consider an upgrade to a better router. given the proliferation of p2p the vast majority of routers, including adsl routers do not have such bizarre limitations as you router. in fact, better quality routers have pppoa passthrough which is better then dmz and useful if you want to set up an external router or if you have a properly firewalled single computer and don't mind connecting directly. i see you are using paradise. perhaps this means you are using cable. if so, i believe you just need a good router which should be able to connect directly to your cable modem. in fact, i think you should be able to connect directly which you might want to consider if you have a properly firewalled single computer. this would not be an option if you have multiple computers. in this case, your only option would be to invest in a better router. they're so cheap nowadays there is no excuse for having such a lousy router. of course, if you have the know-how and a spare old computer, you could make this into a dedicated router. if for some reason you're not willing, your only option would be to wait for freenet 0.7 although you still shouldn't expect things to be as good as if you had an open connection or to give up on freenet. finally i sent this before but it didn't seem to get through. since you're from nz your upstream might be qutie low. i'm not sure whether cable is the same as the lousy telecom adsl but if it is this means its 128k upstream. so make sure you set your upstream bandwidth limit to perhaps no more then 13kbytes/s, probably less. also, be wary. the nature of freenet is that it is always transferring data in out. if as with many nzers, you only have 10gb, your quota may quickly disappear if you're not careful. you might want to limit you upstream and downstream further (if you have a 2mbit connection, it's probably a good idea to limit it just in case). watch your quota carefully. if you want to use freenet efficiently, you should consider adsl with one of the ihug plans with a 'high' data allowance, perhaps the 40gb/40gb one. Hi, I don't need port forwarding - I have 'internet' address at pc (no NAT). Router is cisco 1600 connected to 2mbit/sec frame relay circuit. Router acts as initial filter of incoming traffic - the address I am using was a spare for another web server so it is configured at the router to only let in commonly used web server ports (eg. 21, 80, 443). But I don't get incoming connections? Netstat doesn't show anything listening on port 443. Is this normal for freenet? Many thanks, Bryce S. ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http
[freenet-support] Re: No inbound connections - can't see specified port listening?
[EMAIL PROTECTED] writes: -- big snip -- But I don't get incoming connections? Netstat doesn't show anything listening on port 443. Is this normal for freenet? No. It sounds like freenet is failing to bind the listenport, probably because it's already in use, or manages to do so but then crashes during startup (can happen e.g. with buggy JVMs or big datastores and the default heap size.) Even with no connections at all freenet should work in that you should be able to open the Web Interface page (right-click the system tray bunny.) If you can't even do that a full 10 mins after starting it then one of the above has happened. What does the end of freenet.log say? IIRC you can access this via the system tray bunny, or just find it in the main program directory. Random crashes probably indicate that your datastore is huge and the heap size needs increasing, or that you have a buggy Java version (not very likely, anything 1.4.2+ should be OK.) Bob ___ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
