Fantastic! Ifconfig now shows eth0 rather than dummy0: - io address was 0x2a0. Thanks, I would never had known to change that. tcpdump now showing host jenny/TCL unreachable, no other traffic showing. netstat -rn shows 192.168.11.0 0.0.0.0 255.255.255.0 U eth0 tcpdump does show at the end "eth0 > arp who-has jenny/TCL tell TRX850/TCL (0:80:c8:78:42:bf)" after using lo to ping its own IP address. Thanks all. My problem has moved on and up. Jenny.
All,
Can any one make some recommendations as to the best and most secure method of sharing files under unix. Th machines are behind a firewall, but sat in the DMZ, so we want th minimium number of ports to be left open.
Can anyone advise?
Thanks
D
__________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
On Thu, 12 Apr 2001, David Freeman wrote:
Can any one make some recommendations as to the best and most secure method of sharing files under unix. Th machines are behind a firewall, but sat in the DMZ, so we want th minimium number of ports to be left open.
Use NFS and make sure that you have it configured properly and don't allow any NFS traffic through your routers.
Adam
On Thu, Apr 12, 2001 at 12:21:43PM +0100, Jenny_Hopkins@toby-churchill.com wrote:
Fantastic! Ifconfig now shows eth0 rather than dummy0: - io address was 0x2a0. Thanks, I would never had known to change that. tcpdump now showing host jenny/TCL unreachable, no other traffic showing. netstat -rn shows 192.168.11.0 0.0.0.0 255.255.255.0 U eth0 tcpdump does show at the end "eth0 > arp who-has jenny/TCL tell TRX850/TCL (0:80:c8:78:42:bf)" after using lo to ping its own IP address. Thanks all. My problem has moved on and up. Jenny.
Looking at the output of netstat -rn your kernel routing table looks correct, i.e. send everything for network 192.168.11.0 out of interface eth0.
There is one more stage to routing packets though - the kernel needs to find a MAC (Ethernet) address for the destination machine in order to be able to send the ethernet frame to the right place. It does this with an ARP broadcast and the response to this tells the kernel which MAC address to use.
Unlike many other unixes, if ARP fails for a local destination address on Linux, it reports "No route to host" just the same as if the error had occurred at the IP level.
The most likely reason for ARP failing is that your network card is not receiving anything from the network. You can confirm this my doing 'ifconfig eth0' and looking at the RX packets field. Assuming the cabling is in order the next most liley explanation is that the driver thinks the card is using one IRQ when the card is actually using another one. You could therefore play around with the IRQ setting for the driver in the /etc/modules.conf file much like you did with the I/O address.
Steve.
-
Adam Bower -
David Freeman -
Jenny_Hopkins＠toby-churchill.com -
Steve Fosdick