Re: arp panic

[Hans Petter Selasky]

On 02/04/17 07:43, Chagin Dmitry wrote:


chd.heemeyer.club dumped core - see /var/crash/vmcore.8

Sat Feb  4 09:01:35 MSK 2017

FreeBSD chd.heemeyer.club 12.0-CURRENT FreeBSD 12.0-CURRENT #237 
r313172+c19dc6ff09(lemul): Fri Feb  3 22:38:44 MSK 2017 
r...@chd.heemeyer.club:/home/rootobj/home/git/head/sys/YOY  amd64

panic:

GNU gdb (GDB) 7.12 [GDB v7.12 for FreeBSD]
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd12.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /boot/kernel/kernel...Reading symbols from 
/usr/lib/debug//boot/kernel/kernel.debug...done.
done.

Unread portion of the kernel message buffer:


Fatal trap 9: general protection fault while in kernel mode
cpuid = 3; apic id = 03
instruction pointer = 0x20:0x807833ed
stack pointer   = 0x28:0xfe032db70430
frame pointer   = 0x28:0xfe032db704f0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 11 (swi4: clock (0))

Reading symbols from /boot/kernel/drm2.ko...Reading symbols from 
/usr/lib/debug//boot/kernel/drm2.ko.debug...done.
done.
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from 
/usr/lib/debug//boot/kernel/linprocfs.ko.debug...done.
done.
Reading symbols from /boot/kernel/pseudofs.ko...Reading symbols from 
/usr/lib/debug//boot/kernel/pseudofs.ko.debug...done.
done.
Reading symbols from /boot/kernel/linux_common.ko...Reading symbols from 
/usr/lib/debug//boot/kernel/linux_common.ko.debug...done.
done.
Reading symbols from /boot/kernel/procfs.ko...Reading symbols from 
/usr/lib/debug//boot/kernel/procfs.ko.debug...done.
done.
Reading symbols from /boot/kernel/i915kms.ko...Reading symbols from 
/usr/lib/debug//boot/kernel/i915kms.ko.debug...done.
done.
doadump (textdump=766966752) at /home/git/head/sys/kern/kern_shutdown.c:318
318 dumptid = curthread->td_tid;
(kgdb) #0  doadump (textdump=766966752)
at /home/git/head/sys/kern/kern_shutdown.c:318
#1  0x803fbcc5 in db_fncall_generic (addr=-2139566720,
rv=0xfe032db6fb90, nargs=0, args=0xfe032db6fba0)
at /home/git/head/sys/ddb/db_command.c:581
#2  0x803fb284 in db_fncall (dummy1=-2185371386672, dummy2=false,
dummy3=0, dummy4=0xfe032db6fcd0 "\360\374\266-\003\376\377\377")
at /home/git/head/sys/ddb/db_command.c:629
#3  0x803fabee in db_command (
last_cmdp=0x81703940 , cmd_table=0x0, dopager=1)
at /home/git/head/sys/ddb/db_command.c:453
#4  0x803fa789 in db_command_loop ()
at /home/git/head/sys/ddb/db_command.c:506
#5  0x803ff5da in db_trap (type=9, code=0)
at /home/git/head/sys/ddb/db_main.c:248
#6  0x807f6b3f in kdb_trap (type=9, code=0, tf=0xfe032db70370)
at /home/git/head/sys/kern/subr_kdb.c:654
#7  0x80ceb21c in trap_fatal (frame=0xfe032db70370, eva=0)
at /home/git/head/sys/amd64/amd64/trap.c:819
#8  0x80cea651 in trap (frame=0xfe032db70370)
at /home/git/head/sys/amd64/amd64/trap.c:553
#9  0x80cebd2a in trap_check (frame=0xfe032db70370)
at /home/git/head/sys/amd64/amd64/trap.c:625
#10 
#11 0x807833ed in _rw_wlock_cookie (c=0xdeadc0dedeadc2de,
file=0x80ea3d10 "/home/git/head/sys/netinet/if_ether.c", line=287)
at /home/git/head/sys/kern/kern_rwlock.c:295
#12 0x80a2c723 in arptimer (arg=0xf80007d67a00)
at /home/git/head/sys/netinet/if_ether.c:287
#13 0x807b60bc in softclock_call_cc (c=0xf80007d67ab8,
cc=0x81a31a00 , direct=0)
at /home/git/head/sys/kern/kern_timeout.c:729
#14 0x807b68ec in softclock (arg=0x81a31a00 )
at /home/git/head/sys/kern/kern_timeout.c:867
#15 0x807350c8 in intr_event_execute_handlers (p=0xf80003df9000,
ie=0xf80003deea00) at /home/git/head/sys/kern/kern_intr.c:1262
#16 0x80735e57 in ithread_execute_handlers (p=0xf80003df9000,
ie=0xf80003deea00) at /home/git/head/sys/kern/kern_intr.c:1275
#17 0x80735c86 in ithread_loop (arg=0xf80003e30060)
at /home/git/head/sys/kern/kern_intr.c:1356
#18 0x807306ee in fork_exit (
callout=0x80735b10 , arg=0xf80003e30060,
frame=0xfe032db70ac0) at 

Re: arp flapping after udating system to 11-CURRENT.

[Slawa Olhovchenkov]

On Thu, Feb 04, 2016 at 03:43:05PM -0800, Roger Marquis wrote:

> Slawa Olhovchenkov wrote:
> >> It seems to be flapping between the virtual mac of my bridge interface
> >> and the actual mac adress on the physical interface. This was not the
> >> case when i ran FreeBSD 10.2. Is there some settings I need to do?
> 
> While the documentation says you should assign an IP to the bridge it is 
> probably
> not a good idea, code aside, since bridges are layer 2 devices and IPs are
> layer 3.

bridge members also are layer 2 devices
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Roger Marquis]

Slawa Olhovchenkov wrote:
>> It seems to be flapping between the virtual mac of my bridge interface
>> and the actual mac adress on the physical interface. This was not the
>> case when i ran FreeBSD 10.2. Is there some settings I need to do?

While the documentation says you should assign an IP to the bridge it is 
probably
not a good idea, code aside, since bridges are layer 2 devices and IPs are
layer 3.

Haven't seen this issue while testing if_bridge/epair under 11-CURRENT but also
have not been assigning IPs to bridges, only to bridge members.

Roger Marquis



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Slawa Olhovchenkov]

On Wed, Feb 03, 2016 at 08:31:43AM +0100, Peter Ankerstål wrote:

> Hi!
> 
> I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
> r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
> devices in the network complains about arp-flapping:
> 
> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> 
> 
> It seems to be flapping between the virtual mac of my bridge interface 
> and the actual mac adress on the physical interface. This was not the 
> case when i ran FreeBSD 10.2. Is there some settings I need to do?

I am see this on FreeBSD 10. And FreeBSD 9.
Only switch to ng_bridge remove this for me.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Adrian Chadd]

Sorry, must've missed that...

:(


-a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Allan Jude]

On 2016-02-03 12:36, Chris H wrote:
> On Wed, 3 Feb 2016 11:13:21 -0500 Allan Jude  wrote
> 
>> On 2016-02-03 10:32, Chris H wrote:
>>> On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H"  wrote
>>>
 On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål  wrote

