S
Steve Quatrano
Been working on it 24 hours now with support from HP leading nowhere.
I spent 3 hours last night waiting for a verizon tech and another 30
minutes so far today. In the process i managed to check my firmware
in my MI424-WR Actiontec router from Verizon from
4.0.16.1.45.160 to
4.0.16.1.55.0.10.4.3
I have found lots of posts on problems with this router but a) no
satisfying answers and b) not much specifically about Vista
compatibility problems.
I have noticed some strange messages in the router logfile that appear
to come from this computer trying to get an IP address.
This is the oddest one:
kern.debug New IGMP type=34, why we do not know about it?
But I am also seeing LOTS of these messages filling up the log:
daemon.warn cLink: clink0: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.
daemon.warn cLink: clink1: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.
I spent 3 hours last night waiting for a verizon tech and another 30
minutes so far today. In the process i managed to check my firmware
in my MI424-WR Actiontec router from Verizon from
4.0.16.1.45.160 to
4.0.16.1.55.0.10.4.3
I have found lots of posts on problems with this router but a) no
satisfying answers and b) not much specifically about Vista
compatibility problems.
I have noticed some strange messages in the router logfile that appear
to come from this computer trying to get an IP address.
This is the oddest one:
kern.debug New IGMP type=34, why we do not know about it?
But I am also seeing LOTS of these messages filling up the log:
daemon.warn cLink: clink0: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.
daemon.warn cLink: clink1: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1:
Bad address.