[luckman212]

bump (sorry) : edrikk, any news?

edit: freakily, out of nowhere this started working again for me tonight. I have emailed twitter to ask if they did something on their end, because I have not changed anything here. So weird. Well, glad it's over (for now at least). This does seem to really point to some kind of server-side or intermediate network config issue,

however that still does not explain why this only affects the WRT610N while the same build of DDWRT running on a different piece of hardware was working fine. Oh well, I'll try not to let it keep me awake at night. :roll:

edit #2: I just saw this article, Twitter Hacked by Iranian Cyber Army. Heheh... the timing is a little off, but I wonder if this has something to do with either the original problem, or the fact that it started working again today. Coincidence? who knows...

[luckman212]

well, this morning I woke up and pinched myself to make sure this was still working. and guess what, it wasn't.

back to TCP RESET on all connections to twitter.com

I didn't change a thing. Back to square 1.

[edrikk]

Well, for me, it turned out to be an ISP issue with MY LINE only. I was down for 4 days, and they couldn't get me back up (even though I'm in the middle of a metropolis).

At any rate, I'm back up now, and all is well.

[luckman212]

I wish i believed it was an isp issue, but I am going to have a hard time convincing TimeWarner that its their issue when it works if I directly attach to the modem, as well as if I hook up an off-the-shelf Linksys cheap-o router.

[luckman212]

well, I decided to hook up my laptop directly to the Cable modem, and tested again. Got right thru to twitter no problem. Somehow, Twitter has blacklisted my IP or is able to see the MAC address of my router and has blacklisted THAT(??) never heard of such a thing and they have denied it but that is what I have observed.

I went into DDWRT and cloned the MAC address of my laptop instead, and when I reconnected the router to the Cable Modem It kept the same WAN IP (still thinks that it's my laptop) and whaddya know-- I get thru to twitter without any problem.

Something very fishy going on, but without being able to communicate with the admins @twitter, I doubt I will ever know the real story. In any case, i'm happy for now. Thanks to everyone who offered advice.

edit: update. I did a nvram dump after getting this working using the mac cloning technique above. I did a side-by-side compare to see what the differences were and noticed something odd:

old/non-working:
wan_gateway=68.173.80.1
wan_netmask=255.255.252.0
wan_lease=66469

new/working:
wan_gateway=67.244.14.1
wan_netmask=255.255.254.0
wan_lease=2938

so notice that I get connected to a completely different gateway when I clone my mac. hmmmm...... also, netmask is different and much shorter lease time on the new net. I am going to keep monitoring but this seems to be key.

[Eko]

Where did your 100$ award post go??

I told you to clone WAN MAC exactly 8 days ago... but no, you kept blaming dd-wrt. Anyway, I'm happy that you figured this out. :)

[luckman212]

ah ha... ok eko you got me.
well I kind of forgot so I thought I had figured it out myself

any way, I dont want to be called a cheap scrooge.
so how about we split it down the middle, I send you another US$ 50 donation ??

[Eko]

deal

[luckman212]

ok- done
paypal #0WE79796R2726243S

vesele božične in novoletne praznike !!

[Eko]

[lupine]

+1 Style points to luckman212