Erich >Looks like it, but do you have an address assigned to eth1 at this very moment. >PCMCIA adapters are inhernetly slow on startup, so possibly dhcpd is >started _before_ the adapters are up completely. >This is the reason for the delay code
Yes I think that's correct and now I can get some results like: the PC on eth1 grabs an address from dhcpd, I can ping from a PC on eth1 (local net) 192.168.1.2 to the dlink(router) 192.168.0.1 on eth0 I'm not able yet to ping from same PC to any address on the internet like 32.97.166.74, if I try to ping from the console of 755 (LEAF Bering) I get a message like: # ping 32.97.166.74 PING 32.97.166.74 (32.97.166.74): 56 data bytes ping: sendto: Network is unreachable the LED does not blink on eth1 in this case. I've been looking to Shorewall's -(FAQ 14) I'm connected via a cable modem and it has an internal web server that allows me to configure/monitor it but as -expected if I enable rfc1918 blocking for my eth0 interface (the internet one), it also blocks the cable modems web server. and followed the suggestions but no change in the ping behaviour. I don't understand the overall mechanism of the system and therefore I don't know the requirements for a PC request to get through the firewall to the internet. Thanks for help Roberto ____________________________________________________________ Find what you are looking for with the Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click ------------------------------------------------------------------------ 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