> Hi!
>
> I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
> r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
> devices in the network complains about arp-flapping:
>
> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
>
 FWIW I'm seeing this too. As it happened; I had just changed upstream
 providers, getting a larger static block (IP's), as well as updating
 my long overdue -CURRENT. So I simply blamed it on their (upstream)
 network. I'd love to get to the bottom of this, and would be happy to
 help.

 FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
 Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX
 amd64 >>
 src is at Revision: 406193

>>> Well, it would have helped if I had also mentioned that I'm not using
>>> a bridge, and list the interfaces involved. :/
>>>
>>> nfe0: flags=8843 metric 0 mtu 1500
>>> options=82008
>>>
>>> This also occurs on my 9-STABLE boxes
>>> re0: flags=8843 metric 0 mtu 1500  
>>>
>>>
> options=8209b>> KSTATE> 
>>> nfe0: flags=8843 metric 0 mtu 1500
>>> options=82008
>>>
>>> nfe0: flags=8843 metric 0 mtu 1500
>>> options=82008
>>>
>>> --Chris

>
> It seems to be flapping between the virtual mac of my bridge interface 
> and the actual mac adress on the physical interface. This was not the 
> case when i ran FreeBSD 10.2. Is there some settings I need to do?
>
>
> bridge0: flags=8843 metric 0 mtu 
> 1500
>  description: wired <-> wifi bridge
>  ether 02:e8:ea:15:66:00
>  inet 172.25.0.1 netmask 0xff00 broadcast 172.25.0.255
>  inet6 2001:470:de59::1 prefixlen 64
>  inet6 fe80::2%bridge0 prefixlen 64 scopeid 0xb
>  nd6 options=1
>  groups: bridge
>  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
>  member: wlan2 flags=143
>  ifmaxaddr 0 port 10 priority 128 path cost 6
>  member: wlan1 flags=143
>  ifmaxaddr 0 port 9 priority 128 path cost 6
>  member: wlan0 flags=143
>  ifmaxaddr 0 port 8 priority 128 path cost 2
>  member: em1 flags=143
>  ifmaxaddr 0 port 2 priority 128 path cost 200
>
> em1: flags=8943 metric 0 
> mtu 1500
>  description: wired LAN
>  
> options=42098
>  ether 00:00:24:d0:9e:5d
>  nd6 options=29
>  media: Ethernet autoselect (1000baseT )
>  status: active
>
>
> /Peter.

>>
>> Chris:
>> If you are not using a bridge, please provide the complete output of
>> ifconfig, and the log messages about the arp flapping, so we can see
>> which two interfaces it is bouncing between.
>>
> Thank you very much for the reply, Allan.
> This is what I'm working with/experiencing:
> 
> Logs from just one of the offending boxes, the same is echoed in the
> other boxes' logs, as well
> Feb  3 08:04:48 udns kernel: arp: XX.YY.ZZ.85 moved from 00:24:81:ce:ba:87 to
> 00:17:10:8e:5e:87 on re0
> Feb  3 08:05:58 udns kernel: arp: XX.YY.ZZ.83 moved from 40:61:86:cd:44:97 to
> 00:17:10:8e:5e:87 on re0
> Feb  3 08:08:10 udns kernel: arp: XX.YY.ZZ.83 moved from 00:17:10:8e:5e:87 to
> 40:61:86:cd:44:97 on re0
> Feb  3 08:13:00 udns kernel: arp: XX.YY.ZZ.84 moved from 00:17:10:8e:5e:87 to
> 00:30:67:5e:29:5d on re0
> Feb  3 08:25:40 udns kernel: arp: XX.YY.ZZ.85 moved from 00:24:81:ce:ba:87 to
> 00:17:10:8e:5e:87 on re0
> Feb  3 08:30:37 udns kernel: arp: XX.YY.ZZ.83 moved from 

Re: arp flapping after udating system to 11-CURRENT.

[Chris H]

On Wed, 3 Feb 2016 11:37:30 -0800 Adrian Chadd  wrote

> Hi,
> 
> Are these interfaces in a bridge group?
No.
> Why are you putting the IP on
> the physical interface, instead of the bridgeX interface?
Which is why the IP's are set per interface. :)
I stated that in at *least* one of my replies. :)
> 
> 
> -a
Thanks for the reply, Adrian.

--Chris


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Chris H]

On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål  wrote

> Hi!
> 
> I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
> r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
> devices in the network complains about arp-flapping:
> 
> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> 
FWIW I'm seeing this too. As it happened; I had just changed upstream
providers, getting a larger static block (IP's), as well as updating
my long overdue -CURRENT. So I simply blamed it on their (upstream)
network. I'd love to get to the bottom of this, and would be happy to
help.

FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX amd64

src is at Revision: 406193

--Chris

> 
> It seems to be flapping between the virtual mac of my bridge interface 
> and the actual mac adress on the physical interface. This was not the 
> case when i ran FreeBSD 10.2. Is there some settings I need to do?
> 
> 
> bridge0: flags=8843 metric 0 mtu 
> 1500
>  description: wired <-> wifi bridge
>  ether 02:e8:ea:15:66:00
>  inet 172.25.0.1 netmask 0xff00 broadcast 172.25.0.255
>  inet6 2001:470:de59::1 prefixlen 64
>  inet6 fe80::2%bridge0 prefixlen 64 scopeid 0xb
>  nd6 options=1
>  groups: bridge
>  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
>  member: wlan2 flags=143
>  ifmaxaddr 0 port 10 priority 128 path cost 6
>  member: wlan1 flags=143
>  ifmaxaddr 0 port 9 priority 128 path cost 6
>  member: wlan0 flags=143
>  ifmaxaddr 0 port 8 priority 128 path cost 2
>  member: em1 flags=143
>  ifmaxaddr 0 port 2 priority 128 path cost 200
> 
> em1: flags=8943 metric 0 
> mtu 1500
>  description: wired LAN
>  
> options=42098
>  ether 00:00:24:d0:9e:5d
>  nd6 options=29
>  media: Ethernet autoselect (1000baseT )
>  status: active
> 
> 
> /Peter.


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Chris H]

On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H"  wrote

> On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål  wrote
> 
> > Hi!
> > 
> > I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
> > r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
> > devices in the network complains about arp-flapping:
> > 
> > arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> > arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
> > arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> > 
> FWIW I'm seeing this too. As it happened; I had just changed upstream
> providers, getting a larger static block (IP's), as well as updating
> my long overdue -CURRENT. So I simply blamed it on their (upstream)
> network. I'd love to get to the bottom of this, and would be happy to
> help.
> 
> FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
> Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX amd64
> 
> src is at Revision: 406193
> 
Well, it would have helped if I had also mentioned that I'm not using
a bridge, and list the interfaces involved. :/

nfe0: flags=8843 metric 0 mtu 1500
options=82008

This also occurs on my 9-STABLE boxes
re0: flags=8843 metric 0 mtu 1500  
options=8209b

nfe0: flags=8843 metric 0 mtu 1500
options=82008

nfe0: flags=8843 metric 0 mtu 1500
options=82008

--Chris
> 
> > 
> > It seems to be flapping between the virtual mac of my bridge interface 
> > and the actual mac adress on the physical interface. This was not the 
> > case when i ran FreeBSD 10.2. Is there some settings I need to do?
> > 
> > 
> > bridge0: flags=8843 metric 0 mtu 
> > 1500
> >  description: wired <-> wifi bridge
> >  ether 02:e8:ea:15:66:00
> >  inet 172.25.0.1 netmask 0xff00 broadcast 172.25.0.255
> >  inet6 2001:470:de59::1 prefixlen 64
> >  inet6 fe80::2%bridge0 prefixlen 64 scopeid 0xb
> >  nd6 options=1
> >  groups: bridge
> >  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
> >  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> >  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
> >  member: wlan2 flags=143
> >  ifmaxaddr 0 port 10 priority 128 path cost 6
> >  member: wlan1 flags=143
> >  ifmaxaddr 0 port 9 priority 128 path cost 6
> >  member: wlan0 flags=143
> >  ifmaxaddr 0 port 8 priority 128 path cost 2
> >  member: em1 flags=143
> >  ifmaxaddr 0 port 2 priority 128 path cost 200
> > 
> > em1: flags=8943 metric 0 
> > mtu 1500
> >  description: wired LAN
> >  
> > options=42098
> >  ether 00:00:24:d0:9e:5d
> >  nd6 options=29
> >  media: Ethernet autoselect (1000baseT )
> >  status: active
> > 
> > 
> > /Peter.
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Chris H]

