[SATLUG] OT(?sorta) Linksys WCG200 - DHCP wrong (or bad) address with routing and NAT turned on

ed horned0wl93 at gmail.com
Sun Mar 30 14:54:13 CDT 2008


Jennie Haywood wrote:
> On Sun, Mar 30, 2008 at 1:08 AM, ed <horned0wl93 at gmail.com> wrote:
>   
>> Jennie Haywood wrote:
>>  > This has been incredibly frustrating.  Apparently, we had a power
>>  > outage last night.  Generally the router may go down but it comes back
>>  > up working.
>>  > Oh but not today.  {snip}
>>
>>     
>>  > SO - when the routing and NAT is turned on AND  I let it get the
>>  > address via DHCP, I get an address like 72.48.XX.XX, but I can't ping
>>  >
>>  Sounds like there's a routing issue between Grande and another cable
>>  company.  Might be happening if they're sharing equipment and/or lines.
>>  72.48.0.0-72.48.31.255 is a group of the Grande-Frisco (Grande-05)
>>  network, whereas 66.90.0.0-66.90.63.255 is a group of SmartCityOn-Line
>>  out of Florida.  Looks and sounds like you are experiencing
>>  crossed-lines somewhere up-channel from you. Perhaps one of the DHCP
>>  servers "went wild," or maybe there's been a rogue server injected into
>>  the network somewhere.
>>     
>
> hmm.... I'm getting the 72.48.68 and the 66.90.246 networks.
> One of the things I tried was setting up the 72 address they were
> sending me with a network mask of 255.255.254.0, which is the netmask
> that they are using on the 66 network. It looks like they are using
> the last 254 number of the subnet as the default gateway so put that
> in.   That didn't work.
>
>   
Ok, Jeannie...  It looks like we're at least back in the same network,
as you might see below, with the 72.48.68.xx address being the major
trunk (Grandecom-market03-01), and the 66.90.246.xx being the local
network (SM hub, SA Net).  Its possible that the local DHCP server (69)
is wonky in some way, and either sending or defaulting DHCP requests
up-channel.  If that's the case, the up-channel DHCP server (72)
wouldn't know what to do with you (you're not at the right level on its
routing table), and might either reject or ignore you  -- its hard to
tell... Maybe this is some ammunition you could take back to them?

> 72.48.68.XX
>
> Grande Communications Networks, Inc. GRANDECOM-05 (NET-72-48-0-0-1)
>                                   72.48.0.0 - 72.48.255.255
> Grande Communications SAN ANTONIO HUB 1 GRANDECOM-MARKET03-01
> (NET-72-48-68-0-1)
>                                   72.48.68.0 - 72.48.69.255
>
>
> 66.90.246.XX
>
> OrgName:      Grande Communications Networks, Inc.
> OrgID:            GCNI
> Address:        401 Carlson Cir
> City:               San Marcos
> StateProv:     TX
> PostalCode:   78666
> Country:        US
>
> NetRange:   66.90.128.0 - 66.90.255.255
> CIDR:           66.90.128.0/17
> NetName:    GRANDECOM-01
> NetHandle:  NET-66-90-128-0-1
> Parent:         NET-66-0-0-0-0
> NetType:        Direct Allocation
> NameServer: NS1.LSN.NET
> NameServer: NS2.LSN.NET
> Comment:      ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
> RegDate:        2001-03-29
> Updated:        2003-06-20
>
> OrgAbuseHandle: ABUSE153-ARIN
> OrgAbuseName:   Abuse
> OrgAbusePhone:  +1-512-878-4000
> OrgAbuseEmail:  abuse at grandecom.com
>
> OrgTechHandle: IPSER2-ARIN
> OrgTechName:   IP Services
> OrgTechPhone:  +1-512-878-4000
> OrgTechEmail:  ipservices at grandecom.com
Whaddya think?

Cheers;
Ed





More information about the SATLUG mailing list