Plug (und cox) (fwd)

Mon, 29 Jul 2002 22:30:57 -0700

er 192.168.100.x

anthony
----- Original Message -----
From: "tickticker" <tickticker@cox.net>
To: <plug-discuss@lists.plug.phoenix.az.us>
Sent: Monday, July 29, 2002 3:49 PM
Subject: Re: Plug (und cox) (fwd)


> In fact, it's a fact.  if you browse to 102.168.100.(11 or 1?) you can see
> that the modem holds your mac addies in memory.  when you power it down
for
> so many minutes, your current mac addies are dropped and when you reboot,
> the new ones are put in memory.  if this is a new nic, you must do this.
I
> use a cisco 2611 to spoof an intel nic mac address, then nat/dhcp behind
> that so i can add and remove pc's at will and not be a slave to powering
> down my modem when i swap machines (i can also have 65000 addresses in my
> class b 10.1.x.x scheme).  The reprovisioning that was earlier in this
> thread is usually due to the exite-cox cutover and should only need to be
> done once if at all.
>
> my 2 sense
>
> anthony
>
> ----- Original Message -----
> From: "John Olson" <john.olson@tetrasystems.com>
> To: <plug-discuss@lists.plug.phoenix.az.us>
> Cc: <simplyservice@mobile.rogers.com>
> Sent: Monday, July 29, 2002 3:23 PM
> Subject: RE: Plug (und cox) (fwd)
>
>
> > I'm certain you've got it exactly right.  Some DHCP servers check the
> > MAC of the requesting machine.  Some routers (for sure Linksys) have a
> > "MAC Alias" configuration field so you can enter your NIC's MAC so DHCP
> > servers that check this think it's the original PC that is plugged in.
> >
> > -----Original Message-----
> > From: plug-discuss-admin@lists.plug.phoenix.az.us
> > [mailto:plug-discuss-admin@lists.plug.phoenix.az.us] On Behalf Of
> > Jeffrey Pyne
> > Sent: Monday, July 29, 2002 2:19 PM
> > To: 'plug-discuss@lists.plug.phoenix.az.us'
> > Cc: 'simplyservice@mobile.rogers.com'
> > Subject: RE: Plug (und cox) (fwd)
> >
> >
> > I have an OpenBSD firewall with its external interface configured for
> > DHCP. I also just set my boss up with a RedHat Linux box which gets its
> > external IP address from Cox' DHCP.  So rest assured, you aren't chasing
> > wild geese
> > here-- it is possible to connect a non-Windows system to Cox' network.
> >
> > I did have a problem like yours when Cox switched from @Home to their
> > own service, though.  I called Cox, and they said they had to
> > "provision" my cable modem (which simply involved me reading them my
> > modem's MAC address and Serial Number).  After that, they had me power
> > the modem off for about 30 minutes, and then power it back on.  Once I
> > did that, my OpenBSD machine was able to get an IP address from DHCP.
> > Also, when I set my boss' machine up, the computer that had been
> > connected to his cable modem before had Windows 2000 installed on it.
> > When we first connected the Linux machine to his cable modem, it
> > wouldn't get an IP address from DHCP.  I powered off his cable modem for
> > a while and then back on.  After this, the Linux machine got an IP
> > address.  We didn't have to call them up to "provision" his cable modem,
> > so the modem re-cycle seems to be the magic step.  The tech I spoke with
> > couldn't explain why that works, but it seems to, for whatever reason.
> >
> > Hope that helps.
> >
> > ~Jeff
> >
> > On Sat, 27 Jul 2002 11:52:15 -0400, simply service wrote:
> >
> > > I am having a terrible time trying to configure cox at home
> > > to work with a linux router I built for a friend.  Cox uses
> > > dhcp to assign ips and has changed their system so computer
> > > names were irrelevant.  My friend had his computer connected
> > > to cox on WinXP with dhcp, no problems there...Linux (2.4.18,
> > > SuSe) REFUSES to get an ip (request times out, even when set
> > > to 120 seconds). I've tried -r for old dhcp compliance, still
> > > nothing.  I've tried another network card, nothing...same
> > > config on my office network grabs on right away..I removed
> > > /var/lib/dhcp/eth0.cache or something similar to stop it from
> > > trying to renew its old lease from a different network.
> > > Still nothing.  I'm guessing that cox has done something to
> > > prevent linux from connecting (if you use linux, you are
> > > obviously computer literate, and will more than likely use
> > > nat and connect lots of systems - they might be disswaying
> > > that).  There are direction for how to configure several
> > > os's, including macs and nt 4...no !
> > > special instructions listed, so if true it might be the
> > > differences between m$ dhcp (and mac) and linux that causes
> > > the problem.
> > >
> > > I just spent all night working on this...if you want to email
> > > directly, simplyservice@mobile.rogers.com will do, please
> > > post responses to the list for others tho.  Thanks
> > >
> > > Jason Pfingstmann
> > ________________________________________________
> > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't
> > post to the list quickly and you use Netscape to write mail.
> >
> > PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> > ________________________________________________
> > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't
> post to the list quickly and you use Netscape to write mail.
> >
> > PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't
post to the list quickly and you use Netscape to write mail.
>
> PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>