On Wed, Sep 28, 2016 at 12:09:35PM +0200, Paul de Weerd wrote:
> I ran into this issue while manually configuring a set of aliases on

I can reproduce it on -current:

while ifconfig vio0 inet delete; do :; done
while ifconfig vio1 inet delete; do :; done
netstat -rn -f inet

Destination        Gateway            Flags   Refs      Use   Mtu  Prio Iface
224/4              127.0.0.1          URS        0        0 32768     8 lo0  
127/8              127.0.0.1          UGRS       0        0 32768     8 lo0  
127.0.0.1          127.0.0.1          UHl        1        6 32768     1 lo0  

ifconfig vio0 inet 10.188.70.1/24
ping -c 1 -w 1 10.188.70.2
ifconfig vio0 inet 10.188.70.2/24 alias
ifconfig vio0 inet

vio0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 70:5f:ca:21:8d:70
        index 1 priority 0 llprio 3
        groups: egress
        media: Ethernet autoselect
        status: active
        inet 10.188.70.1 netmask 0xffffff00 broadcast 10.188.70.255
        inet 10.188.70.2 netmask 0xffffff00 broadcast 10.188.70.255

netstat -rn -f inet

Destination        Gateway            Flags   Refs      Use   Mtu  Prio Iface
224/4              127.0.0.1          URS        0        0 32768     8 lo0  
10.188.70/24       10.188.70.1        UCP        1        0     -     4 vio0 
10.188.70/24       10.188.70.2        UCP        0        0     -     4 vio0 
10.188.70.1        70:5f:ca:21:8d:70  UHLl       0        0     -     1 vio0 
10.188.70.2        link#1             UHLc       0        2     -     4 vio0 
10.188.70.255      10.188.70.1        UHPb       0        0     -     1 vio0 
10.188.70.255      10.188.70.2        UHPb       0        0     -     1 vio0 
127/8              127.0.0.1          UGRS       0        0 32768     8 lo0  
127.0.0.1          127.0.0.1          UHl        1        6 32768     1 lo0  

route delete 10.188.70.2
netstat -rn -f inet

Destination        Gateway            Flags   Refs      Use   Mtu  Prio Iface
224/4              127.0.0.1          URS        0        0 32768     8 lo0  
10.188.70/24       10.188.70.1        UCP        0        0     -     4 vio0 
10.188.70/24       10.188.70.2        UCP        0        0     -     4 vio0 
10.188.70.1        70:5f:ca:21:8d:70  UHLl       0        0     -     1 vio0 
10.188.70.255      10.188.70.1        UHPb       0        0     -     1 vio0 
10.188.70.255      10.188.70.2        UHPb       0        0     -     1 vio0 
127/8              127.0.0.1          UGRS       0        0 32768     8 lo0  
127.0.0.1          127.0.0.1          UHl        1        6 32768     1 lo0  

ping -c 1 -w 1 10.188.70.2

panic: kernel diagnostic assertion "ifa == rt->rt_ifa" failed: file 
"../../../../netinet/if_ether.c", line 206
Stopped at      Debugger+0x9:   leave
   TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
*51739  51739      0    0x100033          0    0  ping
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
arp_rtrequest() at arp_rtrequest+0x34d
rtrequest() at rtrequest+0x595
rt_match() at rt_match+0xec
ip_output() at ip_output+0x3ed
rip_output() at rip_output+0x1a4
rip_usrreq() at rip_usrreq+0x1a6
sosend() at sosend+0x2d8
sendit() at sendit+0x24b
sys_sendto() at sys_sendto+0x62
syscall() at syscall+0x197
--- syscall (number 133) ---
end of kernel
end trace frame: 0x40, count: 2
0x1c3835f222ea:
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb> 

bluhm

Reply via email to