[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #18804: ifconfig tun interface support is incomplete
From:       Haiku <trac () haiku-os ! org>
Date:       2024-04-23 22:09:45
Message-ID: 060.995d5f098125de905f0e1a2647ca17e0 () haiku-os ! org
[Download RAW message or body]

--===============3602560995441121514==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#18804: ifconfig tun interface support is incomplete
----------------------------------------+----------------------------
  Reporter:  dovsienko                  |      Owner:  nobody
      Type:  enhancement                |     Status:  new
  Priority:  normal                     |  Milestone:  Unscheduled
 Component:  Network & Internet/Tunnel  |    Version:  R1/Development
Resolution:                             |   Keywords:
Blocked By:                             |   Blocking:
  Platform:  All                        |
----------------------------------------+----------------------------
Comment (by dovsienko):

 The "unknown hardware type" point is cosmetic. The "point-to-point inner
 address does not appear in ifconfig output" is a defect: what ifconfig
 allows to configure it should also display so the user can verify the
 result. The "missing host route" point is a defect.

 Ideally the final implementation should work with OpenVPN (even a patched
 one) without manual tunnel interface configuration, such that tunnel
 interfaces have correct point-to-point addresses and the host routes are
 automatically present. Which in turn would simplify network routes that
 use the point-to-point address as the gateway.
--=20
Ticket URL: <https://dev.haiku-os.org/ticket/18804#comment:4>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.

--===============3602560995441121514==--

[prev in list] [next in list] [prev in thread] [next in thread]