NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

bin/39603: postfix doesn't see all "active" network interfaces

>Number:         39603
>Category:       bin
>Synopsis:       postfix doesn't see all "active" network interfaces
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 22 02:20:00 +0000 2008
>Originator:     Martin S. Weber
>Release:        4.99.72 / i386
NetBSD agamemnon.entropie.local 4.99.72 NetBSD 4.99.72 (AGAMEMNON) #4: Sat Sep 
20 20:45:58 EDT 2008  
postfix on startup checks for its own inet-address(es). On my machine it 
wouldn't find the (active) ath0, maybe because there's an inactive wm0, too. 
Complaint at system startup, or even later after wpa_supplicant and dhclient 
helped ath0 come online, are simply:

postfix: fatal: could not find any active network interfaces

But look:

# ifconfig -a
wm0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: somemac
        media: Ethernet autoselect (none)
        status: no carrier
        ssid SOME nwkey yeahsuremykeystandshere
        powersave off
        bssid somebssid chan 1
        address: somemac
        media: IEEE802.11 autoselect (OFDM54 mode 11g)
        status: active
        inet netmask 0xffffff00 broadcast
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet netmask 0xff000000

I mean I'm writing this via that ath0, it surely is active.
Not sure exactly. On my machine, start postfix with wm0 inactive and ath0 
active. Maybe it's enough to have > 1 network if on the machine and simply 
configure the second+ while leaving the 1st offline ?
Find postfix developers and give them more beer.

Home | Main Index | Thread Index | Old Index