Hey all. I have my router/modem (Netcomm nf4v) in the lounge, and ran a 15m ethernet cable (Cat5E) from there, through the ceiling space, to my bedroom. This was originally just plugged in to the PC and ran at 1gbps.I have now got a netcomm N300 NF5 plugged in to this, using as an access point. I have done what I have previously done when doing a setup like this. Not needing WAN to Lan or anything, just a simple LAN to LAN Access Point setup.Accessed the N300 (AP), disabled DHCP. Changed the Default Network/assigned IP to 192.168.20.2Accessed the nf4v. Its IP is set to 192.168.20.1. All good. Its DHCP enabled, with a range of 192.168.20.100 to 192.168.20.200Plugged both cables in, connected to LAN ports not WAN.Now I connect up and I can ping -t the access point on 192.168.20.2 fine.However, when I ping -t 192.168.20.1 I am getting major packet loss making the internet unusable.eg,C:\Users\User>ping -t 192.168.20.1Pinging 192.168.20.1 with 32 bytes of data:Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Request timed out.Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Request timed out.Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Request timed out.Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Reply from 192.168.20.1: bytes=32 time<1ms TTL=64Request timed out.Reply from 192.168.20.1: bytes=32 time<1ms TTL=64I have disconnected the access point and tried plugging this straight back into the PC and it runs fine without packet loss. Have I missed something simple somewhere???????
↧