public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	"DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
Subject: Re: [pve-devel] [PATCH pve-network 0/7] add dhcp support for all zones
Date: Thu, 22 Feb 2024 11:13:54 +0100	[thread overview]
Message-ID: <ecf0948f-06d2-4299-adb2-019550c2f38b@proxmox.com> (raw)
In-Reply-To: <248b6df66af9dc843b7998898a43bb9ddb007f58.camel@groupe-cyllene.com>



On 12/22/23 22:27, DERUMIER, Alexandre wrote:
> Hi,
> I'll be on holiday next week (I'll be back the 2 january).
> 
> 
> I'll look at QinQ when I'll be back.

I've had another look at this patch series and I think I found the
reason for the issue(s) I encountered during my testing.

One issue is related to the new IP forwarding settings. It seems like
they are not applying. I've looked at the ifquery output after creating
a QinQ / VLAN zone with DHCP enabled:

  {
    "name": "qinq5",
    "auto": true,
    "config": {
      "bridge-ports": "z_qinq5.456",
      "bridge-stp": "no",
      "bridge-fd": "0",
      "ip-forward": "on",
      "address": "172.16.5.1/32"
    },
    "config_status": {
      "bridge-ports": "pass",
      "bridge-stp": "pass",
      "bridge-fd": "pass",
      "ip-forward": "fail",
      "address": "pass"
    },
    "status": "fail"
  },
  {
    "name": "vlan4",
    "auto": true,
    "config": {
      "bridge-ports": "ln_vlan4",
      "bridge-stp": "no",
      "bridge-fd": "0",
      "ip-forward": "on",
      "address": "172.16.4.1/32"
    },
    "config_status": {
      "bridge-ports": "pass",
      "bridge-stp": "pass",
      "bridge-fd": "pass",
      "ip-forward": "fail",
      "address": "pass"
    },
    "status": "fail"
  },

It seems like the ip-forward settings do not get applied and therefore
the command 'fails'. The bridges are up and working but IP forwarding is
enabled:

root@hoan-02:~# cat /proc/sys/net/ipv4/conf/vlan4/forwarding
1

root@hoan-02:~# cat /proc/sys/net/ipv4/conf/qinq5/forwarding
1


The other issue was using QinQ zone with a bridge that has no bridge
port configured and is not vlan-aware. In that case status is checking
for the existence of the sv_<id> interface but it doesn't exist since
there isn't a bridge port.
This is also occuring without this patch, so no show stopper here imo.

> It just miss the ip for dhcpserver different than gateway for ipv6
> handling for vlan/qinq/vxlan, but it should be easy to implement.
> 
> Also, for ipv6 in vrf, it need a patch for dnsmasq, so I think this
> will need to proxmox dnsmasq package version.




  reply	other threads:[~2024-02-22 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  8:32 Alexandre Derumier
2023-12-19  8:32 ` [pve-devel] [PATCH pve-network 1/7] dhcp: add vrf support Alexandre Derumier
2023-12-19  8:32 ` [pve-devel] [PATCH pve-network 2/7] dhcp: enable-ra on layer3 zones only Alexandre Derumier
2023-12-19  8:32 ` [pve-devel] [PATCH pve-network 3/7] dnsmasq service: run service in vrf Alexandre Derumier
2023-12-19  8:32 ` [pve-devel] [PATCH pve-network 4/7] zones: evpn: add dhcp support Alexandre Derumier
2023-12-19  8:32 ` [pve-devel] [PATCH pve-network 5/7] zones: vlan: " Alexandre Derumier
2023-12-19  8:32 ` [pve-devel] [PATCH pve-network 6/7] zones: qinq: " Alexandre Derumier
2023-12-19  8:32 ` [pve-devel] [PATCH pve-network 7/7] zones: vxlan: " Alexandre Derumier
2023-12-22 14:01 ` [pve-devel] [PATCH pve-network 0/7] add dhcp support for all zones Stefan Hanreich
2023-12-22 21:27   ` DERUMIER, Alexandre
2024-02-22 10:13     ` Stefan Hanreich [this message]
     [not found]       ` <6c7a0c383c6aee77689433815775e27f5259da91.camel@groupe-cyllene.com>
2024-02-22 10:52         ` Stefan Hanreich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ecf0948f-06d2-4299-adb2-019550c2f38b@proxmox.com \
    --to=s.hanreich@proxmox.com \
    --cc=alexandre.derumier@groupe-cyllene.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal