cnPilot e400 Mesh Base/Client - No IP Address Assigned

I have 2 cnPilot e400 connected to my home network.

I have connnfigured one as Base (192.168.1.4) and the other as Client (192.168.1.5).

Router is on 192.168.1.1

I can connect see the SSID but all devices fail to connect as no IP Address are being assigned via DHCP.

Can you please help - not sure what I am doing wrong (newbie to networking).

Configs attached.

Also noticed that when I enable the Base it knocks out my router – the network goes down.

Not sure what I have done wrong.

Disabling Mesh Vlan Tagging on both Mesh Base and Mesh Client APs and test.

Thank you Gupta-Bobby - that worked to get me an IP Address to the device

The problem of the router dropping out continues - I loose connection to the internet every few minutes.

The wifi is persistent but I loose the router.

Any ideas?

Create a separate SSID on Base AP and Client AP for wireless clients to connect by setting Mesh as Off. 

In general working scenario:

1. In both Mesh Base and Mesh Client SSID, mesh VLAN tagging is not disabled.

2. Wireless Clients should always connect to separate SSID which has setting Mesh Off. 

From wireless clients try pinging your router continously and then to 8.8.8.8 and see which on is droping.

1 Like

Thank you - yes - I have tried this with both AP - set them up individually with their own SSID and mesh off.

They work fine in this mode. Both can be accessed and devices retain their connection. Router is fine.

The moment I setup the mesh with Base and Client with same SSID, problem arise with the router.

Even if I connect outside the mesh on another Wifi access point, the router goes down every few minutes.

When this happens I am forced to unplub the Base unit to access the network again.

I dont believe its the DNS 8.8.8.8 but more the Base is conflicting with the router 192.168.1.1

Here are my pings to 192.168.1.1 when I enable Base/Client:

64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=3125.783 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=1117.062 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=2120.884 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=430.726 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=51.043 ms
ping: sendto: No route to host
Request timeout for icmp_seq 36
64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=1.574 ms
64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=42.033 ms
ping: sendto: No route to host
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=52.653 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=36.087 ms
64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=38.572 ms
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
64 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=36.373 ms
64 bytes from 192.168.1.1: icmp_seq=47 ttl=64 time=48.887 ms
64 bytes from 192.168.1.1: icmp_seq=48 ttl=64 time=62.673 ms
Request timeout for icmp_seq 49
64 bytes from 192.168.1.1: icmp_seq=50 ttl=64 time=106.653 ms
Request timeout for icmp_seq 51
Request timeout for icmp_seq 52
Request timeout for icmp_seq 53
Request timeout for icmp_seq 54
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59
Request timeout for icmp_seq 60
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62
Request timeout for icmp_seq 63
Request timeout for icmp_seq 64
Request timeout for icmp_seq 65
Request timeout for icmp_seq 66
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72

Hi,

In case of mesh setup, your mesh client AP’s ethernet port should be disabled/disconnected and it should connect via wireless to mesh base AP. If mesh client ethernet is up, it will form a loop, please make sure to disable/disconnect the same.

Thanks,
Divakar

3 Likes

Worked a treat - thank you.

Currently running into same problem. Have an E500 set as Base and 2 E500 set as clients. The mesh is set and runs, but refuses to hand out IP addresses to end users that connect to SSID. Tried disabling the Mesh Vlan Tagging and still couldn’t receive IP address.

Would setting the APs to a static IP address be helpful?

Why do you suggest turning off mesh? Just as a temporary fix for end users to connect to network?