public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: [OT] Interrogate network for devices
Date: Mon, 11 Feb 2008 22:26:05 +0000	[thread overview]
Message-ID: <200802112226.07156.michaelkintzios@gmail.com> (raw)
In-Reply-To: <87myq7whyj.fsf@newsguy.com>

[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]

On Monday 11 February 2008, reader@newsguy.com wrote:

> The cable modem acquires an IP address by dhcp from comcast but also
> internalizes the MAC of the NIC in the PC, so if you change the MAC
> (By inserting a router in between, with a different MAC in this case)
> then the modem continues to try to connect to the MAC it has
> internalized.   It must be rebooted to acquire the new MAC (of the
> router in this case).

He, he, that's what I told ya!  Spoof (clone) the IP address on the router and 
you'd be good to go.  On the other hand if you power cycle the devices in the 
right order as Dale told you, you'll also get to the same point.

> Once that happens the Netgear routers (either one) connect with no
> problems.
>
> > It almost certainly has an Ethernet address.  It might not,
> > however, have an IP address.
>
> As you may have guessed I meant IP address.  That is, although the
> Modem connects to the PC by ethernet wire, it has no inward facing
> address.  This was explained by at least two other posters. (Something
> I'd failed to realize. I expected there to be an inward facing IP)

Quite often there *is* a static LAN IP address for the modem, which can be 
used to connect to it for diagnostic purposes.  Of course if the modem has 
only one ethernet port then you have to disconnect the router from it and 
connect your computer directly, after you set up the same IP subdomain using 
ifconfig.  A mate of mine has a Comcast router (probably different to yours) 
I'll ask how he got in and let you know.

> At any rate all is now well, and thanks to all for the tips and help.

Glad it worked out for you.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-02-11 22:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10  4:29 [gentoo-user] [OT] Interrogate network for devices reader
2008-02-10  4:44 ` Hal Martin
2008-02-10  5:46 ` Dan Farrell
2008-02-10 12:55 ` Mick
2008-02-11  3:26   ` Dan Farrell
2008-02-11  3:52 ` Dale
2008-02-11  6:19   ` Dan Farrell
2008-02-11  7:01     ` Dale
2008-02-11  4:59 ` [gentoo-user] " Grant Edwards
2008-02-11 10:56 ` reader
2008-02-11 15:39   ` Grant Edwards
2008-02-11 16:55     ` reader
2008-02-11 18:34       ` Grant Edwards
2008-02-11 23:24         ` reader
2008-02-11 22:26       ` Mick [this message]
2008-02-11 23:16         ` reader
2008-02-12  1:06       ` Dale
2008-02-12 22:06         ` Mick
2008-02-24 23:39           ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200802112226.07156.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox