David Taylor wrote:
Chris, does your cable modem do NAT and assign your pc a 192.x IP address
and provide DHCP for your network??  If so, just tell your IPcop RED that it
is DHCP provided info, and you should be done.

Possible confusion point here, I think.
Gave all of the above suggestions a go- thanks everyone.
With just telling RED to use DHCP info, having a look at the box's http config shows that
eth0 Link encap:Ethernet HWaddr 00:10:5A:73:60:F7
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1414 errors:0 dropped:0 overruns:0 frame:0
TX packets:1813 errors:0 dropped:0 overruns:0 carrier:0
collisions:148 txqueuelen:100
RX bytes:230556 (225.1 Kb) TX bytes:938560 (916.5 Kb)
Interrupt:11 Base address:0xa000


eth1 Link encap:Ethernet HWaddr 00:A0:D2:04:6D:F9
BROADCAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:2360 (2.3 Kb)
Interrupt:9 Base address:0x3000
Does this mean that the NIC on eth1 (RED) isn't seeing the modem or being told where it is?
And this is perhaps a dirty question.. but is it possible with IPCop to have the cable modem connected via USB?
I'm just about at the point of cutting my losses and moving on, but even if I do it's been interesting and a learning experience.
Thanks


Chris.



Reply via email to