[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Home Networking



Jon Eisenstein" <jeisen@mindspring.com> wrote:

Here's my /etc/network/interfaces setup:
###
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static # This is my university network (ethernet)
    address x.x.x.54
    netmask 255.255.254.0
    network x.x.x.0
    broadcast x.x.x.255
    gateway x.x.x.1

auto eth1
iface eth1 inet static # This is my internal network, see diagram below
    address 192.168.1.1
    network 192.168.1.0
    netmask 255.255.255.0
    broadcast 192.168.1.255
###


This looks OK for the config file. Does Debian start all of this?? You can find out by running "ifconfig" as root. It will report a summary of all interfaces running. You should see lo, eth0, and eth1 listed as running with the same data (IP, etc) as listed above. The lo interface should be on 127.0.0.1.


Here is how my internal network is set up. All cables are the same, that
were purchased from the university store:

[outside network jack] ---- [linux: eth0]
                                          [linux: eth1]
                                                  |            [Linksys
EtherFast 5-port Workgroup Hub]
                                                  ------------[Uplink]  [1]
[2]  [3]  [4]  [5]

|

[Windows]

Hope this is enough information. :) Any more, just make the request and
it'll be given.

Although not clear from the above diagram, you "could" be having a problem with the cable between [Linux: eth1] and the [Lynksys Hub]. If you are using the "uplink" port on the hub, then you MUST use a "crossover" cable and leave the adjacent "normal" port empty. On the other hand if you are using the "normal" port (NOT the one marked "uplink") then you can use a "straight-through" cable... the same as you are using on the other ports. If you bought all the same type of cables, I would suggest you move the [Linux: eth1] --> [Linksys Hub] cable to the empty "normal" port and see what happens.

Unless you have Debian setup to be a dhcp server, all your windows machines should be using unique "static" addresses within your "network" IP space in this setup. Debian doesn't come setup as a dhcp server "out of the box"... you have to do some extra config work to get this going.

Cheers,
-Don Spoon-






--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: