Tags: bridge

08/04/13

  12:25:00 pm, by The Dreamer   , 633 words  
Categories: Software, Computer, Networking

Apparently my dd-wrt does loopback now

A couple months ago I asked if mosh could be made to work if the mosh-server IP changes when roaming between networks.

Years ago, I used to have routers that did 'loopback', but haven't had ones capable of it for sometime...or so I thought. Though I hadn't really had a major need for it. Except perhaps for mosh.

mosh, MObile SHell, is an ssh replacement that supports roaming and intermittent connectivity. Since I do my IRC using irssi in screen, running all the time on a server at home. This makes staying connected to IRC on my laptop much nicer. I can close my laptop, and later open it and it'll still be connected to my screen session.

The problem was when I came home, I'd be unable to recover the connection correctly and the client goes into an unrecoverable state, so that even if I later use my laptop on an outside network the mosh session won't resume.

But, today I opened my laptop (and I just realized that I didn't do what I had intended to do) and I just minimized the window out the of the way...even though it probably wouldn't recover on Monday at work. But, the dock icon showed that something wanted my attention....probably mosh-client giving up? No. Well, my nick had come up a couple of times yesterday, but it shouldn't have known that....but not really thinking, I switch to the channel. And, it does. I switch around and its working. Wait...it shouldn't be though! :!:

So what changed? I do a tcpdump and see that it is connecting to my WAN IP and getting responses from my WAN IP....'loopback' never worked for me though....

:idea: Perhaps its 'loopback' of port forwards that has never worked....

I had moved irssi from box to dbox a while back. The router has two port forwards set related to this to box, a single port TCP forward and port range UDP forward.

But, because my other router is running stock firmware, it has a limited number of port forwards...so as I was migrating services to cbox (and using nginx to reverse proxy web services on other systems on my home network, where those that use a webserver are using apache, including local services...such as cacti on cbox and nagios on dbox), I decided that I would just make cbox the DMZ host...start running host based firewalls at home, especially on this host (it also uses an IP alias...kind of like how we do hosts behind the BigIP at work &#59;D )

So that means no port forward(s) for my dd-wrt router for WAN to dbox....so I guess the NAT allows 'loopback'ng in this case.

Wonder if the same applies to my other router.

The only problem this causes is that I had plans to replace routers. I actually have a new router to replace the current stock router....though I haven't got anything that really needs to speed upgrade to 802.11ac yet in the room where I using wireless bridging. I also had plans to replace my dd-wrt router, which had started getting unreliable which they seem to do after a while....though it seems to have helped after I deleted old traffic data....

Full story »

02/05/13

  08:10:00 am, by The Dreamer   , 428 words  
Categories: General, Networking

Pinterest supports Internet Censorship

It has been about 20 months since I took the EFF Tor Challenge:

Operate a Tor relay to help Tor users all over the world!

Activists worldwide use Tor to protect their anonymity online and to circumvent Internet censorship. But they all rely on a limited number of user-provided "relays" to protect themselves and communicate with others. Internet users worldwide need your help to make the Tor network stronger and faster, so take the Tor Challenge today!

From this I initially set up two Tor relays....initially one with a limited set of exits and one with no exits (middle relay). For more info see: What is a Tor relay?

But, FreeNode blocks exit relay IPs that could access any of their systems....that includes port 80/http. Instead they run a hidden service that would allow a Tor user to connect to IRC via Tor....and say:

We appreciate your accessing Freenode via the Tor hidden service. If you'd like to help us maintain quality access, please consider providing "middleman" bandwidth to the Tor network. Just set your host up as a Tor server and specify how much bandwidth you want to provide.

I did irssi connecting to the hidden service as an experiment....while waiting for the exit relay block to expire. I continued to run irssi this way for a while, until I got tired of doing so.

Since then, Tor wise, I'm playing around with running an anonymous bridge in AWS.....currently costing under $1 each month on the free tier...for bandwidth overages. I'm wondering what it'll be after my free-tier expires, and what would happen if I were to move to another region. Though I guess its deploy new in another region and remove old, since the images have updated a number of times since my initial deployment that there have already been occasions where my image has had trouble staying current.

And, then recently I got stopped from accessing Pinterest, with "the we've detected a bot!", "because Bots may be resource-intensive and slow down Pinterest for other users."

After some email exchanges, they responded that:

Pinterest blocked access because the IP address originating traffic hosts a public Tor node. If you are knowingly hosting a public Tor node, we cannot ensure continued access if traffic coming through your node is malicious.

But, since its a middle relay, the only traffic originating from my IP address to Pinterest is me. So, they're censoring anybody that supports Tor and its use "as a method for whistleblowers and human rights workers to communicate with journalists"....

Guess, they're a strong supporter of Internet Censorship!

Now instead of subjecting some poor random forum to a long rambling thought, I will try to consolidate those things into this blog where they can be more easily ignored profess to be collected thoughts from my mind.

Latest Poopli Updaters -- http://lkc.me/poop

bloglovin

There are 20 years 7 months 24 days 37 minutes and 44 seconds until the end of time.
And, it has been 4 years 5 months 4 days 13 hours 25 minutes and 12 seconds since The Doctor saved us all from the end of the World!

Search

May 2017
Mon Tue Wed Thu Fri Sat Sun
 << <   > >>
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31        
Google

Linkblog

  XML Feeds

Who's Online?

  • Guest Users: 1
This seal is issued to lawrencechen.net by StopTheHacker Inc.
free blog tool

hosted by
Green Web Hosting! This site hosted by DreamHost.

monitored by
Monitored by eXternalTest
SiteUptime Web Site Monitoring Service
website uptime