why do you need to switch after going through the webgui thing? This makes no sence!
Marc turbo wrote: > I reinstalled and it is as you mentioned below the second option. > > cable modem > efw (24.72.112.29red/192.168.100.50green) > switch > > During the initial setup ( blue screen) i am asked for the green IP whci I > supplied with 192.168.100.50. After the reboot and connecting to the webgui > I set the following: > > 1/7 : for red ethernet dhcp > 2/7: None for orange, blue > 3/7: green IP 192.168.100.50 subnet 255.255.255.0 eth1 > 4/7: red: etho hostname: xxxxx domain: zzzzzzzz.zz DNS: automatic > 5/7: DNS: automatic > 6/7: Save > > After this I have to switch the cable so it is: from the switch to the eth1 > nic and eth0 to the cable modem. > > To be sure, I made a reboot and got no dhcp connection to the ISP. I tried > from the terminal with 'dhclient eth0' and after a while it timed out with > no response. Damn!! > The nic was still active, I checked it a few times!! > I searched for /var/efw/red/resolv.conf and this file was not created as > there was nothing to create with as it was no connection. > > here a terminal screen of dhclient: > --------------------------- > [EMAIL PROTECTED]:~ # dhclient eth0 > Internet Systems Consortium DHCP Client V3.0.1 > Copyright 2004 Internet Systems Consortium. > All rights reserved. > For info, please visit http://www.isc.org/products/DHCP > > Listening on LPF/eth0/00:06:5b:82:fc:f7 > Sending on LPF/eth0/00:06:5b:82:fc:f7 > Sending on Socket/fallback > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > --------------------------------------------------- > > Just for the sake of testing I released and renewd the IP of the ISP with > the dlink and it's just working. > > Where am I making the wrong move ?? I really can't see it. > It's late here now and I will work on that further tomorrow. > Thank you for your persistence. Hope to here from you tomorrow. > > Johannes > > > So, where is the efw in that chain? > > Should be: > > cable modem > d-link (24.72.112.29 wan/192.168.0.1 lan) > efw (192.168.0.x > red/ > 192.168.1.1 lan) > switch > > or > > cable modem > efw (24.72.112.29 wan/192.168.0.1 lan) > switch > > Fill in the private ips above with what you actually use. Note the two > different > private ip addy ranges are needed in the first setup. > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of turbo > Sent: Wednesday, October 03, 2007 7:46 PM > To: efw-user@lists.sourceforge.net > Subject: Re: [Efw-user] I am lost with new install, help please > > > okay, here is the setup: > cable modem > d-link (no dhcp server for my LAN) > switch > > The dlink gets the ISP settings per dchp client (the dlink router itself= > dchp release, dchp renew button) And those settings are the ones I noted. > > snipped a lot > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Efw-user mailing list Efw-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/efw-user
