Yes, once I configure default route via NH on that interface, it becomes member of egress group. But, it doesn't cease its membership when the route is removed.
obsd-02# ifconfig vio0 vio0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 12:22:00:00:00:00 index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect status: active inet 100.64.5.22 netmask 0xffffff00 broadcast 100.64.5.255 obsd-02# obsd-02# obsd-02# ifconfig vio1 vio1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 12:22:01:00:00:00 index 2 priority 0 llprio 3 media: Ethernet autoselect status: active inet 172.16.0.2 netmask 0xffffff00 broadcast 172.16.0.255 obsd-02# obsd-02# obsd-02# netstat -rn -f inet | grep vio0 default 100.64.5.254 UGS 0 2 - 8 vio0 100.64.5/24 100.64.5.22 UCn 1 0 - 4 vio0 100.64.5.22 12:22:00:00:00:00 UHLl 0 29 - 1 vio0 100.64.5.254 06:ea:b0:89:e7:eb UHLch 2 20 - 3 vio0 100.64.5.255 100.64.5.22 UHb 0 0 - 1 vio0 obsd-02# obsd-02# obsd-02# netstat -rn -f inet | grep vio1 172.16.0/24 172.16.0.2 UCn 1 0 - 4 vio1 172.16.0.2 12:22:01:00:00:00 UHLl 0 0 - 1 vio1 172.16.0.3 link#2 UHLch 1 2 - 3 vio1 172.16.0.255 172.16.0.2 UHb 0 0 - 1 vio1 172.16.1/24 172.16.0.3 UGS 0 0 - 8 vio1 obsd-02# obsd-02# obsd-02# route add -priority 10 0.0.0.0/0 172.16.0.3 add net 0.0.0.0/0: gateway 172.16.0.3 obsd-02# obsd-02# obsd-02# netstat -rn -f inet | grep vio1 default 172.16.0.3 UGS 0 0 - 10 vio1 172.16.0/24 172.16.0.2 UCn 1 0 - 4 vio1 172.16.0.2 12:22:01:00:00:00 UHLl 0 0 - 1 vio1 172.16.0.3 link#2 UHLch 2 4 - 3 vio1 172.16.0.255 172.16.0.2 UHb 0 0 - 1 vio1 172.16.1/24 172.16.0.3 UGS 0 0 - 8 vio1 obsd-02# obsd-02# obsd-02# ifconfig vio1 vio1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 12:22:01:00:00:00 index 2 priority 0 llprio 3 groups: egress media: Ethernet autoselect status: active inet 172.16.0.2 netmask 0xffffff00 broadcast 172.16.0.255 obsd-02# obsd-02# obsd-02# route delete -priority 10 0.0.0.0/0 delete net 0.0.0.0/0 obsd-02# obsd-02# obsd-02# netstat -rn -f inet | grep vio1 172.16.0/24 172.16.0.2 UCn 1 0 - 4 vio1 172.16.0.2 12:22:01:00:00:00 UHLl 0 0 - 1 vio1 172.16.0.3 link#2 UHLch 1 4 - 3 vio1 172.16.0.255 172.16.0.2 UHb 0 0 - 1 vio1 172.16.1/24 172.16.0.3 UGS 0 0 - 8 vio1 obsd-02# obsd-02# obsd-02# ifconfig vio1 vio1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 12:22:01:00:00:00 index 2 priority 0 llprio 3 groups: egress media: Ethernet autoselect status: active inet 172.16.0.2 netmask 0xffffff00 broadcast 172.16.0.255 obsd-02# > 4 янв. 2024 г., в 12:41, Solène Rapenne <sol...@perso.pw> написал(а): > > Le 04/01/2024 à 10:32, Alexander Okonnikov a écrit : >> To move issue with 'default' in netstat output into separate thread. >> It seems that in OpenBSD 'default' is just alias for 0.0.0.0/0 (as >> expected). For example, I can create just another 0.0.0.0/0 route, and it >> will be displayed as 'default' as well. >> obsd-02# cat /etc/mygate >> 100.64.5.254 >> obsd-02# netstat -rn -f inet | grep default >> default 100.64.5.254 UGS 0 0 - 8 vio0 >> obsd-02# >> obsd-02# route add -priority 10 0.0.0.0/0 172.16.0.3 >> add net 0.0.0.0/0: gateway 172.16.0.3 >> obsd-02# netstat -rn -f inet | grep default >> default 100.64.5.254 UGS 0 0 - 8 vio0 >> default 172.16.0.3 UGS 0 0 - 10 vio1 >> obsd-02# >> I also can delete default route, that is created based on /etc/mygate file. >> obsd-02# netstat -rn -f inet | grep default >> default 100.64.5.254 UGS 0 0 - 8 vio0 >> default 172.16.0.3 UGS 0 0 - 10 vio1 >> obsd-02# route delete 0.0.0.0/0 >> delete net 0.0.0.0/0 >> obsd-02# netstat -rn -f inet | grep default >> default 172.16.0.3 UGS 0 0 - 10 vio1 >> obsd-02# route delete 0.0.0.0/0 >> delete net 0.0.0.0/0 >> obsd-02# netstat -rn -f inet | grep default >> obsd-02# > > Thanks for testing this, could you also verify that if you use 0.0.0.0/0 the > interface joins the egress group? You can check this by using ifconfig, > search for the network interface and see if egress is listed in the field > Groups: >