On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H"  wrote

> On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål  wrote
> 
> > Hi!
> > 
> > I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
> > r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
> > devices in the network complains about arp-flapping:
> > 
> > arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> > arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
> > arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> > 
> FWIW I'm seeing this too. As it happened; I had just changed upstream
> providers, getting a larger static block (IP's), as well as updating
> my long overdue -CURRENT. So I simply blamed it on their (upstream)
> network. I'd love to get to the bottom of this, and would be happy to
> help.
> 
> FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
> Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX amd64
> 
> src is at Revision: 406193
> 
Well, it would have helped if I had also mentioned that I'm not using
a bridge, and list the interfaces involved. :/

nfe0: flags=8843 metric 0 mtu 1500
options=82008

This also occurs on my 9-STABLE boxes
re0: flags=8843 metric 0 mtu 1500  
options=8209b

nfe0: flags=8843 metric 0 mtu 1500
options=82008

nfe0: flags=8843 metric 0 mtu 1500
options=82008

--Chris
> 
> > 
> > It seems to be flapping between the virtual mac of my bridge interface 
> > and the actual mac adress on the physical interface. This was not the 
> > case when i ran FreeBSD 10.2. Is there some settings I need to do?
> > 
> > 
> > bridge0: flags=8843 metric 0 mtu 
> > 1500
> >  description: wired <-> wifi bridge
> >  ether 02:e8:ea:15:66:00
> >  inet 172.25.0.1 netmask 0xff00 broadcast 172.25.0.255
> >  inet6 2001:470:de59::1 prefixlen 64
> >  inet6 fe80::2%bridge0 prefixlen 64 scopeid 0xb
> >  nd6 options=1
> >  groups: bridge
> >  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
> >  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> >  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
> >  member: wlan2 flags=143
> >  ifmaxaddr 0 port 10 priority 128 path cost 6
> >  member: wlan1 flags=143
> >  ifmaxaddr 0 port 9 priority 128 path cost 6
> >  member: wlan0 flags=143
> >  ifmaxaddr 0 port 8 priority 128 path cost 2
> >  member: em1 flags=143
> >  ifmaxaddr 0 port 2 priority 128 path cost 200
> > 
> > em1: flags=8943 metric 0 
> > mtu 1500
> >  description: wired LAN
> >  
> > options=42098
> >  ether 00:00:24:d0:9e:5d
> >  nd6 options=29
> >  media: Ethernet autoselect (1000baseT )
> >  status: active
> > 
> > 
> > /Peter.
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp flapping after udating system to 11-CURRENT.

[Allan Jude]

On 2016-02-03 10:32, Chris H wrote:
> On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H"  wrote
> 
>> On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål  wrote
>>
>>> Hi!
>>>
>>> I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
>>> r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
>>> devices in the network complains about arp-flapping:
>>>
>>> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
>>> arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
>>> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
>>>
>> FWIW I'm seeing this too. As it happened; I had just changed upstream
>> providers, getting a larger static block (IP's), as well as updating
>> my long overdue -CURRENT. So I simply blamed it on their (upstream)
>> network. I'd love to get to the bottom of this, and would be happy to
>> help.
>>
>> FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
>> Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX amd64
>>
>> src is at Revision: 406193
>>
> Well, it would have helped if I had also mentioned that I'm not using
> a bridge, and list the interfaces involved. :/
> 
> nfe0: flags=8843 metric 0 mtu 1500
> options=82008
> 
> This also occurs on my 9-STABLE boxes
> re0: flags=8843 metric 0 mtu 1500  
> options=8209b
> 
> nfe0: flags=8843 metric 0 mtu 1500
> options=82008
> 
> nfe0: flags=8843 metric 0 mtu 1500
> options=82008
> 
> --Chris
>>
>>>
>>> It seems to be flapping between the virtual mac of my bridge interface 
>>> and the actual mac adress on the physical interface. This was not the 
>>> case when i ran FreeBSD 10.2. Is there some settings I need to do?
>>>
>>>
>>> bridge0: flags=8843 metric 0 mtu 
>>> 1500
>>>  description: wired <-> wifi bridge
>>>  ether 02:e8:ea:15:66:00
>>>  inet 172.25.0.1 netmask 0xff00 broadcast 172.25.0.255
>>>  inet6 2001:470:de59::1 prefixlen 64
>>>  inet6 fe80::2%bridge0 prefixlen 64 scopeid 0xb
>>>  nd6 options=1
>>>  groups: bridge
>>>  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>>>  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>>>  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
>>>  member: wlan2 flags=143
>>>  ifmaxaddr 0 port 10 priority 128 path cost 6
>>>  member: wlan1 flags=143
>>>  ifmaxaddr 0 port 9 priority 128 path cost 6
>>>  member: wlan0 flags=143
>>>  ifmaxaddr 0 port 8 priority 128 path cost 2
>>>  member: em1 flags=143
>>>  ifmaxaddr 0 port 2 priority 128 path cost 200
>>>
>>> em1: flags=8943 metric 0 
>>> mtu 1500
>>>  description: wired LAN
>>>  
>>> options=42098
>>>  ether 00:00:24:d0:9e:5d
>>>  nd6 options=29
>>>  media: Ethernet autoselect (1000baseT )
>>>  status: active
>>>
>>>
>>> /Peter.
>>
>>
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

Chris:
If you are not using a bridge, please provide the complete output of
ifconfig, and the log messages about the arp flapping, so we can see
which two interfaces it is bouncing between.

-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature

Re: arp flapping after udating system to 11-CURRENT.

[Chris H]

On Wed, 3 Feb 2016 11:13:21 -0500 Allan Jude  wrote

> On 2016-02-03 10:32, Chris H wrote:
> > On Wed, 03 Feb 2016 06:55:47 -0800 "Chris H"  wrote
> > 
> >> On Wed, 3 Feb 2016 08:31:43 +0100 Peter Ankerstål  wrote
> >>
> >>> Hi!
> >>>
> >>> I recently upgraded my system to 11-CURRENT (FreeBSD 11.0-CURRENT #0 
> >>> r295087: Sun Jan 31 10:21:31 CET 2016) and after that all of my other 
> >>> devices in the network complains about arp-flapping:
> >>>
> >>> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> >>> arp: 172.25.0.1 moved from 02:e8:ea:15:66:00 to 00:00:24:d0:9e:5d on re0
> >>> arp: 172.25.0.1 moved from 00:00:24:d0:9e:5d to 02:e8:ea:15:66:00 on re0
> >>>
> >> FWIW I'm seeing this too. As it happened; I had just changed upstream
> >> providers, getting a larger static block (IP's), as well as updating
> >> my long overdue -CURRENT. So I simply blamed it on their (upstream)
> >> network. I'd love to get to the bottom of this, and would be happy to
> >> help.
> >>
> >> FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
> >> Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX
> >> amd64 >>
> >> src is at Revision: 406193
> >>
> > Well, it would have helped if I had also mentioned that I'm not using
> > a bridge, and list the interfaces involved. :/
> > 
> > nfe0: flags=8843 metric 0 mtu 1500
> > options=82008
> > 
> > This also occurs on my 9-STABLE boxes
> > re0: flags=8843 metric 0 mtu 1500  
> >
> >
options=8209b > KSTATE> 
> > nfe0: flags=8843 metric 0 mtu 1500
> > options=82008
> > 
> > nfe0: flags=8843 metric 0 mtu 1500
> > options=82008
> > 
> > --Chris
> >>
> >>>
> >>> It seems to be flapping between the virtual mac of my bridge interface 
> >>> and the actual mac adress on the physical interface. This was not the 
> >>> case when i ran FreeBSD 10.2. Is there some settings I need to do?
> >>>
> >>>
> >>> bridge0: flags=8843 metric 0 mtu 
> >>> 1500
> >>>  description: wired <-> wifi bridge
> >>>  ether 02:e8:ea:15:66:00
> >>>  inet 172.25.0.1 netmask 0xff00 broadcast 172.25.0.255
> >>>  inet6 2001:470:de59::1 prefixlen 64
> >>>  inet6 fe80::2%bridge0 prefixlen 64 scopeid 0xb
> >>>  nd6 options=1
> >>>  groups: bridge
> >>>  id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
> >>>  maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> >>>  root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
> >>>  member: wlan2 flags=143
> >>>  ifmaxaddr 0 port 10 priority 128 path cost 6
> >>>  member: wlan1 flags=143
> >>>  ifmaxaddr 0 port 9 priority 128 path cost 6
> >>>  member: wlan0 flags=143
> >>>  ifmaxaddr 0 port 8 priority 128 path cost 2
> >>>  member: em1 flags=143
> >>>  ifmaxaddr 0 port 2 priority 128 path cost 200
> >>>
> >>> em1: flags=8943 metric 0 
> >>> mtu 1500
> >>>  description: wired LAN
> >>>  
> >>> options=42098
> >>>  ether 00:00:24:d0:9e:5d
> >>>  nd6 options=29
> >>>  media: Ethernet autoselect (1000baseT )
> >>>  status: active
> >>>
> >>>
> >>> /Peter.
> >>
> 
> Chris:
> If you are not using a bridge, please provide the complete output of
> ifconfig, and the log messages about the arp flapping, so we can see
> which two interfaces it is bouncing between.
> 
Thank you very much for the reply, Allan.
This is what I'm working with/experiencing:

Logs from just one of the offending boxes, the same is echoed in the
other boxes' logs, as well
Feb  3 08:04:48 udns kernel: arp: XX.YY.ZZ.85 moved from 00:24:81:ce:ba:87 to
00:17:10:8e:5e:87 on re0
Feb  3 08:05:58 udns kernel: arp: XX.YY.ZZ.83 moved from 40:61:86:cd:44:97 to
00:17:10:8e:5e:87 on re0
Feb  3 08:08:10 udns kernel: arp: XX.YY.ZZ.83 moved from 00:17:10:8e:5e:87 to
40:61:86:cd:44:97 on re0
Feb  3 08:13:00 udns kernel: arp: XX.YY.ZZ.84 moved from 00:17:10:8e:5e:87 to
00:30:67:5e:29:5d on re0
Feb  3 08:25:40 udns kernel: arp: XX.YY.ZZ.85 moved from 00:24:81:ce:ba:87 to
00:17:10:8e:5e:87 on re0
Feb  3 08:30:37 udns kernel: arp: XX.YY.ZZ.83 moved from 40:61:86:cd:44:97 to
00:17:10:8e:5e:87 on re0
Feb  3 08:36:05 udns kernel: arp: 

Re: arp flapping after udating system to 11-CURRENT.

[Adrian Chadd]

Hi,

Are these interfaces in a bridge group? Why are you putting the IP on
the physical interface, instead of the bridgeX interface?


-a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Harti Brandt]

On Fri, 19 Oct 2001, Mark Peek wrote:

MPYes, it does appear to be due to this commit. The first address on the
MPinterface queue has an address of 0.0.0.0. Here's a patch that works for
MPme to block the messages. I'm guessing at the correct behavior so use at
MPyour own risk. At least the voices^Wlog messages have stopped. :-)
MP
MPMark

The last commit fixed the problem. Thanks.

harti
-- 
harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Max Khon]

hi, there!

 Same here. My -CURRENT system is replying to those ARP request which carry
 0.0.0.0 as sender IP address:
 
 14:43:33.706099 arp who-has 158.227.48.193 (ff:ff:ff:ff:ff:ff) tell 0.0.0.0
 14:43:33.706152 arp reply 0.0.0.0 is-at 0:d0:b7:3e:a0:fb
 
  I think this is because I have an interface that is up and has NO IP
  address:
 
 I don't think so:
 
 # ifconfig -a
 fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
 inet 158.227.6.52 netmask 0xff00 broadcast 158.227.6.255
 inet6 fe80::2d0:b7ff:fe3e:a0fb%fxp0 prefixlen 64 scopeid 0x1 
 inet6 fec0::9ee3:634 prefixlen 120 
 ether 00:d0:b7:3e:a0:fb 
 media: Ethernet autoselect (100baseTX full-duplex)
 status: active
 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
 inet6 ::1 prefixlen 128 
 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
 inet 127.0.0.1 netmask 0xff00 
 
 Something is broken in the ARP implementation of -CURRENT.

please try this patch (provided by jlemon)

Index: if_ether.c
===
RCS file: /ncvs/src/sys/netinet/if_ether.c,v
retrieving revision 1.85
diff -u -r1.85 if_ether.c
--- if_ether.c  2001/10/17 18:07:05 1.85
+++ if_ether.c  2001/10/19 15:38:07
@@ -593,10 +593,12 @@
isaddr.s_addr == ia-ia_addr.sin_addr.s_addr)
goto match;
/*
-* No match, use the first address on the receive interface
+* No match, use the first inet address on the receive interface
 * as a dummy address for the rest of the function.
 */
-   ifa = TAILQ_FIRST(ifp-if_addrhead);
+   TAILQ_FOREACH(ifa, ifp-if_addrhead, ifa_link)
+   if (ifa-ifa_addr  ifa-ifa_addr-sa_family == AF_INET)
+   break;
if (ifa == NULL) {
m_freem(m);
return;

/fjoe

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Harti Brandt]

On Thu, 18 Oct 2001, Terry Lambert wrote:

