Many thanks firstly. I think I made mistakes in network.conf but I could not figure out. I think the additional information may be useful.
The IP addresses in the LAN are assigned by the ISP's DHCP server. They are 192.168.1.100, 192.168.1.109, ... This is why I set 1.253 on eth1 and tried to make it be my new gateway. But I feel odd since ISP manages 1.254, what should be my subnet mask? While pinging the internet, 1.254 and LAN, I got the 1) type error, which is nothing on the screen but reporting 100% lost after ctrl+c. I would like to insert my new route between the ISP's route and my LAN. kind regards, Liumei --- Jeff Newmiller <[EMAIL PROTECTED]> wrote: > On Tue, 1 Oct 2002, Liu Mei wrote: > > > > > Hi, I am a newbie. :-( > > > > I am using the Eiger-Dynamic.bin image since I > have > > not got a static ip from the ISP. > > > > I followed the instruction step by step including > > adding the NIC module. > > > > I had to change the ip of eth1 in the > network.conf. > > (I didn't change the ipchains) > > > > Since the current default gateway is > 192.168.1.254, I > > gave the eth1 192.168.1.253. > > Eth0 seems be 192.168.1.113 after runing dhclient. > > > > Now I can ping both 1.253 and 1.113 but I can't > ping > > the internet, the gateway 1.254 and any other IP > in > > the LAN. > > > > The following message are generated by runing set > of > > command required while looking for help. > > > > Hope you can help me to fix the common problem. > > It kind of looks like you already have a > masquerading device connecting > you upstream, that is acting as a DHCP server. > > a) You seem to be assigning 1.253 on eth1, and the > rest of 1.x are being > managed by the upstream DHCP server (router?) on the > network you are > connecting eth0 to. Each network card should > normally be connected to a > different IP network. Not doing so requires some > sophistication... if you > feel this is definitely required (it probably isn't) > then study up on > "proxy ARP" or "bridging" using Google. > > The easiest alternate network to choose would be > 2.x, with 2.254 assigned > to eth1. Unfortunately, there are many places in > the /etc directory and > below that assume you are using 1.x on eth1, and I > don't have a list of > every line that needs to be changed (I don't even > run Dachstein). Someone > else may be able to supply that, or you may just > have to use the > "grep" command carefully. > > b) Dachstein blocks passing private addresses like > 192.168.x.y between > eth0 and eth1, on the assumption that you are > connectiong to a public > network with eth0. You need to follow the > instructions at > http://sourceforge.net/docman/display_doc.php?docid=2869&group_id=13751 > if > you need this capability. > > c) If your intent is to replace the device that is > currently handling your > routing, then you should not be changing anything > regarding ip addresses > on eth1... rather, you should be disconnecting the > existing router and > installing the Dachstein router. > > [...] > > --------------------------------------------------------------------------- > Jeff Newmiller The ..... > ..... Go Live... > DCN:<[EMAIL PROTECTED]> Basics: ##.#. > ##.#. Live Go... > Live: OO#.. > Dead: OO#.. Playing > Research Engineer (Solar/Batteries O.O#. > #.O#. with > /Software/Embedded Controllers) .OO#. > .OO#. rocks...2k > --------------------------------------------------------------------------- > > __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by: DEDICATED SERVERS only $89! Linux or FreeBSD, FREE setup, FAST network. Get your own server today at http://www.ServePath.com/indexfm.htm ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
