From owner-freebsd-hackers@freebsd.org Mon Jan 14 17:15:12 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB4A714A6BC3 for ; Mon, 14 Jan 2019 17:15:11 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E28AC6C5E0 for ; Mon, 14 Jan 2019 17:15:10 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-ed1-x52b.google.com with SMTP id x30so265185edx.2 for ; Mon, 14 Jan 2019 09:15:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Cb8UmkqzV4CY5fFJUVpgl6ZgnHX9JGK6g3TnGqn3aSo=; b=nUYKXC46JFJ0fqCz3WbqaIgKTPfQfCv63KI6T2f6nxLrH2ohYHnJ996sTmgFIO8BDZ hMI46HMKuONQe65zT9P0cxmyiMgNueEWiSzZrfZaf+91Egxn+ucumZZ83vASzTGZbJOg hXVcccgXIQzNHGohUb5LP78z1IhdDNLns40dR+q0l0SkJRJsJI+tl8cfKjG68TgaJGjH /dxsVubkgyya9EYhObrGiQX9LGICgLrySqFYMMz+8WzI5ow+2CQKBCWPcGMAwdClmSp6 JO0Qs0vbZkSm8Ogb4nbbt6T13t60KmAqjSlDuNohMnwUrBQh8zGsZ2l47YabywGRaHR6 RWCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Cb8UmkqzV4CY5fFJUVpgl6ZgnHX9JGK6g3TnGqn3aSo=; b=IbXMQ5Uydjjk2DoUOXS/i1FnDhRlzDslnzX5h1tyfCitHnwUhlTt9Ory78QJy7gBfW zhJoN8SAeupCsQrGosGYMMKBIRrFSNo5B1iLQZ4ELXnVowT4JmVjaNkdLkJ9wI9SYZzq pKFLHgaOViAXzhAYBJvLb62N201J2PdbXjOuM70jV+br8Vw9X5PfSOZPlpuX9CLoeZEt aFsob4JdXvPGNIJeri8qBZvdJ7xiWEY3lOLqP45zb6IH/5+0BQwlUPc9pZcyqu+gJkDr 5ml3lhrvp74bA6jsELxD8pBpuxHlWHbv4M4FJP74ttpc21kG4iFqpwhSZQKJfZFNmmj6 5OkA== X-Gm-Message-State: AJcUuke18bSkB8z/YqblluzXGseZ6JRVgynqG+Fmb7VT3LsNFQnYpUgj i2JWYGVc/Q9ypd3oJ6v4aGuMjjoIqz5b1uMsyF1nEU+/ X-Google-Smtp-Source: ALg8bN5TtSgDSzRTt/7hAJRU3TW3RN9CcqObDVWGe15RmQHMws71gDeREln9nEd3hI1jQdfkILGUWUkLMNFlqyNHamA= X-Received: by 2002:a50:fb03:: with SMTP id d3mr114695edq.183.1547486109040; Mon, 14 Jan 2019 09:15:09 -0800 (PST) MIME-Version: 1.0 References: <201901141659.x0EGxkDl035975@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201901141659.x0EGxkDl035975@pdx.rh.CN85.dnsmgr.net> From: Mark Saad Date: Mon, 14 Jan 2019 12:14:57 -0500 Message-ID: Subject: Re: Removing an alias can remove routes ? To: "Rodney W. Grimes" Cc: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: E28AC6C5E0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=longcount-org.20150623.gappssmtp.com header.s=20150623 header.b=nUYKXC46 X-Spamd-Result: default: False [-4.57 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[longcount-org.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; IP_SCORE(-2.55)[ip: (-8.87), ipnet: 2a00:1450::/32(-2.02), asn: 15169(-1.76), country: US(-0.08)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[longcount.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[longcount-org.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[b.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt1.aspmx.l.google.com]; R_SPF_NA(0.00)[]; NEURAL_HAM_SHORT(-0.72)[-0.716,0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2019 17:15:12 -0000 On Mon, Jan 14, 2019 at 11:59 AM Rodney W. Grimes wrote: > > > All > > I ran into a peculiar over the weekend on two FreeBSD 10-STABLE > > servers that has me at a loss. Both servers have the same setup lacp > > lagg wtih vlans using the lagg as a parent dev. > > On the vlans I have some alias along with the primary ip. When a > > alias was added or deleted routes that sourced out of the primary ip > > on that vlan were dropped from the routing table. > > > > > > So for example. I have lagg0.vlan1044 . (both servers are similarly > > configured as routers / firewalls ) > > > > [root@pineapple01 ~]# ifconfig lagg0.vlan1044 > > lagg0.vlan1044: flags=8843 > > metric 0 mtu 1500 > > options=300 > > ether 00:0f:53:20:9b:d0 > > inet6 fe80::20f:53ff:fe20:9bd0%lagg0.vlan1044 prefixlen 64 > > scopeid 0x80 > > inet 10.24.213.84 netmask 0xffffffe0 broadcast 10.24.213.95 > > inet 10.24.212.129 netmask 0xffffffff broadcast 10.24.212.129 > > inet 10.24.213.163 netmask 0xfffffff0 broadcast 10.24.213.175 > > inet 10.24.213.76 netmask 0xffffffe0 broadcast 10.24.213.95 > > inet 10.24.213.94 netmask 0xffffffe0 broadcast 10.24.213.95 > > inet 10.24.213.89 netmask 0xffffffe0 broadcast 10.24.213.95 > > inet 10.24.213.75 netmask 0xffffffe0 broadcast 10.24.213.95 > > nd6 options=21 > > media: Ethernet autoselect > > status: active > > vlan: 1044 parent interface: lagg0 > > > > [root@pineapple01 ~]# netstat -nr4Wl > > ... > > 192.168.144.32/27 10.24.213.65 UGS 0 1500 lagg0.vlan1044 > > 192.168.144.96/27 10.24.213.65 UGS 0 1500 lagg0.vlan1044 > > 192.168.23.0/24 10.24.213.65 UGS 0 1500 lagg0.vlan1044 > > 192.168.120.0/21 10.24.213.65 UGS 0 1500 lagg0.vlan1044 > > > > > > So I wanted to remove the alias ended in 163 and fix its netmask back to /32 > > > > I ran this > > > > ifconfig lagg0.vlan1044 inet 10.24.213.163/24 -alias && ifconfig > ^ delete? I use -alias which is an alias of -delete > > > lagg0.vlan1044 inet 10.24.213.163/32 -alias > > > > and shortly there after all of the routes that went out lagg0.vlan1044 > > were gone . I quickly undid my change and put the routes back but I am > > not sure what caused this ? Anyone have any ideas I have done this in > > the past with out issue and I am unsure whats changed other then the > > box have a long up time of 463 days . > > I believe what happened here is that 10.24.213.163/24 when reduced > to a network address is 10.24.213.0/24, which probably got sent to > the route removal code, which since the route to that covers the > gateway at 10.24.213.65 that gateway was no longer accessable > so all routes via it got removed. > ok I see what you are saying and it makes sense to me; do you know why the routing code does not see the primary ip ( the non-alias one) is still live on the interface before deciding to drop the routes associated with it ? > -- > Rod Grimes rgrimes@freebsd.org -- mark saad | nonesuch@longcount.org