DNS Disconnecting in Granny Flat

[AndrewSr]

I currently live in the granny flat and am a heavy gamer. I am using a powerline adaptor to connect a 2nd router as an access point to my main router. The connection speeds are flawless and there is no lag at all! However, about twice a day, I have to reset the router in my room due to a disconnect to the DNS and that fixes it momentarily. I was wondering if anybody knew how to fix this issue? Would you suggest I conenct the router straight to the NBN box? Or would I have to use a super long ethernet cord to connect it directly to the main router without the powerline adaptor? 

I have attempted WIFI extenders but they are even less stable. I am using a router because I have multiple consoles and a PC that I prefer using ethernet connection for. Normally I would connect the powerline adaptor straight to my computer, but then I will have no WIFI access in my room. 

I was just wondering if there was another option that would solve this issue!

[david64]

Hi @AndrewSr . Does your granny flat have its own NBN connection separate from the NBN connection of the main house? Or, does the granny flat connect to the NBN connection of the main house?

What is the distance between main house and granny flat?

What type of NBN connection does the main house/granny flat have?

Powerline adapters need to be connected on same electrial circuit (fuse) for best performance. 

What are the models of the two routers you have?

How have you configured the second router?

Which DNS are you using? When you lose connection to it, can you ping it?

Can you ping the ip address of the main router in the flat?

Can it recover by itself?

Do you factory reset your router or just restart it?

[AndrewSr]

So normally, the granny flat doesn't have any connection. the NBN to the house is FTTP and is connected ot the main router which is a DLINK Viper 2600 DSL3900. 

The distance between the two is a decent distance. I definitely can't connect wirelessly to the main router. I am using a dlink powerline adaptor, but an older model (AV500) and it is on the same electrical line so it works. 

The second router is a DAP1900 and I feel as though I have configured it. I tried reconfiguring the DNS and what not but it is still happening. it is possible that this is where i need help.

In terms of pinging the ip address I'm guessing through cmd? I don't really know how to do this i'll be honest.

It doesn't ercover by itself, i have to reset the router (off and on, not factory reset).

I know that ultimately i can run an ethernet from my main router all the way down to the router in my room, but i'd rather avoid that if possible. IF not, I will look into that 

[david64]

@AndrewSr . The house has FTTP connection. House router is Viper DSL3900. Ethernet connection to AV500 powerline adapter.   Flat has AV500. Ethernet connection to DAP1900.   Is this correct?

AV500 is rather slow and you may miss out on some speed capability. Has 100Mbps LAN port.

You want DAP1900 in Extender mode. It gets its ip address from Viper. Give the DAP1900 a fixed ip address on Viper, say 192.168.1.2, so you can login to its admin page easily. That leaves 3 ethernet ports on DAP1900 plus its wifi. You can connect a switch if needed.

Regarding dropout, you need to know if the powerline connection is dropping, or fault in the DAP1900.

I assume the internet connection in the house is always ok, even when the flat loses connection.

On ethernet computer, open command window. 

ping -n 10 192.168.1.1                    ping the Viper to test powerline connection

If timeout,    ping 192.168.1.2        or whatever address you gave the DAP1900

If this is ok, then powerline problem. You can't get through to house router.

If not ok, problem with DAP1900.

[AndrewSr]

That is the correct connection.

My speeds have actually been really good, but do you think a better model would provide a more stable DNS connection?

I don't really know how to put it in extender mode. I think I have tried and it is in that mode now. I used the 8.8.8.8 as primary DNS

8.8.4.4 secondary DNS

the current ip is 192.168.1.12

I have matched the same DNS on the Viper as that was what TPG told me to do.

When the dropout occurs, the router flashes red. the internet in the main house is fine! The router in the room loses the connection to the DNS. I am pretty sure the powerline is stable but it is possible that it's not. 

Can i test the viper connection from my room or would i have to directly connect to the Viper?

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 10ms, Average = 3ms

[david64]

@AndrewSr . What down and up speeds do you get onTPGs speed test using your ethernet computer?

What is the plan speed of the FTTP connection?

Since your setup does work, leave it as is. You need to check response times in your network. Use your ethernet computer. Use  -n  parameter to do enough pings to get a good indication of response times. Ping the DAP1900, the Viper router, Google DNS.

When you have DNS disconnection, do the commands again. Omit -n parameter. 

You can download the DAP manual from

http://support.dlink.com.au/Download/download.aspx?product=DAP-1900&revision=REV_A&filetype=Manuals

[AndrewSr]

I have the 50MBS plan and I pretty much get those speeds! Both on the computer and the wifi on my phone!

I used the manual initially and connected the router to extend my network

I will attempt pinging again. I don’t really know how to differentiate what I am pinging though, I’m guessing the different IP Addresses?

[AndrewSr]

I'm not entirely sure what I am looking for tbh. I dont really know what my next step is and I'm quite confused. I'm quite frustrated but I think I will have to somehow connect an ethernet between the routers. I just don't understand why it works and then randomly cuts out.

[david64]

@AndrewSr . The point of doing the pings is to find out which piece of the path between your computer and the internet is failing. All the tests are done from your computer in your room connected to the DAP.

First piece of path is the DAP (192.168.1.12 you said). On the basis of having to reboot this, it could be the problem. If you can't ping it, it is the problem.

If you can ping it, the next piece of the path is the powerline connection to the Viper.

Ping the Viper (192.168.1.1). If you can ping it, the powerline connection is ok.

If you can't, the two AV500 might be the problem.

You say the Viper doesn't lose its internet connection, If you can ping the Viper, I'd expect that Google would be working.

If the DAP indicator is blinking red, it is in Recovery Mode, whatever that means. 

This looks to be the settings for Extender mode which I think is the better way to set it up.

Look in DAP manual on P4. You are trying to do Extend Your Wireless Network using Ethernet (which is what the AV500 does).

P21 shows setting to make it an extender.  Existing Network is Ethernet.

P26 is extender settings.  Disable Smart Connect gives access to 2.4G and 5G settings (P29,30).

P31 make LAN connection Dynamic IP.  On Viper, make ip address reservation for the DAP's mac address  of 192.168.1.12. 

[AndrewSr]

Below is all the information regarding my pings. I believe they are connected fine (My DNS is working atm so i wil ltry again when this cuts out).

I have followed your steps and will see how it goes! Thank you so much for helping out ! 

C:\Users\MCC Synclair>ping -n 10 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 11ms, Average = 3ms

C:\Users\MCC Synclair>ping -n 10 192.168.1.10

Pinging 192.168.1.10 with 32 bytes of data:
Reply from 192.168.1.10: bytes=32 time=84ms TTL=64
Reply from 192.168.1.10: bytes=32 time=99ms TTL=64
Reply from 192.168.1.10: bytes=32 time=555ms TTL=64
Reply from 192.168.1.10: bytes=32 time=64ms TTL=64
Reply from 192.168.1.10: bytes=32 time=29ms TTL=64
Reply from 192.168.1.10: bytes=32 time=47ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.10:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 555ms, Average = 146ms