arplookup messages? now what have I done?
I recently added some aliases to my ipconfig and now I'm getting these system messages? Should I be concerned? (FreeBSD 4.6) Feb 3 02:24:23 freedom /kernel: arplookup XXX.XXX.XX.XX failed: host is not on local network Feb 3 00:17:35 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:17:35 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:17:35 freedom sm-mta[94]: gethostbyaddr(IPv6:::1) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(XXX.XXX.XX.XX) failed: 1 Feb 3 00:38:26 freedom sm-mta[94]: gethostbyaddr(IPv6:::1) failed: 1 And... these ones too arplookup XXX.XXX.XX.XX failed: host is not on local network arplookup XXX.XXX.XX.XX failed: host is not on local network Feb 5 03:03:57 freedom /kernel: arplookup XXX.XXX.XX.XX failed: host is not on local network arplookup XXX.XXX.XX.XX failed: host is not on local network arplookup XXX.XXX.XX.XX failed: host is not on local network Feb 5 03:04:57 freedom last message repeated 3 times arplookup XXX.XXX.XX.XX failed: host is not on local network Feb 5 06:16:56 freedom /kernel: arplookup XXX.XXX.XX.XXfailed: host is not on local And here's the rc.conf file ifconfig_de0=inet XXX.168.0.219 netmask 255.255.255.0 ifconfig_tl0=inet XXX.82.15.219 netmask 255.255.255.240 ifconfig_tl0_alias0=inet XXX.82.15.220 netmask 0x ifconfig_tl0_alias1=inet XXX.82.15.221 netmask 0x ifconfig_tl0_alias2=inet XXX.82.15.222 netmask 0x ifconfig_tl0_alias3=inet XXX.167.176.107 netmask 0x ifconfig_tl0_alias4=inet XXX.167.176.108 netmask 0x ifconfig_tl0_alias5=inet XXX.167.176.109 netmask 0x ifconfig_tl0_alias6=inet XXX.167.176.110 netmask 0x -- Phillip To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: arplookup messages? now what have I done?
mailing list said: I recently added some aliases to my ipconfig and now I'm getting these system messages? Should I be concerned? (FreeBSD 4.6) snip ifconfig_de0=inet XXX.168.0.219 netmask 255.255.255.0 ifconfig_tl0=inet XXX.82.15.219 netmask 255.255.255.240 snip ifconfig_tl0_alias3=inet XXX.167.176.107 netmask 0x ifconfig_tl0_alias4=inet XXX.167.176.108 netmask 0x ifconfig_tl0_alias5=inet XXX.167.176.109 netmask 0x ifconfig_tl0_alias6=inet XXX.167.176.110 netmask 0x Hey: Your interface is in xxx.168.0.0/24 and your aliases are in xxx.167.0.0/24. Those are two different subnets. You need to configure your aliases in xxx.168.0.0 or reconfigure the interface into xxx.167.0.0. Or, you could extend your subnet mask to a /22 (255.255.252.0) (you can't use a /23 because it won't inlude 167 and 168). Mike -- Michael K. Smith Senior Network and Systems Engineer - NoaNet [EMAIL PROTECTED] 206.219.7116 NOC: 866.662.6380 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: arplookup messages? now what have I done?
Hi Michael, My network topology skills are limited... does this mean the following: - my default gateway is on a 255.255.255.240 subnet - so is my devices real address - there is another device listed there (de0), no problems (internal) So, if I change the aliased devices to 0xff0 (255.255.255.240), they will be a-ok and not produce those message? I believe I had it set like that and the devices wouldn't initiate? Many thanks in advance, phillip. -Original Message- From: Michael K. Smith [mailto:[EMAIL PROTECTED]] Sent: February 6, 2003 3:28 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: arplookup messages? now what have I done? mailing list said: I recently added some aliases to my ipconfig and now I'm getting these system messages? Should I be concerned? (FreeBSD 4.6) snip ifconfig_de0=inet XXX.168.0.219 netmask 255.255.255.0 ifconfig_tl0=inet XXX.82.15.219 netmask 255.255.255.240 snip ifconfig_tl0_alias3=inet XXX.167.176.107 netmask 0x ifconfig_tl0_alias4=inet XXX.167.176.108 netmask 0x ifconfig_tl0_alias5=inet XXX.167.176.109 netmask 0x ifconfig_tl0_alias6=inet XXX.167.176.110 netmask 0x Hey: Your interface is in xxx.168.0.0/24 and your aliases are in xxx.167.0.0/24. Those are two different subnets. You need to configure your aliases in xxx.168.0.0 or reconfigure the interface into xxx.167.0.0. Or, you could extend your subnet mask to a /22 (255.255.252.0) (you can't use a /23 because it won't inlude 167 and 168). Mike -- Michael K. Smith Senior Network and Systems Engineer - NoaNet [EMAIL PROTECTED] 206.219.7116 NOC: 866.662.6380 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: arplookup messages? now what have I done?
mailing list\ said: Hi Michael, My network topology skills are limited... does this mean the following: - my default gateway is on a 255.255.255.240 subnet - so is my devices real address - there is another device listed there (de0), no problems (internal) So, if I change the aliased devices to 0xff0 (255.255.255.240), they will be a-ok and not produce those message? I believe I had it set like that and the devices wouldn't initiate? Many thanks in advance, Hey Phillip: You have three things that need to line up in order for this to work: 1) The IP Address 2) The subnet mask 3) The alias and its associated interface In your example: ifconfig_de0=inet XXX.168.0.219 netmask 255.255.255.0 ifconfig_tl0=inet XXX.82.15.219 netmask 255.255.255.240 snip ifconfig_tl0_alias3=inet XXX.167.176.107 netmask 0x ifconfig_tl0_alias4=inet XXX.167.176.108 netmask 0x ifconfig_tl0_alias5=inet XXX.167.176.109 netmask 0x ifconfig_tl0_alias6=inet XXX.167.176.110 netmask 0x The subnet mask for xxx.82.15.219 would mean you could use addresses that are masked when the subnet mask is applied. I would recommend reading up on masking in your copious free time. Suffice it to say that, in this case, the following is true: xxx.82.15.208 - xxx.82.15.223 is the address range, with .208 and .223 reserved. If you want to have your aliases attached to the tl0 interface, you need to use addresses in that range. So, something like: ifconfig_tl0_alias3=inet XXX.82.15.210 netmask 0x Also, I would recommend using the .209 or .222 address (first and last useable in the subnet) as your tl0 (default gateway) interface. It's standard operating procedure and will help you in the troubleshooting process to have things fairly standardized. If you set your interface to .209, then you could set interface aliases from .210 to .222 inclusive. Mike -- Michael K. Smith Senior Network and Systems Engineer - NoaNet [EMAIL PROTECTED] 206.219.7116 NOC: 866.662.6380 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: arplookup messages? now what have I done?
Hmmm, I'm confused If you want to have your aliases attached to the tl0 interface, you need to use addresses in that range. So, something like: ifconfig_tl0_alias3=inet XXX.82.15.210 netmask 0x That's what I have, and I'm getting those funny arplookup error messages. The subnet mask for xxx.82.15.219 would mean you could use addresses that are masked when the subnet mask is applied. I would recommend reading up on masking in your copious free time. I'll definitely have a look around (think I have the CCNA books at home). I have two DSL lines, one provides the 82.15.209+ and the other the 167.176.x, but both have the same 255.255.255.240 subnet. I'm thinking that this may have something to do with the messages? phillip. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