TLTo expand a little...
TL
TL That said, it's probably a good idea to never ARP for 0.0.0.0,
TL since a who has in that case is a really dumb idea, since,
TL as weas pointed out, it's intended to mean this host, in the
TL absence of an IP address (i.e. 0.0.0.0 is not an IP address,
TL it's a special value meaning not an IP address).
TL
TLIt's probably also a good idea to make interfaces who have an
TLIP of 0.0.0.0 _not_ respond to ARP requests for that address,
TLand, just in case there are other idiots, we should also not
TLgive proxy ARP responses for that address, etiher.

I have run tcpdump all night to find out what happens. The host receives
an ARP request with a source address of 0.0.0.0:

18:33:51.222688 arp who-has hydra tell 0.0.0.0
 0001 0800 0604 0001 0030 65c6 a174 
     c1af 8755  
       

I think, this may happen if the host does not yet know it's IP address
(DHCP maybe?).

But FreeBSD-current for some unknown reason answers to this request:

18:33:51.222835 arp reply 0.0.0.0 is-at 0:60:97:a:99:f
 0001 0800 0604 0002 0060 970a 990f 
  0030 65c6 a174    
       

and then prints:

Oct 18 18:33:51 scotty /boot/kernel/kernel: arp: 00:30:65:c6:a1:74 is using my IP 
address 0.0.0.0!

I think this is because I have an interface that is up and has NO IP
address:

lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet 127.0.0.1 netmask 0xff00
xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500
inet 193.175.135.70 netmask 0xff00 broadcast 193.175.135.255
ether 00:60:97:0a:99:0f
media: Ethernet 10baseT/UTP (10baseT/UTP half-duplex)

hatm0: flags=841UP,RUNNING,SIMPLEX mtu 9180
media: ATM UTP/155MBit
status: active
lane0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1516
ether 00:00:00:00:00:00

I think it is definitly wrong to assume that an interface with no IP
address has IP address 0.0.0.0

harti

TLGhah.  I hate special cases...

everything is a special case...

harti

TL
TL-- Terry
TL
TLTo Unsubscribe: send mail to [EMAIL PROTECTED]
TLwith unsubscribe freebsd-net in the body of the message
TL

-- 
harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
  [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Jose M. Alcaide]

On Fri, Oct 19, 2001 at 11:12:48AM +0200, Harti Brandt wrote:
 I have run tcpdump all night to find out what happens. The host receives
 an ARP request with a source address of 0.0.0.0:
 
 18:33:51.222688 arp who-has hydra tell 0.0.0.0
  0001 0800 0604 0001 0030 65c6 a174 
      c1af 8755  
        
 
 I think, this may happen if the host does not yet know it's IP address
 (DHCP maybe?).
 
 But FreeBSD-current for some unknown reason answers to this request:
 
 18:33:51.222835 arp reply 0.0.0.0 is-at 0:60:97:a:99:f
  0001 0800 0604 0002 0060 970a 990f 
   0030 65c6 a174    
        
 
 and then prints:
 
 Oct 18 18:33:51 scotty /boot/kernel/kernel: arp: 00:30:65:c6:a1:74 is using my IP 
address 0.0.0.0!

Same here. My -CURRENT system is replying to those ARP request which carry
0.0.0.0 as sender IP address:

14:43:33.706099 arp who-has 158.227.48.193 (ff:ff:ff:ff:ff:ff) tell 0.0.0.0
14:43:33.706152 arp reply 0.0.0.0 is-at 0:d0:b7:3e:a0:fb

 I think this is because I have an interface that is up and has NO IP
 address:

I don't think so:

# ifconfig -a
fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 158.227.6.52 netmask 0xff00 broadcast 158.227.6.255
inet6 fe80::2d0:b7ff:fe3e:a0fb%fxp0 prefixlen 64 scopeid 0x1 
inet6 fec0::9ee3:634 prefixlen 120 
ether 00:d0:b7:3e:a0:fb 
media: Ethernet autoselect (100baseTX full-duplex)
status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128 
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
inet 127.0.0.1 netmask 0xff00 

Something is broken in the ARP implementation of -CURRENT.

  --JMA
-- 
** Jose M. Alcaide  //  [EMAIL PROTECTED]  //  [EMAIL PROTECTED] **
** Beware of Programmers who carry screwdrivers --  Leonard Brandwein **

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Jonathan Lemon]

On Fri, Oct 19, 2001 at 04:58:21PM -0700, Mark Peek wrote:
 At 11:23 AM +0200 10/18/01, Harti Brandt wrote:
 On Thu, 18 Oct 2001, Max Khon wrote:
 
 MKhi, there!
 MK
 MKOn Thu, Oct 18, 2001 at 12:00:52AM +0200, Jose M. Alcaide wrote:
 MK
 MK On Wed, Oct 17, 2001 at 12:11:45PM -0700, Julian Elischer wrote:
 MK  I've seen this when DHCP fails to allocate an address.
 MK 
 MK
 MK But I am not using DHCP. Maybe there are other machines in the LAN (it is
 MK a *big* LAN) trying to get their addresses using DHCP, and now -CURRENT
 MK shows a message whenever detects one of those packets. I will try to
 MK identify the senders (over 40!).
 MK
 MK Anyway, these 0.0.0.0 ARP messages are new in -CURRENT, and none of our
 MK machines running FreeBSD 4.x show them.
 MK
 MKhow current -CURRENT are you running?
 
 I have these two on a yesterday's current and remember that they appeared
 after I saw a commit message approx. 2 weeks ago about adding hashing of
 inet addresses (maybe rev. 1.83 of if_ether.c).
 
 
 Yes, it does appear to be due to this commit. The first address on the
 interface queue has an address of 0.0.0.0. Here's a patch that works for
 me to block the messages. I'm guessing at the correct behavior so use at
 your own risk. At least the voices^Wlog messages have stopped. :-)

Below is the patch that I've sent to the people who reported the
problem, I'm waiting to hear back from them that it works.
-- 
Jonathan

Index: if_ether.c
===
RCS file: /ncvs/src/sys/netinet/if_ether.c,v
retrieving revision 1.85
diff -u -r1.85 if_ether.c
--- if_ether.c  2001/10/17 18:07:05 1.85
+++ if_ether.c  2001/10/19 15:38:07
@@ -593,10 +593,12 @@
isaddr.s_addr == ia-ia_addr.sin_addr.s_addr)
goto match;
/*
-* No match, use the first address on the receive interface
+* No match, use the first inet address on the receive interface
 * as a dummy address for the rest of the function.
 */
-   ifa = TAILQ_FIRST(ifp-if_addrhead);
+   TAILQ_FOREACH(ifa, ifp-if_addrhead, ifa_link)
+   if (ifa-ifa_addr  ifa-ifa_addr-sa_family == AF_INET)
+   break;
if (ifa == NULL) {
m_freem(m);
return;

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Mark Peek]

At 9:14 PM -0500 10/19/01, Jonathan Lemon wrote:
Below is the patch that I've sent to the people who reported the
problem, I'm waiting to hear back from them that it works.

Thanks for the real patch. It appears to work fine on my system. No 
log messages and arps look good so far.

Mark

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Mark Peek]

At 11:23 AM +0200 10/18/01, Harti Brandt wrote:
On Thu, 18 Oct 2001, Max Khon wrote:

MKhi, there!
MK
MKOn Thu, Oct 18, 2001 at 12:00:52AM +0200, Jose M. Alcaide wrote:
MK
MK On Wed, Oct 17, 2001 at 12:11:45PM -0700, Julian Elischer wrote:
MK  I've seen this when DHCP fails to allocate an address.
MK 
MK
MK But I am not using DHCP. Maybe there are other machines in the LAN (it is
MK a *big* LAN) trying to get their addresses using DHCP, and now -CURRENT
MK shows a message whenever detects one of those packets. I will try to
MK identify the senders (over 40!).
MK
MK Anyway, these 0.0.0.0 ARP messages are new in -CURRENT, and none of our
MK machines running FreeBSD 4.x show them.
MK
MKhow current -CURRENT are you running?

