Ok, I moved my supernode onto my home lan, forwarded the necessary ports, and got it to work.
I was running my supernode @ vpsland and the only thing I can think of is either they compress traffic or somehow interfere with udp traffic. I'm not sure. Either way, I can ping and RDP my tablet PC that is connected to the 'net via a sprint data card. Nice! C On Sun, Jul 12, 2009 at 12:20 PM, Chris Norman <[email protected]> wrote: > Ok, I'll keep trying without HTTP tunneling. > > I can't get my edge's to register without it unless they're on my local LAN > (which sort of defeats the purpose) :). > > I downloaded the VPN clients from vpnhosting.cz and tested that. I > couldn't get that to work on their supernode either. > > They do, however, have an edge build with no compression. > If anyone has a trunk source that they *know* works plz zip and email. I'll > compare the file to see if there's anything diff. > > I built it using VS2008 on Vista 64 biz. I'll try building on 32bit, but I > seriously doubt it'll make a difference. > > Thanks! > C > > > On Sun, Jul 12, 2009 at 12:18 AM, Richard Andrews > <[email protected]>wrote: > >> The error is (lzoconf.h). >> >> #define LZO_E_INPUT_OVERRUN (-4) >> >> I've never seen it before. I gues something did not build properly. >> >> n2n folks - does anyone out there have a working Windows binary set >> they can provide to Chris to get him going. >> >> Remove http tunnelling (-t). HTTP tunnelling was experimental and >> never worked properly AFAIK. >> >> Can you try the getting started example from the wiki as closely as >> possible. >> >> -- >> Rich >> >> >> On Sun, Jul 12, 2009 at 8:43 AM, Chris Norman<[email protected]> wrote: >> > Ok, I've compiled the trunk and I can run my supernode and edge will >> connect >> > (but only in -t mode). >> > >> > When I connect another edge, the first node dies with this error: >> > >> > >> > >> > C:\n2n2>edge -a 10.1.2.2 -c mynetwork -k encryptme -l xx.yy.zz.aa:8080 >> -t >> > 10.1.2.2 >> > 11/Jul/2009 17:39:55 [ edge.c:1133] Using supernode xx.yy.zz.aa:8080 >> > Open device >> > [name={36EFA202-1526-4E75-9168-356E08EB9ACA}][ip=10.1.2.2][ifName=Lo >> > cal Area Connection 2][MTU=1400][mac=00:FF:36:EF:A2:02] >> > Setting Local Area Connection 2 device address... >> > Ok. >> > >> > Device Local Area Connection 2 set to 10.1.2.2/255.255.255.0 >> > 11/Jul/2009 17:40:01 [ edge.c: 670] Registering with supernode >> > 11/Jul/2009 17:40:01 [ edge.c:1364] >> > 11/Jul/2009 17:40:01 [ edge.c:1365] Ready >> > 11/Jul/2009 17:40:02 [ edge.c:1032] Received REGISTER_ACK from >> remote >> > peer [ >> > ip=0.0.0.0:0] >> > 11/Jul/2009 17:40:02 [ edge.c:1431] STATUS: pending=0, operational=0 >> > 11/Jul/2009 17:40:02 [ n2n.c: 503] WARNING: Failed to decompress >> 221 >> > byte p >> > acket. LZO error=-4 >> > >> > C:\n2n2> >> > >> > >> > >> > Strange ... >> > >> > After this, the edge nodes struggle to connect. >> > >> > I see the nodes register on the server. >> > >> > Does the fact I'm running them both from one network (and therefore >> natted >> > from the same IP) make a difference? >> > >> > I connected my other computer to an open wireless network, and had >> similar >> > results. >> > >> > Thanks in advance for any assistance, >> > C >> _______________________________________________ >> Ntop-dev mailing list >> [email protected] >> http://listgateway.unipi.it/mailman/listinfo/ntop-dev >> > > > > -- > From http://highscalability.com/google-architecture: > A 1,000-fold computer power increase can be had for a 33 times lower cost > if you you use a failure-prone infrastructure rather than an infrastructure > built on highly reliable components. You must build reliability on top of > unreliability for this strategy to work." > -- >From http://highscalability.com/google-architecture: A 1,000-fold computer power increase can be had for a 33 times lower cost if you you use a failure-prone infrastructure rather than an infrastructure built on highly reliable components. You must build reliability on top of unreliability for this strategy to work."
_______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
