Making d-link router act as a switch

shwaipshwaip bluffin' with my muffin Icrontian
edited June 2004 in Science & Tech
I'm currently fixing the network in the house, and I now have it set up as follows:

DSL Modem -> Wireless Router -> PCs

However, I'm short one port on the back of the wireless router, and I now have a spare D-Link DI-604 router that I want to set up to be a switch, and basically have none of the functions that makes a router a....router. How would one go about doing this?

Thx

Comments

  • edited June 2004
    just turn off the DHCP on the "switch." Connect a LAN port on the router to the WAN port on the "switch."
  • shwaipshwaip bluffin' with my muffin Icrontian
    edited June 2004
    ok, I tried that, but it is still assigning IPs.

    I have the wireless router set to give my fileserver a static IP (.151), and it is showing that its IP is .100, assigned by the non-wireless router.


    and if i release/renew on a different computer connected thru the (non-wireless) router, I can't get a new IP, or access the router anymore, I need to reset it.
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited June 2004
    shwaip wrote:
    I'm currently fixing the network in the house, and I now have it set up as follows:

    DSL Modem -> Wireless Router -> PCs

    However, I'm short one port on the back of the wireless router, and I now have a spare D-Link DI-604 router that I want to set up to be a switch, and basically have none of the functions that makes a router a....router. How would one go about doing this?

    Thx

    Um, plug a wireless gate into the wired router's Uplink port, let the wireless feed the gate an IP, have router accept DHCP for it's IP through gate???? I THINK what MIGHT BE happening is that things are working and with the IP of .100 showing on the wireless, that this is the WIRED ROUTER's IP that the wireless router is seeing.... BUT, what you want is in fact an address forwarding for a server, so you probably get to do that by ports the server is being told to handle.

    The problem is, if you want this server on the web or accessible outside the LAN, I would do this instead:

    DSL Modem<-->Wired Router<-->Wireless Router<->PCs on wireless

    Hook server to wired router, in DMZ (DMZ CAN be fixed IP, often is, while rest of ports can still be DHCP'd) if you can spec that, for web serving if needed and do not need to masq the server IP. Hook Wireless router to Wired(with Wired router upline between modem and wireless), let Wired grab DHCP from modem, feed it to Wireless, let Wireless handle PCs other than server.

    I know what you are thinking, but to spend absolute minimal money, you simply make your wired router a ROUTER, let the wireless be a subsidiary router for wireless devices.

    Otherwise you need a media conversion(wired<-->wireless) somewhere, and it is hard to maintain fixed IP through network that way-- unless you can DMZ and Fixed IP your server wirelessly already, but the setup for that brings a mishmosh of things (many security considerations, data integrity issues also) into play that I do not think you really need to fight with....
  • dodododo Landisville, PA
    edited June 2004
    you might have to change the default port on the "spare" router to something other than 192.168.0.1 (it may be conflicting with teh other router)
Sign In or Register to comment.