> Steve Singer wrote: > Seems the driver doesn't work correctly, try again, > and see the result.
When I try it now (TKIP on the AP). I get the same behaviour, dladm: cannot connect link 'iwi0': operation timed out Feb 11 22:02:00 t42s mac: [ID 744254 kern.info] NOTICE: iwi0 link up Feb 11 22:02:00 t42s in.routed[444]: [ID 749644 daemon.notice] iwi0 has a bad address 0.0.0.0 Feb 11 22:02:00 t42s mac: [ID 486395 kern.info] NOTICE: iwi0 link down Feb 11 22:02:12 t42s mac: [ID 744254 kern.info] NOTICE: iwi0 link up Feb 11 22:02:12 t42s in.routed[444]: [ID 749644 daemon.notice] iwi0 has a bad address 0.0.0.0 Feb 11 22:02:12 t42s mac: [ID 486395 kern.info] NOTICE: iwi0 link down Feb 11 22:03:03 t42s mac: [ID 744254 kern.info] NOTICE: iwi0 link up Feb 11 22:03:03 t42s in.routed[444]: [ID 749644 daemon.notice] iwi0 has a bad address 0.0.0.0 Feb 11 22:03:03 t42s mac: [ID 486395 kern.info] NOTICE: iwi0 link down Feb 11 22:03:14 t42s mac: [ID 744254 kern.info] NOTICE: iwi0 link up Feb 11 22:03:14 t42s in.routed[444]: [ID 749644 daemon.notice] iwi0 has a bad address 0.0.0.0 Feb 11 22:03:14 t42s mac: [ID 486395 kern.info] NOTICE: iwi0 link down Feb 11 22:03:55 t42s mac: [ID 744254 kern.info] NOTICE: iwi0 link up Feb 11 22:03:55 t42s mac: [ID 486395 kern.info] NOTICE: iwi0 link down Feb 11 22:03:59 t42s in.routed[444]: [ID 464608 daemon.error] route 192.0.0.0/8 --> 192.168.1.4 nexthop is not directly connected but I do not see the generate the master_stop() error. It happened a few times yesterday but I've rebooted since then. > > -- > Quaker This message posted from opensolaris.org
