Connecting to Comcast

[Andrew W. Gaunt]

Remember you can ifconfig a single NIC with a secondary IP in
when using linux/Solaris. This is kind neat since it allows you
to easily run two 'networks' on the same media.


rockhopper:/etc/rc3.d# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:20:8F:24:04 
          inet addr:152.148.8.187  Bcast:152.148.255.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23132456 errors:0 dropped:0 overruns:0 frame:0
          TX packets:474038 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1505871693 (1.4 GiB)  TX bytes:62763477 (59.8 MiB)
          Interrupt:32

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3863874 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3863874 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:337303529 (321.6 MiB)  TX bytes:337303529 (321.6 MiB)

rockhopper:/etc/rc3.d# ifconfig eth0:1 192.168.100.10
rockhopper:/etc/rc3.d# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:20:8F:24:04 
          inet addr:152.148.8.187  Bcast:152.148.255.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23132816 errors:0 dropped:0 overruns:0 frame:0
          TX packets:474263 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1505895154 (1.4 GiB)  TX bytes:62786987 (59.8 MiB)
          Interrupt:32

eth0:1    Link encap:Ethernet  HWaddr 08:00:20:8F:24:04 
          inet addr:192.168.100.10  Bcast:192.168.100.255  
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:32

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3863874 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3863874 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:337303529 (321.6 MiB)  TX bytes:337303529 (321.6 MiB)

rockhopper:/etc/rc3.d# ifconfig eth0:1 down
rockhopper:/etc/rc3.d# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 08:00:20:8F:24:04 
          inet addr:152.148.8.187  Bcast:152.148.255.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23133912 errors:0 dropped:0 overruns:0 frame:0
          TX packets:474746 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1505964880 (1.4 GiB)  TX bytes:62839289 (59.9 MiB)
          Interrupt:32

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3863874 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3863874 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:337303529 (321.6 MiB)  TX bytes:337303529 (321.6 MiB)


-- 
____    __
 | 0|___||.  Andrew Gaunt - Computing Development Environment
_| _| : : }  Lucent Technologies: http://www-cde.mv.lucent.com/~quantum
 -(O)-==-o\  Personal: http://www.gaunt.org



pll at lanminds.com wrote:

>>>>>>On Tue, 23 Sep 2003, "Jerry" == Jerry Feldman wrote:
>>>>>>
>
>  Jerry> First, try to see if you can access your cable modem at
>  Jerry> 192.168.100.1.
>
>I found this IP on the web somewhere after googling around.  The 
>question I have is this, how can I access a network for which I have 
>no route?
>
>IOW, I have 2 nics, one on my internal LAN, and one for connecting to 
>the CM. The 'external' NIC is obviously unconfigured, since it's 
>supposed to be configured using DHCP, which isn't working.
>
>And yes, I've tried manually configuring that NIC to be on the 
>192.168.100/24 subnet, and that didn't seem to work.
>(I'm also *very* disappointed that there's no serial port on these 
>modems, though, ironically, on my "Digital Cable" set-top box there 
>is?! :)
>
>I'm beginning to hate ComCast already, and I haven't even *used* 
>their stuff yet :) (and I thought DSL was the only technology that 
>had install horror-stories :)
>
>Thanks, I'll try the website :)
>