I have these two on a yesterday's current and remember that they appeared
after I saw a commit message approx. 2 weeks ago about adding hashing of
inet addresses (maybe rev. 1.83 of if_ether.c).


Yes, it does appear to be due to this commit. The first address on the
interface queue has an address of 0.0.0.0. Here's a patch that works for
me to block the messages. I'm guessing at the correct behavior so use at
your own risk. At least the voices^Wlog messages have stopped. :-)

Mark

--
Index: if_ether.c
===
RCS file: /cvs/freebsd/src/sys/netinet/if_ether.c,v
retrieving revision 1.85
diff -u -r1.85 if_ether.c
--- if_ether.c  2001/10/17 18:07:05 1.85
+++ if_ether.c  2001/10/19 23:53:44
@@ -593,15 +593,19 @@
isaddr.s_addr == ia-ia_addr.sin_addr.s_addr)
goto match;
/*
-* No match, use the first address on the receive interface
-* as a dummy address for the rest of the function.
+* No match, use the first non-0.0.0.0 address on the receive
+* interface as a dummy address for the rest of the function.
 */
-   ifa = TAILQ_FIRST(ifp-if_addrhead);
-   if (ifa == NULL) {
-   m_freem(m);
-   return;
-   }
-   ia = ifatoia(ifa);
+   TAILQ_FOREACH(ifa, ifp-if_addrhead, ifa_link)
+   if (ifatoia(ifa)-ia_addr.sin_addr.s_addr != 0) {
+   ia = ifatoia(ifa);
+   goto match;
+   }
+
+   /* No applicable interface/address so bail... */
+   m_freem(m);
+   return;
+
 match:
myaddr = ia-ia_addr.sin_addr;
if (!bcmp(ar_sha(ah), IF_LLADDR(ifp), ifp-if_addrlen)) {

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Max Khon]

hi, there!

On Thu, Oct 18, 2001 at 12:00:52AM +0200, Jose M. Alcaide wrote:

 On Wed, Oct 17, 2001 at 12:11:45PM -0700, Julian Elischer wrote:
  I've seen this when DHCP fails to allocate an address.
  
 
 But I am not using DHCP. Maybe there are other machines in the LAN (it is
 a *big* LAN) trying to get their addresses using DHCP, and now -CURRENT
 shows a message whenever detects one of those packets. I will try to
 identify the senders (over 40!).
 
 Anyway, these 0.0.0.0 ARP messages are new in -CURRENT, and none of our
 machines running FreeBSD 4.x show them.

how current -CURRENT are you running?

/fjoe

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Jose M. Alcaide]

On Wed, Oct 17, 2001 at 10:55:25PM -0800, Beech Rintoul wrote:
 On Wed, 17 Oct 2001, Jose M. Alcaide wrote:
  After rebuilding the kernel two days ago (Oct 15), I am getting lots of
  messages like these:
 
  arp: 00:30:65:de:99:32 is using my IP address 0.0.0.0!
  arp: 00:0a:27:b0:a7:06 is using my IP address 0.0.0.0!
  arp: 00:30:65:d1:2f:cc is using my IP address 0.0.0.0!
  arp: 00:30:65:e9:57:5e is using my IP address 0.0.0.0!
 
  and so on.
 
  Neither ifconfig(8) nor arp(8) show anything unusual.
 
 
 I'm having the exact same problem. I connect to a large subnet  /12 and I'm 
 getting flooded with these. This just started about a week ago. I'm also not 
 using DHCP. Any way of blocking this short of turning off all kernel messages?

I found something interesting: these messages are caused by ARP requests
carrying 0.0.0.0 as the sender IP address. All of them come from Apple
Macintosh (over 40 different machines). I am not sure whether 0.0.0.0 is a
legal sender IP address in an ARP request; 0.0.0.0 means this host, so
that I think that it is a valid address when the machine doing the ARP
request does not know its IP address yet (though this sounds stupid).

Anyway, the fact is that -CURRENT can flood the console and
/var/log/messages if there are many Macintosh sending these ARP requests
in a LAN (as it is our case). I think that there is no reason to printf
these messages, since 0.0.0.0 is a valid IP address meaning this host.

-- 
** Jose M. Alcaide  //  [EMAIL PROTECTED]  //  [EMAIL PROTECTED] **
** Beware of Programmers who carry screwdrivers --  Leonard Brandwein **

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Terry Lambert]

Jose M. Alcaide wrote:
 I found something interesting: these messages are caused by ARP requests
 carrying 0.0.0.0 as the sender IP address. All of them come from Apple
 Macintosh (over 40 different machines). I am not sure whether 0.0.0.0 is a
 legal sender IP address in an ARP request; 0.0.0.0 means this host, so
 that I think that it is a valid address when the machine doing the ARP
 request does not know its IP address yet (though this sounds stupid).

Most likely, these are ARPs for multicast for SLPv2 location
of network resources, such as default gateway, etc., prior to
stateless autoconfiguration.

We discussed doing this on one of the IETF lists, as a side issue
to IPv6 stateless autoconfiguration, which ends up giving you a
routable address, in the context of permitting the reverse
address to be set to a machine name outside your domain for a
machine who got a routable stateless address from your domain.

You may also want to look at the ZEROCONF working group list
archives.


 Anyway, the fact is that -CURRENT can flood the console and
 /var/log/messages if there are many Macintosh sending these ARP requests
 in a LAN (as it is our case). I think that there is no reason to printf
 these messages, since 0.0.0.0 is a valid IP address meaning this host.

Yes.  This is basically a required use for a whohas for doing
stateless autoconfiguration, both in IPv6 (routable) and IPv4
(in the presence of a NAT).

The most recent DHCP and autoconfiguration RFC lets you ignore
DHCP entirely, and it lets you have a DHCP server refuse an
address to the host, with no recourse for the host to do the
autoconfiguration (e.g. a properly configured DHCP server can
make a conforming client not get an address at all).  I don't
think that, in that case, leaving the machine at 0.0.0.0 is a
valid thing to do: the interface should probably be forced down
instead.

That said, it's probably a good idea to never ARP for 0.0.0.0,
since a who has in that case is a really dumb idea, since,
as weas pointed out, it's intended to mean this host, in the
absence of an IP address (i.e. 0.0.0.0 is not an IP address,
it's a special value meaning not an IP address).

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Terry Lambert]

To expand a little...

 That said, it's probably a good idea to never ARP for 0.0.0.0,
 since a who has in that case is a really dumb idea, since,
 as weas pointed out, it's intended to mean this host, in the
 absence of an IP address (i.e. 0.0.0.0 is not an IP address,
 it's a special value meaning not an IP address).

It's probably also a good idea to make interfaces who have an
IP of 0.0.0.0 _not_ respond to ARP requests for that address,
and, just in case there are other idiots, we should also not
give proxy ARP responses for that address, etiher.

Ghah.  I hate special cases...

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Julian Elischer]

I've seen this when DHCP fails to allocate an address.


