dhcpcd-discuss

greetings,

> Hi
> 
> On 22/12/2013 7:07, Dagg Stompler wrote:
> > by carrier you mean ifconfig tap2 up? if so the interface is up, I'll
> > verify and run again, the issue occurs to me when I start tap2 as
> > service, in that case it should be up because I see no problems when
> > starting br0 for example.
> 
> No, carrier is a flag set by the device driver to say that it's all 
> working at both ends.
> On Linux is basically boils down to UP and RUNNING as shown by ifconfig.
> You could also try a newer dhcpcd version as some fixes have been made 
> in regards to carrier handling.

tried that, still no go, see:
NCC-5001-D dagg # ifconfig tap2
tap2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 0a:f8:1e:71:23:92  txqueuelen 500  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

NCC-5001-D dagg # dhcpcd tap2
dhcpcd[16884]: version 6.1.0 starting
dhcpcd[16884]: tap2: waiting for carrier
dhcpcd[16884]: timed out
dhcpcd[16884]: allowing 8 seconds for IPv4LL timeout
dhcpcd[16884]: timed out
dhcpcd[16884]: exited