No loadbalancer, no reverse proxy (except for MaaS own nginx). I use external dhcp scenario.
I find this error consistently appearing accross my 2 setups. One in AWS vpc, one in my private virtual lab. Let me know if you need addtional info or traces/logs.
No loadbalancer, no reverse proxy (except for MaaS own nginx). I use external dhcp scenario.
I find this error consistently appearing accross my 2 setups. One in AWS vpc, one in my private virtual lab. Let me know if you need addtional info or traces/logs.
Net config from the lab env:
Network netplans (ubuntu server 22.04) config:
network:
ethernets:
eth0:
addresses:
- 192.168.0.234/24
nameservers:
addresses: [192.168.0.1]
search: [lan]
routes:
- to: default
via: 192.168.0.1
version: 2
root@maas: /var/log/ maas# ip a UP,LOWER_ UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc mq state UP group default qlen 1000 7bdb::64f/ 128 scope global dynamic noprefixroute 7bdb:0: 215:5dff: fe38:129/ 64 scope global mngtmpaddr noprefixroute 5dff:fe38: 129/64 scope link /var/log/ maas#
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,
link/ether 00:15:5d:38:01:29 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.234/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fd77:eeee:
valid_lft 42713sec preferred_lft 42713sec
inet6 fd77:eeee:
valid_lft forever preferred_lft forever
inet6 fe80::215:
valid_lft forever preferred_lft forever
root@maas: