Dropbear error: interface nebula1 has no physdev or physdev has no suitable ip

I'd like to explicitly indicate which interfaces I allow dropbear to listen on and when specifying nebula1 I get the follwoing error:

SG-105 in ~ # service dropbear restart
interface nebula1 has no physdev or physdev has no suitable ip

SG-105 in ~ # cat /etc/config/dropbear 

config dropbear
        option Port '22'
        option Interface 'lan'

config dropbear
        option Port '22'
        option Interface 'nebula1'

SG-105 in ~ # ifconfig nebula1
nebula1   Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:aaa.bbb.ccc.ddd  P-t-P:aaa.bbb.ccc.ddd  Mask:
          RX packets:69 errors:0 dropped:0 overruns:0 frame:0
          TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:8974 (8.7 KiB)  TX bytes:9188 (8.9 KiB)

I've masked the actual IP, but it is there.

I wonder if it's something I need to fix in nebula package? It's a kmod-tun interface -- do I need to add something to /etc/config/network? Can I do it dynamically within PROCD objects? Tagging @jow for the PROCD question.

1 Like

It should just work if you avoid interface binding for Dropbear.
An ideal method is implementing netifd support for nebula.
Declaring an unmanaged interface can be a workaround.

1 Like

Thanks for your prompt reply. I do want to bind to specific interfaces, as I'm not sure how it would behave towards the wg "peers" if not interface-bound.

I'll see what I need to do for the netifd support.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.