Good start on a trouble report. A few specific questions: 1. Can the DachStein router/firewall ping its *own* IP addresses? 192.168.1.2 in particular? If not, how does this fail (I suspect from your report that you have read the FAQ materials on pings, but just in case, I'll mention that pings fail in about 5 distinct ways)?
2. Can the SuSE host ping its *own* interface (192.168.1.1)? If not, how does this fail? 3. Is the routing table on the SuSE host correct? (Look at the output of "netstat -nr" on it.) 4. Since the "LAN" seems to consist of only the two hosts ... are you sure all the hardware is OK? Are both UTP cables good (regular cables, NOT crossover cables)? Are the ports on the hub good? Are both devices plugged into normal (NOT "uplink") ports on the hub? Do appropriate lights come on, on the various NICs and hub ports, when cables are connected and pings are running (sorry I can't be more specific here; there are too many variations on LED arrangements)? I think there's a FAQ answer that asks a few more queations than these regarding hardware. As to your PPPoE question ... I haven't used PPPoE in some time, and not with DachStein, but Ken Hadley's instructions, part of the PPPoE package itself, should guide you (They certainly seemed adequate to me back when I used his EigerStein-based PPPoE image). At 01:29 PM 12/12/01 -0500, Dr. Richard W. Tibbs wrote: >Sending this on the leaf-user list after some hours of trying.... >My present problem is that I can't ping from my dachstien box, loaded >with the rc2 version booted from floppy. >Is it possible there is some firewall filtering that prevents ping even >outbound? >In consonance with the troubleshooting support page, I have the >following network diagram: > > A PC running Suse 7 cat5 hub > cat5 dachstein box >(192.168.1.1/24 dev eth0) <-------> (SMC EZ Hub 10/100) <------> >(192.168.1.2/24 dev eth1) > > (dhcp dev eth0 ) <----> Alcatel speed > > touch >DSL modem. > >I have a known working ethernet nic in the Suse box, used it before to >ping a different box, all works fine. > >I have two Netgear FA311 nics in the dachstein box, and the natsemi.o >module seems to pick them up fine upon >insmod natsemi.o > >The output of lsmod shows the natsemi loaded, and in use by pci-scan. >The results of dmesg are no errors, only >eth1: setting full-duplex based on negotiated link capability > >I would like to set an IP address on eth1, set a route, and ping my Suse >machine just to verify it. >I have done: >ip addr add 192.168.1.2/24 broadcast 192.168.1.255 dev eth1 >ip link set up >ip route add 192.168.1.0/24 dev eth1 > >The output of ip addr show is: >1: lo: <LOOPBACK,UP> yadda yadd >2: eth0: <BROADCAST,MULTICAST> yadda link/ether (the correct hw addr) >3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 > link/ether (the correct hw addr) > inet 192.168.1.2/24 brd 192.168.1.255 scope global eth1 > >and the output of ip route show is: >192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.2 > >But a ping command >ping 192.168.1.1 >shows 9 or 10 packets sent, none recieved, all packets lost. > >Also --- looking ahead to tyring to connect up eth0 to my dsl provider: >I have read the LRP xDSL how-to, but it is only for static IP from a >provider, apparently. >Is there a how-to for getting PPPOE running over a DSL modem in Dachstein? -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
