ZoneMinder Forums

i can not seem to connect to this thing via ethernet connection i have tried and tried....i have done a hard reset on the device and still wont talk out to 192.168.0.90 the default factory ip to connect to on the device

also below is a packet capture that may help someone help me determine what is going on i did a packet capture on eth0 the same port that the axis 206 camera is plugged into

tcpdump -i eth0
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
20:23:32.333343 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:23:33.393321 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:23:35.453254 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:23:50.763717 IP 169.254.65.159.mdns > 224.0.0.251.mdns: 0*- [0q] 12/0/0 (Cache flush) A 169.254.65.159,[|domain]
20:24:39.602408 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:24:41.662313 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:24:43.722374 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:24:54.762904 IP 169.254.65.159.mdns > 224.0.0.251.mdns: 0*- [0q] 6/0/0[|domain]
20:25:47.871874 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:25:49.931709 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:25:51.991841 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:26:56.141129 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:26:58.200946 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:27:00.261179 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:27:02.761378 IP 169.254.65.159.mdns > 224.0.0.251.mdns: 0*- [0q] 6/0/0[|domain]
20:28:03.410485 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:28:05.470337 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:28:07.535384 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:29:11.679836 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:29:13.740042 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:29:15.799822 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:30:19.949193 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:30:22.009077 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:30:24.069086 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:31:18.759021 IP 169.254.65.159.mdns > 224.0.0.251.mdns: 0*- [0q] 6/0/0[|domain]
20:31:28.218388 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:31:30.278446 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:31:32.338465 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548

Hi,

I have several of the 207 model and I wanted a Static IP, so I set the IP address using arp and ping like in the manual. I looked on line at the manual for the 206 and from memory it looks like the same procedure. I see the "default factory ip" in the manual, but Inever really tried it.

Have you tried to set the address? Is it in the same address range as ZM?

Not much of an answer, but you might try setting the IP yourself.

Keith

agree that it sounds like the IP is not set in the device or you have your network on a different subnet maybe?

decadude wrote: tcpdump -i eth0
tcpdump: WARNING: eth0: no IPv4 address assigned

This is means you haven't statically assigned the device an address.

decadude wrote: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
20:23:32.333343 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:23:33.393321 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548
20:23:35.453254 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:40:8c:74:10:cd (oui Unknown), length 548

This is the device trying to obtain an IP from a DHCP server.

decadude wrote: 20:23:50.763717 IP 169.254.65.159.mdns > 224.0.0.251.mdns: 0*- [0q] 12/0/0 (Cache flush) A 169.254.65.159,[|domain]

The 169.254.65.159 and 224.0.0.251 are APIPA addresses and basically tells us that the next device upstream isn't providing a dhcp response or you do not have a working dhcp server on the network.