From owner-freebsd-net@freebsd.org Sun Jun 23 06:35:32 2019 Return-Path: Delivered-To: freebsd-net@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 744FE15C7152 for ; Sun, 23 Jun 2019 06:35:32 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta02.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE3B275AEA for ; Sun, 23 Jun 2019 06:35:30 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([96.28.161.151]) by cmsmtp with ESMTP id ew5xhUDdyiYm2ew5zhBvm2; Sun, 23 Jun 2019 06:35:24 +0000 Date: Sun, 23 Jun 2019 06:35:03 +0000 From: "Thomas Mueller" To: freebsd-net@freebsd.org Subject: Re: Can Ethernet and wi-fi be used concurrently? References: <5d0ed525.1c69fb81.d673e.e3dfSMTPIN_ADDED_MISSING@mx.google.com> X-CMAE-Envelope: MS4wfDPnDRZbtbDjBd65D6Z5SKRBo4zIN4AuUOqEzYdaj0HJcau51ucx1vkEgDScuToaVZ5topuKT4eBHvo0xLc9QOery+VO6PfXclQF/8I4FWZXsyFnz0wJ teZ63EP43YtDMWU6tWji1gPHdqsxn+MnXYIyNZ6cgtAxOK9I+oFx583j X-Rspamd-Queue-Id: EE3B275AEA X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of mueller6722@twc.com designates 107.14.73.226 as permitted sender) smtp.mailfrom=mueller6722@twc.com X-Spamd-Result: default: False [-0.82 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.94)[-0.936,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.14.73.0/24]; FREEMAIL_FROM(0.00)[twc.com]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.90)[-0.901,0]; MISSING_MID(2.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MX_GOOD(-0.01)[cached: dnvrco-cmedge02.email.rr.com]; NEURAL_HAM_SHORT(-0.90)[-0.897,0]; RCVD_IN_DNSWL_NONE(0.00)[226.73.14.107.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.27)[ipnet: 107.14.73.0/24(-3.51), asn: 7843(-2.81), country: US(-0.06)]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[twc.com]; FROM_EQ_ENVFROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[151.161.28.96.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7843, ipnet:107.14.73.0/24, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[twc.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2019 06:35:32 -0000 from Mel Pilgrim and my last post: > On 2019-06-22 18:24, Thomas Mueller wrote: > > I would like to know if it is possible to have both Ethernet and > > wi-fi running concurrently? > > > Purpose would be, if the cable service is down, meaning no internet > > access but intranet OK, to continue to have intranet access while > > using wi-fi with a mobile phone as hotspot to aceess the internet. > If you can keep the mobile hotspot disconnected until you need it, configure > the wired interface with a higher metric than the wireless interface and > routing will do the rest for you. Could I start (ifconfig) the wired ethernet with metric 0 and then connect the wi-fi with metric > 0? Then possibly the system could lose time by trying the wired interface first on internet access attempts even when the cable service is down? > On 2019-06-22 19:05, John Lyon wrote: > > You should be able to use the lagg driver to combine the two > > interfaces in failover mode to achieve your goal. > lagg doesn't apply here because Thomas's issue is routing failover. The > master interface would remain up for intranet access. Tom