Hi Bruno -

Actually thats the eth0 card and its working fine ( did change the 999 items)
...the subnet 255.255.252.0 is issued to the eth0 as it it set up to be DHCP to my ISP.

Eth1 is the internal card.

What does this mean

"And interrogations are not welcome, either"

Easy one I missed when I was working on this. Did you relese and renew the IP addresses on the interanl boxes after initiating the DCHP service on eth1 (NIC serving internal net)?

My 1st post, questions to follow . . .

RedBeard55

Yep I did that (endlessly! :) )

Here's the latest - and further down where I ended up

DLINK's weak ass support - stated:

*************

Your Case ID is PTS23605516.

[Critical: Please do not change the subject line of your email when you reply. Leaving the subject line as it is will allow us to review your complete history and help us to better serve you.]

Date of Reply: 3/24/2004 8:16:51 AM

Products: DI-604
Operating System: Linux



To use your router as an access point/switch only, please follow the steps below:

Step 1 Do not use the WAN port.

Step 2 Depending on your network setup, you may need to change the LAN IP address of the router. The default is 192.168.0.1. If you are using another router, DHCP server, or Internet connection sharing software, change the LAN IP address of the router to an IP in your subnet. The LAN IP address must be static.

Step 3 Disable DHCP on the router. To disable DHCP, go into the routers configuration > Home > DHCP. Click Disable and then click apply.

Step 4 Your computer will not receive a DHCP address from you DHCP server so you will need to set the IP addresses statically on your computer.

To view the FAQ on how to set your IP address statically please visit: http://support.dlink.com/faq/view.asp?prod_id=1053


Should you require further assistance with your D-Link products, please reply to this message, or call toll free at 877-453-5465. Thank you for networking with D-Link.

**********

So basically you can't have a router behind a router ....

Heres what I settled on for all interested parties ...

Cable modem
to
HUB (old 4 port)

out of 2 ports a and b

a
out on one port to
Dlink Router for home network (set as DHCP)

b
into ETH0 (set up as DHCP)

and in addition -
OUT of ETH1 (now set as DHCP)
to a port on the DLINK router
so I can see it on my network neighborhood
and it will be easier to admin apache via Dreamweaver

So basically I gave up on the DHCP server on eth1 trying
to feed the dlink router

The End (?)

"Cable modem
to
HUB (old 4 port)

out of 2 ports a and b

a
out on one port to
Dlink Router for home network (set as DHCP)

b
into ETH0 (set up as DHCP)

and in addition -
OUT of ETH1 (now set as DHCP)
to a port on the DLINK router
so I can see it on my network neighborhood
and it will be easier to admin apache via Dreamweaver

So basically I gave up on the DHCP server on eth1 trying
to feed the dlink router"

****

1. My Terayon cable modem won't route, so I can't use that config. If yours can route, it's ok.

2. I thought you were doing like this:

internet >>> cbmodem >>> SuSE >>> DLink >>> PC's

3. Is everything working the way you wanted?

CableModem
V
V
V
V
Dumb HUB >>>.SuSE PC on eth1 (DHCP)
V ~
V ~
V eth1 (DHCP) (not necessary but a nice backdoor in)
V ~
V ~
DLINK--- >-----W2kPC1--->----W2kPC2--->---W2kPC3
(WAN in)

CableModem
V
V
V
V
Dumb HUB >>>.SuSE PC on eth1 (DHCP)
V ~
V ~
V eth1 (DHCP) (not necessary but a nice backdoor in)
V ~
V ~
DLINK--- >-----W2kPC1--->----W2kPC2--->---W2kPC3
(WAN in)

CableModem
V
V
V
V
Dumb HUB >>>.SuSE PC on eth1 (DHCP)
V ~
V ~
V eth1 (DHCP) (not necessary but a nice backdoor in)
V ~
V ~
DLINK--- >-----W2kPC1--->----W2kPC2--->---W2kPC3
(WAN in)

Is it working this way? If it is, discard the diagram below.

This is my final trial, drifter. I think you should do this:

Internet
V
V
V
CableModem
V
V
V
eth0 (dhcp)
SuSE (SuSe will do routing. Remove the dlink piece from the
assembly)
eth1 (static 192.168.0.1)
V
V
V
V
Dumb HUB
V V V
V V V
V V V
V V V
PC1 PC2 PC3 etc...

The hub has no IP. The PCn machines receive IP's 192.168.0.X, being X between 2 and 255.
Gateway for internal machines is eth1, you see? Gateway is 192.168.0.1.