Comments inline... > I am building a router with EigerStein-2beta-img-EigerStein_2beta.exe. > I have to connect to an internal 172.16.0.0/16 network. > I have prepared a diskette which boots. > The router can ping the internet, but have not yet tested the internal network. > > I would like to know if I am making any obvious errors before I troubleshoot the router at the client's location and get in over my head and embarrass myself.
Then you should definately test the internal network (as well as the router's access to the internet) before going onsite. See below for more info... > Thanks for your help in advance. > > The router is a Pentium 120 w/32M, no hard drive, 2 new linksys nics (tulip). > I have modified network.conf to use this internal network. > > ********** network diagram *********** Looks OK <snipped> > *********** VARIABLES SET IN NETWORK.CONF ************* > > eth0_IP_SHARED_MEDIA=YES > > eth0_BRIDGE=NO > > eth0_PROXY_ARP=NO > > eth0_FAIRQ=NO > > eth1_IPADDR=172.16.1.250 > eth1_MASKLEN=16 > eth1_BROADCAST=172.16.1.255 This is an odd broadcast address for your /16 network. Typically, the broadcast address would be 172.16.255.255. You CAN use any broadcast address you want, but you need to make sure ALL of your clients are using the same one, or you'll get mysterious problems. > eth1_IP_SPOOF=YES > eth1_IP_KRNL_LOGMARTIANS=YES > eth1_IP_SHARED_MEDIA=NO > eth1_BRIDGE=NO > eth1_PROXY_ARP=NO > eth1_FAIRQ=NO > > ppp_BNDWIDTH=30Kbit > ppp_FAIRQ=YES > ppp_TXQLEN=30 > ppp_IABURST=20 > ppp_IARATE=10Kbit > ppp_PXMTU=1500 > > IPFILTER_SWITCH=firewall > <snip> > > INTERN_IF="eth1" # Internal Interface > INTERN_NET=172.16.1.0/16 # Internal network (to be masqueraded) Your network address is actually 172.16.0.0/16 > INTERN_IP=172.16.1.250 # IP number of Internal Interface > # (to allow forwarding to external IP) > MASQ_SWITCH=YES # Masquerade internal network to outside > # world - YES/NO <snip> OK, first you need to verify the internal network is REALLY setup how you want. Are they really running a /16 network with a non-standard broadcast address, or are you perhaps confused and they're really running a /24? Once you've got the internal net specifics cleared up, you need to setup the REST of the system for the new IP. This includes things like the dhcp server, dnscache, weblet, and maybe some other things I'm not thinking of right now. If you don't plan on using any of these services, you should at least configure your system to not load them on boot, and possibly delete them from your floppy...you'll have more free disk space and RAM to play with. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
