Tags: dd-wrt

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 »

01/11/12

  11:24:00 pm, by The Dreamer   , 1720 words  
Categories: Stuff, Software, Networking, Cox HSI

I almost needed to buy a new router...

Link: http://smile.amazon.com/gp/product/B0028ACYEK/ref=as_li_ss_tl?ie=UTF8&tag=la34thdr34chs-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B0028ACYEK

...and I've been eyeballing the WZR-HP-G300NH (not only 300Mbps N instead of 150MBps N, but also gigabit ports...also 64MB of RAM and 32MB of Flash ... up from 32MB & 4MB. Not clear on performance difference between Atheros 7240 and 9130...hopefully something).

Because while the current WHR-HP-GN is a step up from my WRT54GS...the QoS still impacts my throughput by a significant amount. Though not enough to turn off QoS in the meantime.

There have bunch a new builds of dd-wrt last month, but no 2012 releases yet. Big thing seems to be 3.x kernels. But, I tried one of the releases...and it was significantly slower with QOS than the last summer release (Build 17201), which has been doing adequate for me. Seems to get laggy over time, so back to rebooting my routers weekly...which can be annoying, because it takes a long time to become responsive again...and connections get dropped sometimes, especially if its long enough to trigger a new IP. So, I reverted back to 17201, which many other people seem to feel is the current best release. Not sure what functionality future builds are shooting to acquire. I think what I have does almost everything I want. I just want it to be less of a bottle neck when doing QoS.

IE: with the WRT54GS, ~5.5MBps down was the best I could get. And, when I started, I only had 6Mbps down service. But, Cox has been upping the speed on upstream and downstream over time. And, its supposed to be like 20MBps and up to 2Mbps up now. But with QoS on....~5.5Mbps was all I continued see, so I dismissed such claims from Cox.

I'm sure all the college students in the area are don't much to things. At least my DSL is more consistent. Though its only 6Mbps/768kbps, the maximum service tier for DSL here. Apparently, certain units in unit B can get U-Verse...but not all of them and I'm in unit A, so no go. Probably means they're on the box next to Chase Manhattan apartments to the south..rather than the box near CAUMC across the intersection.

I had made my own customization to QoS rules on the WRT54GS, and I had largely developed updated equivalents for the WHR-HP-GN's....the only thing missing is 'connbytes' feature in iptables. The kernel supports connbytes, but the provided iptables command does not. The behavior had changes since Iast used requiring the '--connbytes-dir' and '--connbytes-mode' paramers, but soon figured out that the iptables command had been built standalone, and without the feature.

Pages: 1· 2· 3

11/13/11

  02:49:29 pm, by The Dreamer   , 930 words  
Categories: VoIP, Networking, Cox HSI, AT&T DSL, Broadband, RoadRunner

I guess it was time to replace my WRT54GS routers

Link: http://www.amazon.com/Buffalo-Technology-AirStation-Wireless-WHR-HP-GN/dp/B002WBV37Y/

For quite some time, I've been running WRT54GS routers....that I had hacked to run Sveasoft Alchemy...eventually reaching 1.0 release and then pretty much doing very little to.

Originally, I had gotten a WRT54GS v1.1 that I upgraded, and used with my Roadrunner Cablemodem service. Later word came out that newer WRT54GS had less memory than before, and were switching to non-replaceable OSs. So, I started keeping an eye out for older WRT54GS routers...to get as a spare. One day in a Wal-Mart, I was going through the WRT54GS's on a shelf...when way at the back behind the newer v5 stock, was a v2.0. Well, I had to buy it right then and there.

Later when I moved to Manhattan, KS...I was presented with the opportunity to go dual WAN. Well, wasn't my intent, but I was forced into it. So, not wanting to mess up my 'cable' configs. I set up the backup WRT54GS for DSL use.

And, things have been humming along pretty well, with the two WRT54GS routers and the running of both Cox and AT&T broadband.

That was until last September....I was trying transparent proxy and ended up bricking the WRT54GS for DSL. So, I started looking online for a new router to replace the WRT54GS that would be better than what I had now. One of the key features of Sveasoft is the better QoS...which was important since I was doing a lot of VoIP (having at the time both Lingo and Vonage, since neither had Manhattan, KS numbers...they have since gone away...and its just Broadvoice now. But, I've been thinking of getting another....) But, I had turned of QoS on the cable one, because I found that it was affecting my ability to see the speed improvements that Cox had been making to it. So, I had already started looking at what next after WRT54GS....but now with a bricked router, things were more urgent.

So, what I did was order a pair of Buffalo WHR-HP-GN (with dd-wrt) routers from Amazon, using Amazon Prime...on September 9, 2010.

Full story »

Pages: 1· 2

03/01/10

  06:55:56 am, by The Dreamer   , 72 words  
Categories: Networking, Cox HSI

Will I get a new router or not?

Well, this is interesting....

The best I was getting after the latest Cox speed upgrade was:

But, with Wondershaper(QoS) turned off, I'm now getting speeds like these:

It might be acceptable to stay with my current set up, rather that seek out a new router and learn dd-wrt.

I did add a Hawking Broadband Booster (HBB1) that I got off of eBay to at least try to do some QoS.

Hmmm... :hmm:

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 6 months 25 days 5 hours 34 minutes and 7 seconds until the end of time.
And, it has been 4 years 6 months 2 days 8 hours 28 minutes and 49 seconds since The Doctor saved us all from the end of the World!

Search

June 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    
Google

Linkblog

  XML Feeds

Who's Online?

  • Guest Users: 4
This seal is issued to lawrencechen.net by StopTheHacker Inc.
powered by b2evolution free blog software

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

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