Date: Sun, 17 Mar 1996 12:03:55 -0800 (PST) From: Robert Du Gaue <rdugaue@calweb.com> To: questions@freebsd.org Subject: ARP ARP ARP ARP (fwd) Message-ID: <Pine.BSF.3.91.960317120202.1254B-100000@web1.calweb.com>
next in thread | raw e-mail | index | archive | help
Sent this to livingston support, but it may be a FreeBSD issue or config problem, so I'm posting it here to. If anyone has any suggestions please let me know. Somehow it seems a once gentle and quiet network as turned itself into a segemented monster. :-) ---------- Forwarded message ---------- Date: Sun, 17 Mar 1996 09:33:54 -0800 (PST) From: Robert Du Gaue <rdugaue@calweb.com> To: support@livingston.com Subject: ARP ARP ARP ARP I seem to be having a problem that poped up recently (and I can't connect it to any network changes, except for adding my 7th portmaster...). Some on my FreeBSD machines are not learning the ARP address of the Portmasters which cause them to appear as if they are not on the backbone. One machine will look like this : 165.90.138.26 0:c0:5:1:d:25 UHLW 6 0 de0 1184 165.90.138.27 0:c0:5:1:1e:48 UHLW 1 0 de0 1166 165.90.138.28 0:c0:5:1:2e:f6 UHLW 18 0 de0 1197 165.90.138.29 0:c0:5:1:2a:d2 UHLW 0 0 de0 1144 165.90.138.30 0:c0:5:1:36:e UHLW 0 0 de0 1144 165.90.138.31 0:c0:5:1:36:ea UHLW 0 0 de0 1144 165.90.138.32 0:c0:5:1:42:bf UHLW 0 0 de0 1142 Where .26 - .32 are my Portmasters (display obtained using netstat -nr) And yet I have other machines that show: 165.90.138.26 0:c0:5:1:d:25 UHLW 52 21552 de0 1184 165.90.138.27 0:c0:5:1:1e:48 UHLW 5 5015 de0 1166 165.90.138.28 0:c0:5:1:2e:f6 UHLW 27 1427628 de0 1197 165.90.138.29 0:c0:5:1:2a:d2 UHLW 2 170850 de0 1200 => 165.90.138.29 0:c0:5:1:2a:d2 ULS2c 0 0 de0 165.90.138.177 165.90.138.27 UGH 0 0 de0 177 is a user IP, but most importantly 30,31, and 32 are all missing. If I try to force them into the table I get an error that says the interface can intuit the info and rejects it (almost as if the machine thinks the PMs are not on the network!). Another machine shows: 165.90.138.26 0:c0:5:1:d:25 UHLW 2 302561 de0 1167 165.90.138.27 0:c0:5:1:1e:48 UHLW 5 132302 de0 1149 165.90.138.28 0:c0:5:1:2e:f6 UHLW 20 2 de0 1180 165.90.138.29 0:c0:5:1:2a:d2 UHLW 3 5457 de0 1123 165.90.138.30 0:c0:5:1:36:e UHLW 9 104374 de0 1185 165.90.138.32 0:c0:5:1:42:bf UHLW 0 8955 de0 1185 165.90.138.177 165.90.138.27 UGH 0 0 de0 SO this one is only missing .31. Because of this I get routing problems when some comes in from that portmaster on a machine that doesn't know the arp. My Internet Router (a xyplex) will broadcast a redirect telling the machine that the IP coming in is for .31 so the machine learns a route that'll direct that IP to .31, which since it doesn't know the arp address a bogus gateway is defined and all traffic after that doesn't get there. :( Any ideas first why some machines are not learning Portmaster ARPS while others seem to be just fine? I even tried configuring my xyplex to route all assigned IP traffic to my .26 Portmaster (the first one I got), but even then .26 doesn't seem to be learning routes and the traffic for some portmasters will then bounce back and forth between WRONG portmasters. (this might be a different problem, but I wanted to mention it incase it's related). Please note, this routing problem was asked by my unix admin about 2 weeks ago and no reply has yet to be given... Your prompt action on this would be very helpful. If you need access to the system or the portmasters let me know and I'll adjust passwords accordingly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960317120202.1254B-100000>