Hi Guys,
I joined yesterday. I Spoke to Yayzi earlier/yesterday (Whatsapp) and it got passed to their networks team. Just wondering if there is anything I can do while I wait.
I have my router set up EX230. I have the VLAN set to 911. I am able to get an IPv6 address address but not able to get an IPv4 address from Yayzi (WAN). I have looked through the logs and and noticed it’s trying to request an address from the DHCP but no response.
I noticed it trying from 154.56.254.x and assigned this statically. This brought the internet up for about 5 mins (long enough to run a speed test) before I got kicked (understandably).
Any suggestions?
Dan
Have you rebooted both the router and ONT?
Odd that you got the IPv6 and not V4.
You can always email them as this sometimes gets seen to faster. [email protected]
Did you get a Yayzi router as well or no?
Yes Yayzi router: TP Link EX230.
What time do they log off for the day?
Could you try factory reset the unit?
They don’t really have a time as sometimes they tend to check tickets after hours. But 100% 9-5.
1 Like
Still no luck Im afraid.
Heres the log file:
BBA Platform version:3.1.8-rc17
2016-01-01 00:00:48 [5] System: Enable IPv4 SPI Firewall
2016-01-01 00:00:48 [5] System: Enable IPv6 SPI Firewall
2016-01-01 00:00:51 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2016-01-01 00:00:53 [4] VoIP: prefix ‘x’, you enabled this rule for some endptbut didn’t indicate the destination.
2016-01-01 00:00:57 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:00:59 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:01 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:05 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:08 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:10 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
2016-01-01 00:01:20 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:22 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:24 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:28 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:28 [5] Mesh: Add Device :MAC : A8:6E:84:A3:86:A3
2016-01-01 00:01:30 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:01:32 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
2016-01-01 00:01:37 [5] Mesh: Success Add Client : MAC : 02:B2:AF:74:56:4D
2016-01-01 00:01:37 [5] DHCPD: Recv DISCOVER from 02:B2:AF:74:56:4D
2016-01-01 00:01:37 [5] DHCPD: Send OFFER with ip 192.168.0.100
2016-01-01 00:02:12 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:02:14 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:02:16 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:02:20 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:02:22 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:02:24 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
2016-01-01 00:03:35 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:03:37 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:03:39 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:03:43 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:03:45 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:03:47 [5] DHCPC: Recv no OFFER, DHCP Service unavailable
Yeah looks like a DHCP server issue. @Yayzi_Team will be aware if they have assigned to the network team 
1 Like
I have just noticed it trying again and received and offer but it didnt stick.
2016-01-01 00:07:50 [5] DHCPC: Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:07:50 [5] DHCPC: Recv OFFER from server 154.56.254.1 with ip 154.56.254.147 (from D4:6D:50:2D:B9:B6 to A8:6E:84:A3:86:A4)
2016-01-01 00:07:50 [5] DHCPC: Send REQUEST to server 154.56.254.1 with request ip 154.56.254.147 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:07:52 [5] DHCPC: Send REQUEST to server 154.56.254.1 with request ip 154.56.254.147 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:07:54 [5] DHCPC: Send REQUEST to server 154.56.254.1 with request ip 154.56.254.147 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:08:04 [5] DHCPC: Send DISCOVER with request ip 154.56.254.147 and unicast flag 1 (from A8:6E:84:A3:86:A4 to FF:FF:FF:FF:FF:FF)
2016-01-01 00:08:06 [5] DHCPC: Send DISCOVER
Not heard anything from Yayzi all day. Have just emailed as suggested. Hopefully this will be sorted soon as Im starting to wonder if Ive made the right move.
Date and time have been set previously but will try again. Isnt the time normally set via ntp on the router? Obviously requires an IP first.
Got a reponse via email saying they don’t monitor the forums so will see if this method works.
No luck with time set correctly
1 Like
Just to keep this page updated in case anyone comes across it in the future.
Email has been passed to networks. Configurations of both the router and Yayzi’s end are set up correctly. Waiting to see what networks say.
1 Like
Hi Guys,
Just to close this off. Networks have changed some stuff, looks like a different IP range 217.x and were up and running.
Thanks all.
2 Likes