Thanks all, I had only set them this way to see if all the cards were working. I didn't realize that it would cause this problem. I have some other routers kicking in the office and a few spare pc's, I guess I'll be setting up a test network. I'll probably remove one of the cards as the configured router will only need 2 (again I was testing the 3). Where this is eventually going is replacing our three Linksys BEFSX41 with three of these. The reason is the linksys routers have an extraordinarily high failure rate and there firmware is always buggy. We have three offices each one has a router that performs NAT for the subnet, and links to the main office via VPN, as well as performing DHCP functions. I am curious as to whether Vyatta VPN will be compatible with Linksys. If it is we can role these out in a much more orderly fashion. If not it means I have to have all three configured before I can switch over. I'm glad to see that my current issue is simply operator error.
Thanks again for your help. Jesse On 12/28/07, Robert Bays <[EMAIL PROTECTED]> wrote: > > Jesse, > > Linux treats arp queries differently than routers do. In a default > installation it will respond to any arp request for any IP on the system > through any of it's interfaces. You can change this with "echo 1 > > /proc/sys/net/ipv4/conf/all/arp_filter". This used to be set by default > in Vyatta Community but I don't see it in my local copy of VC3 right > now. (I need to look into that.) By setting this the system will only > respond to arp requests out interfaces that the kernel would normally > route a packet to the requesting subnet. > > Even that won't help your situation though since all of your addresses > are on the same subnet. The kernel will pick one interface and respond > to all arp requests for all IPs in your subnet out that one interface. > To fix this problem you would need to use the "ip arp" extensions and > filter arp/requests and responses. This still isn't *really* a good > solution because it only is guaranteed to solve the inbound part of the > issue. > > It's usually easier just to change your topology so as your IPs aren't > on the same layer 3 subnet. > > Cheers, > Robert. > > Jesse Robertson wrote: > > I'm just beginning to learn about this and am in the process of setting > > up a test router. I have installed 3 ethernet cards in the test pc of > > various brands and ages ( I used what I had laying around and this is > > only replacing a linksys BEFSX41 (Hopefully)). The software recognizes > > the 3 separate cards and has called them eth 0 - 2 and reads there MAC > > addresses nicely. I set each card to its own IP 192.168.1.30/24 > > <http://192.168.1.30/24> -192.168.1.32/24 <http://192.168.1.32/24> and > > when I go to Configure and Show it displays correctly. The issue is > > that I have only connected one card to a switch and that is showing up > > as all three ip addresses. It responds intermittently to pings and > > though I activated the WebGUI I cannot access it. > > > > If someone has an idea of what I'm doing wrong I'd appreciate the help. > > Thanks > > > > Jesse > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users >
_______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
