On Fri, Mar 19, 2021 at 12:04:51PM +0100, Thomas Haller via networkmanager-list
wrote:
> On Fri, 2021-03-19 at 12:03 +0100, Thomas Haller via networkmanager-
> list wrote:
> > On Fri, 2021-03-19 at 06:52 -0400, Adam Sherlock via networkmanager-
> > list wrote:
> >
>
> Hi,
>
> I forgot to say: G
On Wed, Feb 12, 2020 at 10:29:36PM +0100, r...@shrl.nl wrote:
> Is there a way to configure two wired connections. One for my home
> network (assigned-mac-address=permanent) and one for all other wired
> connections (assigned-mac-address=random) in a manner at which
> networkmanager autodetects if
On Thu, Feb 13, 2020 at 08:25:47PM -0500, Anthony Fletcher wrote:
> Yes - you make a good point about the rules for the DUID. So I'm back
> to using different NM profiles or a script that sets a different
> static IPv6 address depending on the VLAN RA,
In order to get different IPv6 address from S
Nmstate 0.0.8 released.
### New Features
- Support reapply configuration without link down when possible.
- Relicensed to LGPL 2.1+.
- Allow editing existing interface without specifying the type property
in the desired state.
### Bug Fixes
- Allow adding a port to the Linux bridge by spec
Hi Guys,
PR https://github.com/nmstate/nmstate/pull/354 has express a initial layout.
I want to expand that to discuss of how we reorganize our code:
* `InterfaecBasic` contains IPv4, IPv6 and other stuff shared between
interfaces.
* Specific interface type will have their own class like: E
On Sat, May 18, 2019 at 05:24:31PM +0200, Thomas Haller wrote:
> On Sat, 2019-05-18 at 20:32 +0800, Gris Ge via networkmanager-list
> wrote:
> > **My first patch to NM, need some help for test cases**
> >
> > Use NM_SETTING_IP6_CONFIG_METHOD_DISABLED/"disabled"
**My first patch to NM, need some help for test cases**
Use NM_SETTING_IP6_CONFIG_METHOD_DISABLED/"disabled" for disabling
IPv6 per profile.
Signed-off-by: Gris Ge
---
clients/common/nm-meta-setting-desc.c | 3 +-
clients/common/nm-vpn-helpers.c | 2 +-
clients/common/se
Hi Guys,
For the IP route editing in nmstate, the parietal editing is
problematic:
User case A:
Current routes: 1.1.1.0/24 via 2.2.2.2 dev eth1
Desired routes: changed next hope to 3.3.3.3
User case B:
Current routes: 1.1.1.0/24 via 2.2.2.2 dev eth1
Desire
Hi Guys,
I believe we can cast vote on these options based on feedback:
Option A:
https://gist.github.com/cathay4t/70b69bda1de0f60ec533bf98fdc04f95
Notes:
* The basic layout: info['routes'][0] =
* Each route entry will have 'family' property.
* The route protocol
On Mon, Mar 04, 2019 at 05:58:01PM +0100, Thomas Haller wrote:
> On Mon, 2019-03-04 at 22:11 +0800, Gris Ge wrote:
> > * Top tree is 'routes', and subtree is 'ipv4' and 'ipv6'.
> >Even the IPv4 and IPv6 route entry are mostly identical, but we
> > need
> >schema to differentiate the 'desti
Based on feedbacks, this is V2 scheme for review:
```
{
"routes": {
"ipv4": [ # Sorted with 'table-id' then 'destination'
{
"status": "up",
# up or absent(to be removed)
# If not defin
On Thu, Feb 28, 2019 at 10:40:48PM +0200, Edward Haas wrote:
>
> What is the root level key? `routing`?
The root level is 'ipv4-routes' and 'ipv6-routes'.
Try to save a layer for user to type comparing to ['routing']['routes']
> ipv4 and ipv6 look identical to me here.
> It makes sense then to ha
Hi Guys,
Could you review below schema for routing in nmstate before we start
add routing support in nmstate?
```
{
"ipv4-routes": [# Sorted with 'table-id' then 'destination'
{
"table-name": "main", # Empty if no name attached
"table-
13 matches
Mail list logo
