DD-WRT and Cox-- any warnings?

[Dan Lund]

You'll probably have to deal with cloning the current mac on the WAN port.
I had to with my Belkin, since Cox seems to be doing some twisted form
of MAC checks.

I'm not saying in all cases it does that since I'm not everywhere and
dealing with every customer since I'm just one customer.  However,
I've been a customer of Cox for like 7-8 years and have never had this
problem until 1 year 1/2 ago when I connected in a new house I
purchased.  I just dealt with them by initiating a connection with a
laptop while talking to the nasty tech on the line.  After that, I
just cloned the mac of the nic from that laptop on the Belkin I was
going to use.  After that, all fine.
I know I've spouted about this before, so I'm just throwing this out
again in this situation to inform you :)

--Dan

On Mon, Jun 2, 2008 at 7:56 PM,  <fouldragon at aol.com> wrote:
> Well, I bought one of those $15 bargain Airlink101 routers from Fry's
> in an abortive attempt to fix a poor 802.11g connectivity situation.
> As it turned off, it was something else.  Not wanting to consider it a
> write-off, I installed the new DD-WRT v24 firmware on it.
>
> However, before I drop it in (replacing a second-hand stock firmware
> Linksys WRT54G which I'm powering off a 12v laptop brick I'm really
> coveting for another project) I'm wondering if there are any settings I
> need to adjust to avoid offending the local ISP (in my case, Cox) -- I
> assume that the 'info page' and 'remote management' features might
> count as forbidden 'servers' to them, so I already turned them off, but
> what else?
>
> It's nice having something I can telnet into (since I don't spend
> enough time at a putty window at work)

-- 
Thanks,
Dan Lund