On Wed, 17 Oct 2001, Jose M. Alcaide wrote:

 After rebuilding the kernel two days ago (Oct 15), I am getting lots of
 messages like these:
 
 arp: 00:30:65:de:99:32 is using my IP address 0.0.0.0!
 arp: 00:0a:27:b0:a7:06 is using my IP address 0.0.0.0!
 arp: 00:30:65:d1:2f:cc is using my IP address 0.0.0.0!
 arp: 00:30:65:e9:57:5e is using my IP address 0.0.0.0!
 
 and so on.
 
 Neither ifconfig(8) nor arp(8) show anything unusual.
 
 Somebody reported this problem about two weeks ago, but there were no
 answers. Any ideas?
 
 Cheers,
 JMA
 -- 
 ** Jose M. Alcaide  //  [EMAIL PROTECTED]  //  [EMAIL PROTECTED] **
 ** Beware of Programmers who carry screwdrivers --  Leonard Brandwein **
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: arp: some ether addr is using my IP address 0.0.0.0! ??!?!?

[Jose M. Alcaide]

On Wed, Oct 17, 2001 at 12:11:45PM -0700, Julian Elischer wrote:
 I've seen this when DHCP fails to allocate an address.
 

But I am not using DHCP. Maybe there are other machines in the LAN (it is
a *big* LAN) trying to get their addresses using DHCP, and now -CURRENT
shows a message whenever detects one of those packets. I will try to
identify the senders (over 40!).

Anyway, these 0.0.0.0 ARP messages are new in -CURRENT, and none of our
machines running FreeBSD 4.x show them.

-- 
** Jose M. Alcaide  //  [EMAIL PROTECTED]  //  [EMAIL PROTECTED] **
** Beware of Programmers who carry screwdrivers --  Leonard Brandwein **

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ARP issues (Arcnet)

[Mike Nowlin]

 Once again I'm trying to port Arcnet driver from NetBSD/amiga to
 FreeBSD/i386 (like I did more than a year ago for 3.x). The problem is in

Wow!  I might be able to make the Arcnet board in my Tandy 6000 XENIX
machine actually talk to someone someday!?!?!?!?  COOL!  :)

(Actually, that machine still works, and I fire it up every so often to
play around with...  68000, 1.5MB RAM, 35MB HD, 5 serial ports.  Runs UUCP
with the best of 'em...)

mike




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: arp.

[Andy V. Oleynik]

andrea wrote:

 I have to add a gateway to my net for experimental reasons.
 Actually there are : a main-router that works as interface to the Internet,
 and some hosts on my sub net.

 Internet-MyRouterMySubNet

 NOw i need to configure one host of MYSubNet to act as a gatway for the
 secondary subnet.
 Both the 1SubNet and 2 SubNEt share the same ip-range.

  Internet-MyRouterMySubNet-My2SubNet

As I understood U have smth like this :
Internet-MyRouterMySubNet
   |2ndRouter-My2SubNet
Then U have to cut My2SubNet from ur  MySubNet and configure
routes to appropriate subnets on appropriate hosts. As long as ur 2ndsubnet
is part of ur mainsubnet  the hosts from  2ndsubnet will be seen from internet

 wise a versa. U may need to run DNS for reverse zone of ur  My2SubNet




 All the sub.net have to be seen from the Internet so I'll need to add a
 route to MainRouter in order to route the Secondary Subnet.
 The problem is that i cannot change configuration of the mainroute,so i


in fact this isnt  big problem as soon as U have properly configured
subnets:) . Correct me if I wrong.

 wonder if is possible to configure the new gateway to do a sort of proxy
 arp for my secondary Subnet.
 But arp-tables are system-wide so if i change arp entry to cacth request on
 PrimaryNet the 2subnet dont'works anymore.
 Is possible to catch arp request only on a single subnet,without broke any
 other subnet connected to the same host.?
 thank you!

 To Unsubscribe: send mail to majord...@freebsd.org
 with unsubscribe freebsd-questions in the body of the message

--
WBW  Andy V. Oleynik  (When U work in virtual office
   U have good chance to obtain virtual money Ж%-)





To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message

Re: arp.

[Crist J. Clark]

Andy V. Oleynik wrote,
[Charset koi8-r unsupported, filtering to ASCII...]
 andrea wrote:
 
  I have to add a gateway to my net for experimental reasons.
  Actually there are : a main-router that works as interface to the Internet,
  and some hosts on my sub net.
 
  Internet-MyRouterMySubNet
 
  NOw i need to configure one host of MYSubNet to act as a gatway for the
  secondary subnet.
  Both the 1SubNet and 2 SubNEt share the same ip-range.
 
   Internet-MyRouterMySubNet-My2SubNet
 
 As I understood U have smth like this :
 Internet-MyRouterMySubNet
|2ndRouter-My2SubNet
 Then U have to cut My2SubNet from ur  MySubNet and configure
 routes to appropriate subnets on appropriate hosts. As long as ur 2ndsubnet
 is part of ur mainsubnet  the hosts from  2ndsubnet will be seen from internet
 
  wise a versa. U may need to run DNS for reverse zone of ur  My2SubNet

DNS has nothing really to do with this problem. I believe the original
poster is describing the following (this may be what the second poster
meant to write, but proportional fonts, tab damage, or his character
set wiped it out),

Internet--PrimaryRouter--SubNet1
|
 SecondaryRouter-SubNet2

 
 
  All the sub.net have to be seen from the Internet so I'll need to add a
  route to MainRouter in order to route the Secondary Subnet.
  The problem is that i cannot change configuration of the mainroute,so i
 
 
 in fact this isnt  big problem as soon as U have properly configured
 subnets:) . Correct me if I wrong.

This is a problem. You are wrong. But back to the original poster, why
can you not change the configuration on the Primary Router[0]? If this is
your network, and you want to be able to do things like this, you need
to be able to change the Primary Router configuration.

To the second poster, when the Primary Router receives a packet
destined for a machine on SubNet1 or SubNet2, since the Router
believes all of those machines are still on its LAN, it will try to
use the MAC address (layer 2) to send the packet directly to the
machine. However, now this machine has been moved behind the Secondary
Router. The Secondary Router is not listening for other machines'
packets at layer 2 (in a typical router setup), so it never gets the
packet and never tries to forward it. It also would not respond to ARP
calls by the Primary Router when it is looking for a machine on
SubNet2.

  wonder if is possible to configure the new gateway to do a sort of proxy
  arp for my secondary Subnet.
  But arp-tables are system-wide so if i change arp entry to cacth request on
  PrimaryNet the 2subnet dont'works anymore.
  Is possible to catch arp request only on a single subnet,without broke any
  other subnet connected to the same host.?

It is possible. But I am unaware of a tool to do this[1] (which does not
mean there is not one). Might you be better off building a 'new' net
behind your Secondary Router? Say using NAT and a 10.0.0 subnet?

[0] All you need to do on the router is add a route to Secondary
Router for IPs on SubNet2. All you need is the address for the
Secondary Router and a subnet mask.

[1] The Secondary Router would not actually be doing routing in this
case. It's acting more like a switch. You did not really tell us why
you are doing this. Would getting a switch be a better option for you?
-- 
Crist J. Clark   cjcl...@home.com


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message

Re: arp.

[Andy V. Oleynik]

Crist J. Clark wrote:

 Andy V. Oleynik wrote,
 [Charset koi8-r unsupported, filtering to ASCII...]
  andrea wrote:
 
   I have to add a gateway to my net for experimental reasons.
   Actually there are : a main-router that works as interface to the 
   Internet,
   and some hosts on my sub net.
  
   Internet-MyRouterMySubNet
  
   NOw i need to configure one host of MYSubNet to act as a gatway for the
   secondary subnet.
   Both the 1SubNet and 2 SubNEt share the same ip-range.
  
