At the end, you ask that I (or we) "Please help me further". If we are to do that, you have to give us a clear, organized description of the setup you have, not isolated fragments of information that mean nothing out of context.
I read your reply to Jeff as well as this one and, looking at the two, simply do not understand your setup. Why is your ISP using private-range addresses? Why does your ISP assign LAN addresses, and not just the external address? I ask these questions ONLY to illustrate the level of my confusion, so please do not simply answer then. Instead, start over, this time with a description of the setup and some diagnostics from the LEAF router. I already suggested that you read the SR FAQ listed at the bottom of this message, and I renew that suggestion. (Though I do need to warn you that its details were not written for Eiger-Dynamic, so you may have to do some adapting to get such an old distro to report the information we need to see.) Up to now, I (and I imagine Jeff) had assumed that this was a standard setup with a NAT'ing router. But you need to be clear about that part too -- if the LEAF router does NAT, then you can use ANY private-range IP addresses behind it, except for the address range used on your external network. If the LEAF router does not do NAT, and the ISP is using private-range addresses that it NATs somewhere upstream of you (they have to be NAT'd *somewhere* to work), then you do need to pay attention to what addresses the ISP wants you to use ... and you and the ISP, between you, need some mechanism to tell the ISP's routers that your LEAF router is their route to the LAN. (You can do this yourself with proxy arp, or the ISP can do it by modifying its routing table.) But I hope you see why you need to describe the setup more completely than you have so far, if you want competent help. A couple of additional comments are intermixed below. At 02:58 PM 10/1/02 -0700, Liu Mei wrote: >--- Ray Olszewski <[EMAIL PROTECTED]> wrote: > > > From what you posted (deleted here to save space), > > it *appears* that your > > problem is that your external and internal networks > > are the same network. > > If that is correct, you need to change your internal > > network to something > > different (since the external assignment is, > > presumably, outside your > > control). The external network is probably > > 192.168.1.0/24 (though what you > > posted does not really make that clear), > >I don't know what exactly my subnet mask is. I didn't >change this setting. That means that the router thinks it is /24. The question is: what does the ISP think it is? This is something the ISP should have told you, so check the instructions you got from it. > > so you can > > switch the internal to > > (for example) 192.168.2.0/24 . > > >In fact, before using the image, the default gateway >is 1.254, some IP addresses assigned by the ISP's DHCP >server in the LAN are 1.100, 1.109,etc. > >Can I simply change eth1 to 2.254 and other PCs to >2.xxx? I don't know whether ISP has given 2.xxx to >others or not. As I said above, whether this matters depends on whether you are using NAT or not. > > That said, and since you say you are a newbie, let > > me offer a couple of > > bits of general advice. > > > >Many thanks indeed. > > > First, Eiger-Dynamic is ancient, > > > You might do > > well to move to a current version ...Dachstein and > > Bering seem to be the > > most popular for router applications, but the others > > are good too. > >I followed the webpage and choosed Eiger-Dynamic since >I have not had the static IP. What webpage are you referring to? No current LEAF Web page *should* be mentioning Eiger-Dynamic as anything other than a legacy, unsupported release. >Can Dachstein and Bering handle the dynamic IP >problem? Yes. You use the DHCP-client package (I forget the exact name) to do this. > > Second, the link at the bottom of list messages > > points you to a FAQ that > > offers advice about what information to post when > > asking troubleshooting > > questions. A copy of your routing table would, in > > this instance, have been > > more useful than the config file. > >I am sorry, I just want to provide more information to >make my problem a bit clear. Good. The FAQ will tel you how to do this. > >Also, "can't ping" > > is too vague -- pings > > fail in many ways, > >My ping error is the first type, which is nothing >shown on the screen but reports 100% lost after ctrl+c Hmmm ... this info helps, but not enough, without the basics of the interface list and routing table (and the exact addresses you tried to ping). -- -------------------------------------------"Never tell me the odds!"-------- Ray Olszewski -- Han Solo Palo Alto, California, USA [EMAIL PROTECTED] ------------------------------------------------------------------------------- ------------------------------------------------------- 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
