On Saturday 06 November 2004 16:14, Stan Glasoe wrote:
On Saturday 06 November 2004 2:11 pm, Don Parris wrote:
I'm trying to setup two NICs on one box, and seem to be having trouble eaching the rest of the LAN using eth1. I use eth0 for the DSL connection.
ifconfig reports: dsl0 Link encap:Point-to-Point Protocol inet addr:192.168.99.1 P-t-P:192.168.99.99
eth0 Link encap:Ethernet HWaddr 00:0A:E6:68:3E:24 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
eth1 Link encap:Ethernet HWaddr 00:01:02:73:CA:CF inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
ping -I 192.168.1.2 192.168.1.14 produces "host unreachable".
I've tried 2 different NICs. I suspect the problem is not dead NICs but perhaps something I need to do differently or additionally. I've setup the hosts file with both NICs listed (and tried it with only eth1's address listed - 192.168.1.2) I'm not quite sure what else to do.
Thanks, Don
How are these NICs cabled? Does eth0 go directly to dsl0? Does eth1 go to a physically separate LAN through an ethernet switch that 192.168.1.14 is also plugged into? Is dsl0 an external DSL modem or is it internal to the PC? Where is the DHCP server or does everything have static IP addresses?
Set eth0 and eth1 to different subnets such as eth0=192.168.?.x/24 and eth1=192.168.1.x/24. This is where its nice to have a DHCP server serving the rest of your 192.168.1.x/24 network since everything else that eth1 connects to is already at 192.168.1.x/24.
What I did was to set eth0 as the external/Internet device at 192.168.1,x connecting to my broadband router which has a minimal firewall and NAT and DHCP server (which would be serving to only one device, eth0). The router talks to the DSL/Cable modem. Then eth1 as the internal/LAN device talks to the rest of the LAN on 192.168.2.x and does caching DNS, DHCP server, Squid proxy, Shorewall firewall and other security things.
There are some other details to check but lets get the basic plumbing straight first...
Stan Well, I did not setup DHCP - let me get the /etc/hosts file approach first. I left eth0 config'd as 192.168.1.3. I changed the rest of the LAN 192.168.2.x. At least now, when I ping the LAN, the hub lights up for both NICs, whereas before, it would only light up for the NIC I was pinging from.
All other boxes recognize each other, and I can ping via IP or host name. But when I ping from x/2.2 (or to it), ping doesn't return a result, and I have to hit [ctrl]+c. I've also noticed an error message that may have an impact - not sure: Error inserting ipfwadm (/lib/modules/2.6.8-24.3-default/kernel/net/ipv4/netfilter/ipfwadm.ko): Device or resource busy Next step? -- DC Parris GNU Evangelist http://matheteuo.org/ http://chaddb.sourceforge.net/ "Free software is like God's love - you can share it with anyone anytime anywhere!"