Internet-MyRouterMySubNet-My2SubNet
 
  As I understood U have smth like this :
  Internet-MyRouterMySubNet
 |2ndRouter-My2SubNet


I mean 2ndrouter is on  MySubNet, sorrey for unclearity:)

  Then U have to cut My2SubNet from ur  MySubNet and configure
  routes to appropriate subnets on appropriate hosts. As long as ur 2ndsubnet
  is part of ur mainsubnet  the hosts from  2ndsubnet will be seen from 
  internet
 
   wise a versa. U may need to run DNS for reverse zone of ur  My2SubNet

 DNS has nothing really to do with this problem. I believe the original


I said U may not U must. At least I  run DNS for revzones of my subnets.

 poster is describing the following (this may be what the second poster
 meant to write, but proportional fonts, tab damage, or his character
 set wiped it out),

 Internet--PrimaryRouter--SubNet1
 |
  SecondaryRouter-SubNet2

  
  
   All the sub.net have to be seen from the Internet so I'll need to add a
   route to MainRouter in order to route the Secondary Subnet.
   The problem is that i cannot change configuration of the mainroute,so i
  
 
  in fact this isnt  big problem as soon as U have properly configured
  subnets:) . Correct me if I wrong.

 This is a problem. You are wrong. But back to the original poster, why

Sorrey Crist, but there is no need to connect 2nd router to 1st. If U have to
have 2nd subnet just insert 2nd NIC into 1st router and as I sad above
configure ur subnets (with appropriate routes on router off cause 
defaulterouter on hosts on subnets :).



 can you not change the configuration on the Primary Router[0]? If this is
 your network, and you want to be able to do things like this, you need
 to be able to change the Primary Router configuration.

 To the second poster, when the Primary Router receives a packet
 destined for a machine on SubNet1 or SubNet2, since the Router
 believes all of those machines are still on its LAN, it will try to
 use the MAC address (layer 2) to send the packet directly to the


Is this true if 1strouter knows that a route to 2ndsubnet is throught 2ndrouter
which is
on same subnet as 1strouter?

 machine. However, now this machine has been moved behind the Secondary
 Router. The Secondary Router is not listening for other machines'


why not if it's configured as gateway to 2ndsnet?

 packets at layer 2 (in a typical router setup), so it never gets the


 packet and never tries to forward it. It also would not respond to ARP


 calls by the Primary Router when it is looking for a machine on
 SubNet2.



   wonder if is possible to configure the new gateway to do a sort of proxy
   arp for my secondary Subnet.
   But arp-tables are system-wide so if i change arp entry to cacth request 
   on
   PrimaryNet the 2subnet dont'works anymore.
   Is possible to catch arp request only on a single subnet,without broke any
   other subnet connected to the same host.?

 It is possible. But I am unaware of a tool to do this[1] (which does not
 mean there is not one). Might you be better off building a 'new' net
 behind your Secondary Router? Say using NAT and a 10.0.0 subnet?

 [0] All you need to do on the router is add a route to Secondary
 Router for IPs on SubNet2. All you need is the address for the
 Secondary Router and a subnet mask.

 [1] The Secondary Router would not actually be doing routing in this
 case. It's acting more like a switch. You did not really tell us why
 you are doing this. Would getting a switch be a better option for you?
 --
 Crist J. Clark   cjcl...@home.com

--
WBW  Andy V. Oleynik  (When U work in virtual office
   U have good chance to obtain virtual money Ж%-)





To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message

Re: arp.

[Curt Sampson]

On Mon, 5 Apr 1999, andrea wrote:

 [etc.]

If I read you correctly, what you want to do is something like this:

 internet
|
main router
192.168.1.1/24  
|
|-- other hosts on 192.168.1.0/25 subnet
|
192.168.1.2/25
sub-router 
192.168.1.129/25
|
|-- other hosts on 192.168.1.128/25 subnet
|

In other words, you have split your network into two subnets, but
because you have no control over the `main router' above, you cannot
inform it of the new subnet mask, so it believes that all the hosts
on the 192.168.1.128 subnet are local.

This is not hard to solve; you just turn on routing in the sub-router
box and enable proxy-arp. This will cause the subrouter box, when
it receives an arp request for the 128/25 subnet on the 0/25
interface, to reply to that ARP with its own address. The host that
requested the arp then sends all packets to the sub-router, and
normal routing gets it to its destination.

The question is, does NetBSD do this properly? I think it does,
but I'm lacking the AUI/10base-T transceiver I need to test this
out right now. However, in theory, if you have a host 192.168.1.130
that needs to talk to the main router, you type the following
command on the sub-router:

arp -s 192.168.1.130 sub-router's MAC address pub

(The sub-router's MAC address can be gotten from an `ifconfig -a'
or `netstat -i'; it will be a sequence of six hex numbers separated
by colons, such as `8:0:20:1f:77:e0'.)

The unfortunate part about this is that you have to add a separate
arp entry for each host you want to proxy-arp for. On a cisco
router, the proxy-arp option allows you to arp for anything it
knows how to route to. This feature wouldn't be too hard to add to
NetBSD, actually; you'd just have to modify arplookup to generate
and add a new (pub, temp) arp entry for any IP address it can find
a route for in its routing tables. (This would be controlled by a
sysctl that would default to off, of course.) I may look at doing
this after the 1.4 release. Or someone else could do it and save
me the trouble. :-)

cjs
-- 
Curt Sampson  c...@cynic.net   604 801 5335   De gustibus, aut bene aut nihil.
The most widely ported operating system in the world: http://www.netbsd.org



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message

Re: arp.

[Robin Melville]

At 12:22 pm +0100 5/4/99, andrea wrote:
I have to add a gateway to my net for experimental reasons.
Actually there are : a main-router that works as interface to the Internet,
and some hosts on my sub net.

Internet-MyRouterMySubNet

NOw i need to configure one host of MYSubNet to act as a gatway for the
secondary subnet.
Both the 1SubNet and 2 SubNEt share the same ip-range.

 Internet-MyRouterMySubNet-My2SubNet

All the sub.net have to be seen from the Internet so I'll need to add a
route to MainRouter in order to route the Secondary Subnet.
The problem is that i cannot change configuration of the mainroute,so i
wonder if is possible to configure the new gateway to do a sort of proxy
arp for my secondary Subnet.
But arp-tables are system-wide so if i change arp entry to cacth request on
PrimaryNet the 2subnet dont'works anymore.
Is possible to catch arp request only on a single subnet,without broke any
other subnet connected to the same host.?
thank you!

Assuming that these are IP routers and not ethernet switches, the arp
tables aren't particularly relevent. If the main router is running 'routed'
or some other RIP routing daemon, all you need to do is run a similar
daemon and your new subnet route will be propagated. Alternatively, or
essentially if you are using unregistered IP, you could use 'natd' on
'MyRouter' to masquerade the internal addresses onto the external interface.

The handbook pages on natd make it very easy to set up.

Good luck

Robin.

--
Robin Melville, Addiction Information Services
Nottingham Alcohol  Drug Team
Tel:  +44 (0)115 952 9478   Fax:  +44 (0)115 952 9421
work: rob...@nadt.org.ukhome: rob...@innotts.co.uk
Pages: http://www.innotts.co.uk/~robmel(home page)
   http://www.innotts.co.uk/nadt   (substance misuse pages)
--




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message