Re: arpresolve: can't allocate llinfo for 255.255.255.0rt
Can anyone explain how or where the 199.15.320xc70f22 entry could have come from? I've been unable to remove it ... Have you tried route -delete 199.15.32.0 -netmask 199.15.34.0? (I'm guessing at the .0 part; it got truncated. netstat -nrA might help figure out what it really is) (I can't explain where it came from, other than maybe an oddly typo'd command; maybe a route add instead of an ifconfig?) Bill To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
arpresolve: can't allocate llinfo for 255.255.255.0rt
I started getting these messages in the daily security output. arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt Upon inspection of the routing table I see this (mikej@hobbs) /usr/home/mikej$netstat -r Routing tables Internet: DestinationGatewayFlags Refs Use Netif Expire defaultc5500-rsm-vlan10 UGSc851872 tl0 localhost localhost UH 00 lo0 129.2.1/24 link#2 UC 00 de0 199.15/16 link#1 UC 00 tl0 199.15.32 c5500-rsm-vlan10 UGSc00 tl0 = 199.15.320xc70f22 255.255.255.0 UGSc0 185 tl0 c5500-rsm-vlan10 0:e0:34:a1:84:0UHLW50 tl0 1198 calvin 0:80:5f:cb:de:16 UHLW122152 tl0 67 Can anyone explain how or where the "199.15.320xc70f22" entry could have come from? I've been unable to remove it and don't have a window to reload the server for several days. Thanks-- Michael Jung(502) 315-2457 Voice Senior Network Specialist (502) 315-2815 Facsimile National Processing Company, Inc. [EMAIL PROTECTED] 1231 Durrett Lane MJ548 Louisville, KY 40285 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: arpresolve: can't allocate llinfo for 255.255.255.0rt
On Thu, Jul 22, 1999 at 09:30:28AM -0400, Jung, Michael wrote: I started getting these messages in the daily security output. arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt I get those after a long run of nmap on our /16 network. At this point, I just kill nmap and the problem goes away. I didn't bother looking into the routing table though. Maybe it's time to see what the PC support monkeys have plugged into my network again. :-) -- Dom Mitchell -- Palmer Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
arpresolve: can't allocate llinfo for 255.255.255.0rt
I started getting these messages in the daily security output. arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt Upon inspection of the routing table I see this (mi...@hobbs) /usr/home/mikej$netstat -r Routing tables Internet: DestinationGatewayFlags Refs Use Netif Expire defaultc5500-rsm-vlan10 UGSc851872 tl0 localhost localhost UH 00 lo0 129.2.1/24 link#2 UC 00 de0 199.15/16 link#1 UC 00 tl0 199.15.32 c5500-rsm-vlan10 UGSc00 tl0 = 199.15.320xc70f22 255.255.255.0 UGSc0 185 tl0 c5500-rsm-vlan10 0:e0:34:a1:84:0UHLW50 tl0 1198 calvin 0:80:5f:cb:de:16 UHLW122152 tl0 67 Can anyone explain how or where the 199.15.320xc70f22 entry could have come from? I've been unable to remove it and don't have a window to reload the server for several days. Thanks-- Michael Jung(502) 315-2457 Voice Senior Network Specialist (502) 315-2815 Facsimile National Processing Company, Inc. mj...@npc.net 1231 Durrett Lane MJ548 Louisville, KY 40285 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: arpresolve: can't allocate llinfo for 255.255.255.0rt
On Thu, Jul 22, 1999 at 09:30:28AM -0400, Jung, Michael wrote: I started getting these messages in the daily security output. arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt arpresolve: can't allocate llinfo for 255.255.255.0rt I get those after a long run of nmap on our /16 network. At this point, I just kill nmap and the problem goes away. I didn't bother looking into the routing table though. Maybe it's time to see what the PC support monkeys have plugged into my network again. :-) -- Dom Mitchell -- Palmer Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
