ZipGateway in IPv4


#1

Hi,
can I use ZipGateway using ipV4 network instead ipv6?
How must I change zipgateway.cfg for to do this?

Thanks


#2

zipgateway periodically broadcasts DHCPDISCOVER messages for nodes it has probed. If there is a DHCP server present in the network that can answer these messages with IPv4 address offers, then both the zipgateway and the Z-Wave nodes will be reachable at IPv4 addresses - no configuration values in zipgateway.cfg are needed.

/Hans


#3

Hello!

@hanskroner Thank you for this explanation.

I installed Z/IP Gateway and configured it to use my WiFi adapter (it’s called wlp3s0).

$ ifconfig
enp0s25   Link encap:Ethernet  HWaddr 68:f7:28:f9:de:53
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:20 Memory:e1200000-e1220000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:5010 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5010 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15499901 (15.4 MB)  TX bytes:15499901 (15.4 MB)

tap0      Link encap:Ethernet  HWaddr 76:12:ab:59:a7:b6
          inet addr:10.7.36.41  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: fe80::7412:abff:fe59:a7b6/64 Scope:Link
          inet6 addr: fd00:aaaa::7412:abff:fe59:a7b6/64 Scope:Global
          inet6 addr: fd00:aaaa::1234/128 Scope:Global
          inet6 addr: fd00:aaaa::78b5:53e:a500:4368/64 Scope:Global
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:76248 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10472 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:23575001 (23.5 MB)  TX bytes:1034931 (1.0 MB)

wlp3s0    Link encap:Ethernet  HWaddr 5c:e0:c5:c0:44:5a
          inet addr:10.7.36.41  Bcast:10.7.36.255  Mask:255.255.255.0
          inet6 addr: fd00:aaab::9548:6f03:96da:67b1/64 Scope:Global
          inet6 addr: fd00:aaab::3542:84f9:8f2f:97d/64 Scope:Global
          inet6 addr: fe80::aa0a:ba1d:1ec3:e26e/64 Scope:Link
          inet6 addr: fd00:aaab::1821:3e6:10ed:61dd/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:123353 errors:0 dropped:0 overruns:0 frame:0
          TX packets:271175 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:30262559 (30.2 MB)  TX bytes:66596974 (66.5 MB)

The host connects to the local network through this adapter; and gets its own IPv4 address successfully. Thus DHCP server works perfectly and the host is reachable by its IPv4 address. But when I try to determine IP addresses of my Z/IP network I see only IPv6 addresses:

$ avahi-browse _z-wave._udp -r
+   tap0 IPv6 Static Controller [c6a173a70100]              _z-wave._udp         local
+   tap0 IPv6 Switch Binary [c6a173a70500]                  _z-wave._udp         local
=   tap0 IPv6 Static Controller [c6a173a70100]              _z-wave._udp         local
   hostname = [zwC6A173A701.local]
   address = [fd00:aaaa::3]
   port = [41230]
   txt = ["icon=" "txtvers=1" "securityClasses=▒" "productID=" "mode=" "epid=" "info=^V"W▒#Xtl▒"]
=   tap0 IPv6 Switch Binary [c6a173a70500]                  _z-wave._udp         local
   hostname = [zwC6A173A705.local]
   address = [fd00:bbbb::5]
   port = [41230]
   txt = ["icon=" "txtvers=1" "securityClasses=" "productID=v" "mode=" "epid=" "info=^%\▒Y▒r2"]

I made some investigation according to your comment and found out that DHCPDISCOVER messages go to the wrong interface (not to wlp3s0 which I configured during the installation). I checked it with dhcpdump utility.

$ sudo dhcpdump -i tap0
  TIME: 2018-08-30 16:02:12.481
    IP: 0.0.0.0 (0:1e:32:1b:b:e4) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
    OP: 1 (BOOTPREQUEST)
 HTYPE: 1 (Ethernet)
  HLEN: 6
  HOPS: 0
   XID: 66ae042c
  SECS: 0
 FLAGS: 7f80
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 00:1e:32:1b:0b:e4:00:00:00:00:00:00:00:00:00:00
 SNAME: .
 FNAME: .
OPTION:  53 (  1) DHCP message type         1 (DHCPDISCOVER)
OPTION:  61 (  8) Client-identifier         00:00:00:1e:32:1b:0b:e4
OPTION:  55 (  3) Parameter Request List      1 (Subnet mask)
                                              3 (Routers)
                                              6 (DNS server)

How can I fix this behaviour and configure my Z/IP Gateway to use the proper interface?


#4

Does anyone know the reason?


#5

It seems that the wireless installation does not work at all.