Why after setting up a router as an access point I can't reach it anymore?
I have a Xiaomi mi router, and I have made this simple configuration:
internet --- main router (with internet)------lan cable----xiaomi router
I want to use the wifi from the xiaomi in another room. So I have disable DHCP on the xiaomi, setted up the wireless, and restarted it. To make this changes I connected to the router default address: 192.168.31.1. After having restarted everything, I am able to access to internet from the deviced connected to the Xiaomi mi router wifi, but can't access the router anymore to the address 192.168.31.1. If I go on my macbook network panel to see which router I am connected to, it indicates my main router with the IP (192.168.178.1).
But I am connected to the xiaomi router. It is like my xiaomi in "invisible", but I am not an expert of network, so I can't understand why, and how I can do a proper configuration to achieve the same result but mantaining the access to my xiaomi router.
networking wireless-networking router wireless-router wireless-access-point
|
show 4 more comments
I have a Xiaomi mi router, and I have made this simple configuration:
internet --- main router (with internet)------lan cable----xiaomi router
I want to use the wifi from the xiaomi in another room. So I have disable DHCP on the xiaomi, setted up the wireless, and restarted it. To make this changes I connected to the router default address: 192.168.31.1. After having restarted everything, I am able to access to internet from the deviced connected to the Xiaomi mi router wifi, but can't access the router anymore to the address 192.168.31.1. If I go on my macbook network panel to see which router I am connected to, it indicates my main router with the IP (192.168.178.1).
But I am connected to the xiaomi router. It is like my xiaomi in "invisible", but I am not an expert of network, so I can't understand why, and how I can do a proper configuration to achieve the same result but mantaining the access to my xiaomi router.
networking wireless-networking router wireless-router wireless-access-point
Why did you disable DHCP?
– CharlieRB
Mar 18 '16 at 19:25
I have read it on a guide
– ciaoben
Mar 18 '16 at 19:38
Reading it in a guide doesn't tell me much. Nor does it tell me why the guide is disabling DHCP. Does your "main router" have DHCP enabled? Or is it just a broadband modem provided by your internet company?
– CharlieRB
Mar 18 '16 at 19:43
sorry I know I can't help much! anyway On the main router I have DHCP enabled!
– ciaoben
Mar 18 '16 at 19:46
When you turned off DHCP, you disabled the ability of the router to set IP addresses. They now come from the main router. This explains why you can no longer use192.168.31.1to access the router. Have you tried to access the router at192.168.178.1?
– CharlieRB
Mar 18 '16 at 19:50
|
show 4 more comments
I have a Xiaomi mi router, and I have made this simple configuration:
internet --- main router (with internet)------lan cable----xiaomi router
I want to use the wifi from the xiaomi in another room. So I have disable DHCP on the xiaomi, setted up the wireless, and restarted it. To make this changes I connected to the router default address: 192.168.31.1. After having restarted everything, I am able to access to internet from the deviced connected to the Xiaomi mi router wifi, but can't access the router anymore to the address 192.168.31.1. If I go on my macbook network panel to see which router I am connected to, it indicates my main router with the IP (192.168.178.1).
But I am connected to the xiaomi router. It is like my xiaomi in "invisible", but I am not an expert of network, so I can't understand why, and how I can do a proper configuration to achieve the same result but mantaining the access to my xiaomi router.
networking wireless-networking router wireless-router wireless-access-point
I have a Xiaomi mi router, and I have made this simple configuration:
internet --- main router (with internet)------lan cable----xiaomi router
I want to use the wifi from the xiaomi in another room. So I have disable DHCP on the xiaomi, setted up the wireless, and restarted it. To make this changes I connected to the router default address: 192.168.31.1. After having restarted everything, I am able to access to internet from the deviced connected to the Xiaomi mi router wifi, but can't access the router anymore to the address 192.168.31.1. If I go on my macbook network panel to see which router I am connected to, it indicates my main router with the IP (192.168.178.1).
But I am connected to the xiaomi router. It is like my xiaomi in "invisible", but I am not an expert of network, so I can't understand why, and how I can do a proper configuration to achieve the same result but mantaining the access to my xiaomi router.
networking wireless-networking router wireless-router wireless-access-point
networking wireless-networking router wireless-router wireless-access-point
asked Mar 18 '16 at 16:52
ciaobenciaoben
10112
10112
Why did you disable DHCP?
– CharlieRB
Mar 18 '16 at 19:25
I have read it on a guide
– ciaoben
Mar 18 '16 at 19:38
Reading it in a guide doesn't tell me much. Nor does it tell me why the guide is disabling DHCP. Does your "main router" have DHCP enabled? Or is it just a broadband modem provided by your internet company?
– CharlieRB
Mar 18 '16 at 19:43
sorry I know I can't help much! anyway On the main router I have DHCP enabled!
– ciaoben
Mar 18 '16 at 19:46
When you turned off DHCP, you disabled the ability of the router to set IP addresses. They now come from the main router. This explains why you can no longer use192.168.31.1to access the router. Have you tried to access the router at192.168.178.1?
– CharlieRB
Mar 18 '16 at 19:50
|
show 4 more comments
Why did you disable DHCP?
– CharlieRB
Mar 18 '16 at 19:25
I have read it on a guide
– ciaoben
Mar 18 '16 at 19:38
Reading it in a guide doesn't tell me much. Nor does it tell me why the guide is disabling DHCP. Does your "main router" have DHCP enabled? Or is it just a broadband modem provided by your internet company?
– CharlieRB
Mar 18 '16 at 19:43
sorry I know I can't help much! anyway On the main router I have DHCP enabled!
– ciaoben
Mar 18 '16 at 19:46
When you turned off DHCP, you disabled the ability of the router to set IP addresses. They now come from the main router. This explains why you can no longer use192.168.31.1to access the router. Have you tried to access the router at192.168.178.1?
– CharlieRB
Mar 18 '16 at 19:50
Why did you disable DHCP?
– CharlieRB
Mar 18 '16 at 19:25
Why did you disable DHCP?
– CharlieRB
Mar 18 '16 at 19:25
I have read it on a guide
– ciaoben
Mar 18 '16 at 19:38
I have read it on a guide
– ciaoben
Mar 18 '16 at 19:38
Reading it in a guide doesn't tell me much. Nor does it tell me why the guide is disabling DHCP. Does your "main router" have DHCP enabled? Or is it just a broadband modem provided by your internet company?
– CharlieRB
Mar 18 '16 at 19:43
Reading it in a guide doesn't tell me much. Nor does it tell me why the guide is disabling DHCP. Does your "main router" have DHCP enabled? Or is it just a broadband modem provided by your internet company?
– CharlieRB
Mar 18 '16 at 19:43
sorry I know I can't help much! anyway On the main router I have DHCP enabled!
– ciaoben
Mar 18 '16 at 19:46
sorry I know I can't help much! anyway On the main router I have DHCP enabled!
– ciaoben
Mar 18 '16 at 19:46
When you turned off DHCP, you disabled the ability of the router to set IP addresses. They now come from the main router. This explains why you can no longer use
192.168.31.1 to access the router. Have you tried to access the router at 192.168.178.1?– CharlieRB
Mar 18 '16 at 19:50
When you turned off DHCP, you disabled the ability of the router to set IP addresses. They now come from the main router. This explains why you can no longer use
192.168.31.1 to access the router. Have you tried to access the router at 192.168.178.1?– CharlieRB
Mar 18 '16 at 19:50
|
show 4 more comments
3 Answers
3
active
oldest
votes
This is exactly what you need, take a look. You need to make sure the plug is not the "Internet" port instead its the 2 other port. https://www.nextofwindows.com/how-to-configure-mi-wi-fi-as-second-router-to-extend-existing-network-same-ssid-roaming
er. The AP works. He dosen't know how to contact it.
– Journeyman Geek♦
Dec 2 '16 at 1:34
add a comment |
Kinda amusingly, the 'easiest' way to sort this out is by network scanning your network and identifying which one of these is your AP.
Zenmap is a pretty nice front end for nmap.

These are the settings I use. You'll want to change the target to "192.168.31.1-255", and hit scan. Then go have a cup of coffee. This takes a little while. It seems to do nothing at this time so be patient.
Essentially this gives you a list of hosts, and what they are running. Some interpretation is required depending on your device.
Once its done, it looks like this

You can click through each host, and interpret the output
The output looks something like this ideally - it tells you what ports are open, which is useless here, and then this information. The service info line is typically what you want in this case.
MAC Address: AC:22:00:00:00:00 (Asustek Computer)
Device type: general purpose
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6
OS details: Linux 2.6.8 - 2.6.27
Network Distance: 1 hop
Service Info: Host: RT-N56U; Device: WAP
This tells me My MAC address (and I can google the first 4 letters there to doublecheck who made it), what I run, and what it actually is - a RT-N56U access point.
In the case of my other AP, there's a bunch of junk data.
MAC Address: C4:A8:1D:84:F3:59 (Unknown)
No exact OS matches for host (If you know what OS is running on it, see http://nmap.org/submit/ ).....
Network Distance: 1 hop
Service Info: OS: Linux; CPE: cpe:/h:dlink:dir-865l:1.07, cpe:/o:linux:linux_kernel
Zenmap can't quite identify what it is, but gives you enough information to ID what it is - look at the service info line. It tells me it runs linux, its a CPE (consumer premises equipment) and its a dlink, dir-865l running firmware 1.07
add a comment |
It’s years old, but it deserves an answer!
First of all: There is absolutely no need to reset anything.
Your Xiaomi router is still reachable at 192.168.31.1. However, to communicate with it, you need to be in the same subnet. Currently, with DHCP from your main router, you’re in the 192.168.178.0/24 network while you want to be in the 192.168.31.0/24 network.
To access your Xiaomi router, manually change your PCs IP address to 192.168.31.2. You will not be able to access the Internet like this, though.
To be able to access your Xiaomi router during normal operation, you need to change its IP address. You could use 192.168.178.2, for example. Just make sure there is no IP address conflict. Preferably, the address would also be outside the DHCP range of your main router.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1054570%2fwhy-after-setting-up-a-router-as-an-access-point-i-cant-reach-it-anymore%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is exactly what you need, take a look. You need to make sure the plug is not the "Internet" port instead its the 2 other port. https://www.nextofwindows.com/how-to-configure-mi-wi-fi-as-second-router-to-extend-existing-network-same-ssid-roaming
er. The AP works. He dosen't know how to contact it.
– Journeyman Geek♦
Dec 2 '16 at 1:34
add a comment |
This is exactly what you need, take a look. You need to make sure the plug is not the "Internet" port instead its the 2 other port. https://www.nextofwindows.com/how-to-configure-mi-wi-fi-as-second-router-to-extend-existing-network-same-ssid-roaming
er. The AP works. He dosen't know how to contact it.
– Journeyman Geek♦
Dec 2 '16 at 1:34
add a comment |
This is exactly what you need, take a look. You need to make sure the plug is not the "Internet" port instead its the 2 other port. https://www.nextofwindows.com/how-to-configure-mi-wi-fi-as-second-router-to-extend-existing-network-same-ssid-roaming
This is exactly what you need, take a look. You need to make sure the plug is not the "Internet" port instead its the 2 other port. https://www.nextofwindows.com/how-to-configure-mi-wi-fi-as-second-router-to-extend-existing-network-same-ssid-roaming
answered Dec 2 '16 at 0:48
JonathanJonathan
1,18221425
1,18221425
er. The AP works. He dosen't know how to contact it.
– Journeyman Geek♦
Dec 2 '16 at 1:34
add a comment |
er. The AP works. He dosen't know how to contact it.
– Journeyman Geek♦
Dec 2 '16 at 1:34
er. The AP works. He dosen't know how to contact it.
– Journeyman Geek♦
Dec 2 '16 at 1:34
er. The AP works. He dosen't know how to contact it.
– Journeyman Geek♦
Dec 2 '16 at 1:34
add a comment |
Kinda amusingly, the 'easiest' way to sort this out is by network scanning your network and identifying which one of these is your AP.
Zenmap is a pretty nice front end for nmap.

These are the settings I use. You'll want to change the target to "192.168.31.1-255", and hit scan. Then go have a cup of coffee. This takes a little while. It seems to do nothing at this time so be patient.
Essentially this gives you a list of hosts, and what they are running. Some interpretation is required depending on your device.
Once its done, it looks like this

You can click through each host, and interpret the output
The output looks something like this ideally - it tells you what ports are open, which is useless here, and then this information. The service info line is typically what you want in this case.
MAC Address: AC:22:00:00:00:00 (Asustek Computer)
Device type: general purpose
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6
OS details: Linux 2.6.8 - 2.6.27
Network Distance: 1 hop
Service Info: Host: RT-N56U; Device: WAP
This tells me My MAC address (and I can google the first 4 letters there to doublecheck who made it), what I run, and what it actually is - a RT-N56U access point.
In the case of my other AP, there's a bunch of junk data.
MAC Address: C4:A8:1D:84:F3:59 (Unknown)
No exact OS matches for host (If you know what OS is running on it, see http://nmap.org/submit/ ).....
Network Distance: 1 hop
Service Info: OS: Linux; CPE: cpe:/h:dlink:dir-865l:1.07, cpe:/o:linux:linux_kernel
Zenmap can't quite identify what it is, but gives you enough information to ID what it is - look at the service info line. It tells me it runs linux, its a CPE (consumer premises equipment) and its a dlink, dir-865l running firmware 1.07
add a comment |
Kinda amusingly, the 'easiest' way to sort this out is by network scanning your network and identifying which one of these is your AP.
Zenmap is a pretty nice front end for nmap.

These are the settings I use. You'll want to change the target to "192.168.31.1-255", and hit scan. Then go have a cup of coffee. This takes a little while. It seems to do nothing at this time so be patient.
Essentially this gives you a list of hosts, and what they are running. Some interpretation is required depending on your device.
Once its done, it looks like this

You can click through each host, and interpret the output
The output looks something like this ideally - it tells you what ports are open, which is useless here, and then this information. The service info line is typically what you want in this case.
MAC Address: AC:22:00:00:00:00 (Asustek Computer)
Device type: general purpose
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6
OS details: Linux 2.6.8 - 2.6.27
Network Distance: 1 hop
Service Info: Host: RT-N56U; Device: WAP
This tells me My MAC address (and I can google the first 4 letters there to doublecheck who made it), what I run, and what it actually is - a RT-N56U access point.
In the case of my other AP, there's a bunch of junk data.
MAC Address: C4:A8:1D:84:F3:59 (Unknown)
No exact OS matches for host (If you know what OS is running on it, see http://nmap.org/submit/ ).....
Network Distance: 1 hop
Service Info: OS: Linux; CPE: cpe:/h:dlink:dir-865l:1.07, cpe:/o:linux:linux_kernel
Zenmap can't quite identify what it is, but gives you enough information to ID what it is - look at the service info line. It tells me it runs linux, its a CPE (consumer premises equipment) and its a dlink, dir-865l running firmware 1.07
add a comment |
Kinda amusingly, the 'easiest' way to sort this out is by network scanning your network and identifying which one of these is your AP.
Zenmap is a pretty nice front end for nmap.

These are the settings I use. You'll want to change the target to "192.168.31.1-255", and hit scan. Then go have a cup of coffee. This takes a little while. It seems to do nothing at this time so be patient.
Essentially this gives you a list of hosts, and what they are running. Some interpretation is required depending on your device.
Once its done, it looks like this

You can click through each host, and interpret the output
The output looks something like this ideally - it tells you what ports are open, which is useless here, and then this information. The service info line is typically what you want in this case.
MAC Address: AC:22:00:00:00:00 (Asustek Computer)
Device type: general purpose
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6
OS details: Linux 2.6.8 - 2.6.27
Network Distance: 1 hop
Service Info: Host: RT-N56U; Device: WAP
This tells me My MAC address (and I can google the first 4 letters there to doublecheck who made it), what I run, and what it actually is - a RT-N56U access point.
In the case of my other AP, there's a bunch of junk data.
MAC Address: C4:A8:1D:84:F3:59 (Unknown)
No exact OS matches for host (If you know what OS is running on it, see http://nmap.org/submit/ ).....
Network Distance: 1 hop
Service Info: OS: Linux; CPE: cpe:/h:dlink:dir-865l:1.07, cpe:/o:linux:linux_kernel
Zenmap can't quite identify what it is, but gives you enough information to ID what it is - look at the service info line. It tells me it runs linux, its a CPE (consumer premises equipment) and its a dlink, dir-865l running firmware 1.07
Kinda amusingly, the 'easiest' way to sort this out is by network scanning your network and identifying which one of these is your AP.
Zenmap is a pretty nice front end for nmap.

These are the settings I use. You'll want to change the target to "192.168.31.1-255", and hit scan. Then go have a cup of coffee. This takes a little while. It seems to do nothing at this time so be patient.
Essentially this gives you a list of hosts, and what they are running. Some interpretation is required depending on your device.
Once its done, it looks like this

You can click through each host, and interpret the output
The output looks something like this ideally - it tells you what ports are open, which is useless here, and then this information. The service info line is typically what you want in this case.
MAC Address: AC:22:00:00:00:00 (Asustek Computer)
Device type: general purpose
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6
OS details: Linux 2.6.8 - 2.6.27
Network Distance: 1 hop
Service Info: Host: RT-N56U; Device: WAP
This tells me My MAC address (and I can google the first 4 letters there to doublecheck who made it), what I run, and what it actually is - a RT-N56U access point.
In the case of my other AP, there's a bunch of junk data.
MAC Address: C4:A8:1D:84:F3:59 (Unknown)
No exact OS matches for host (If you know what OS is running on it, see http://nmap.org/submit/ ).....
Network Distance: 1 hop
Service Info: OS: Linux; CPE: cpe:/h:dlink:dir-865l:1.07, cpe:/o:linux:linux_kernel
Zenmap can't quite identify what it is, but gives you enough information to ID what it is - look at the service info line. It tells me it runs linux, its a CPE (consumer premises equipment) and its a dlink, dir-865l running firmware 1.07
answered Dec 2 '16 at 1:24
Journeyman Geek♦Journeyman Geek
113k44217371
113k44217371
add a comment |
add a comment |
It’s years old, but it deserves an answer!
First of all: There is absolutely no need to reset anything.
Your Xiaomi router is still reachable at 192.168.31.1. However, to communicate with it, you need to be in the same subnet. Currently, with DHCP from your main router, you’re in the 192.168.178.0/24 network while you want to be in the 192.168.31.0/24 network.
To access your Xiaomi router, manually change your PCs IP address to 192.168.31.2. You will not be able to access the Internet like this, though.
To be able to access your Xiaomi router during normal operation, you need to change its IP address. You could use 192.168.178.2, for example. Just make sure there is no IP address conflict. Preferably, the address would also be outside the DHCP range of your main router.
add a comment |
It’s years old, but it deserves an answer!
First of all: There is absolutely no need to reset anything.
Your Xiaomi router is still reachable at 192.168.31.1. However, to communicate with it, you need to be in the same subnet. Currently, with DHCP from your main router, you’re in the 192.168.178.0/24 network while you want to be in the 192.168.31.0/24 network.
To access your Xiaomi router, manually change your PCs IP address to 192.168.31.2. You will not be able to access the Internet like this, though.
To be able to access your Xiaomi router during normal operation, you need to change its IP address. You could use 192.168.178.2, for example. Just make sure there is no IP address conflict. Preferably, the address would also be outside the DHCP range of your main router.
add a comment |
It’s years old, but it deserves an answer!
First of all: There is absolutely no need to reset anything.
Your Xiaomi router is still reachable at 192.168.31.1. However, to communicate with it, you need to be in the same subnet. Currently, with DHCP from your main router, you’re in the 192.168.178.0/24 network while you want to be in the 192.168.31.0/24 network.
To access your Xiaomi router, manually change your PCs IP address to 192.168.31.2. You will not be able to access the Internet like this, though.
To be able to access your Xiaomi router during normal operation, you need to change its IP address. You could use 192.168.178.2, for example. Just make sure there is no IP address conflict. Preferably, the address would also be outside the DHCP range of your main router.
It’s years old, but it deserves an answer!
First of all: There is absolutely no need to reset anything.
Your Xiaomi router is still reachable at 192.168.31.1. However, to communicate with it, you need to be in the same subnet. Currently, with DHCP from your main router, you’re in the 192.168.178.0/24 network while you want to be in the 192.168.31.0/24 network.
To access your Xiaomi router, manually change your PCs IP address to 192.168.31.2. You will not be able to access the Internet like this, though.
To be able to access your Xiaomi router during normal operation, you need to change its IP address. You could use 192.168.178.2, for example. Just make sure there is no IP address conflict. Preferably, the address would also be outside the DHCP range of your main router.
answered Feb 3 at 16:15
Daniel BDaniel B
34.2k76487
34.2k76487
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1054570%2fwhy-after-setting-up-a-router-as-an-access-point-i-cant-reach-it-anymore%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why did you disable DHCP?
– CharlieRB
Mar 18 '16 at 19:25
I have read it on a guide
– ciaoben
Mar 18 '16 at 19:38
Reading it in a guide doesn't tell me much. Nor does it tell me why the guide is disabling DHCP. Does your "main router" have DHCP enabled? Or is it just a broadband modem provided by your internet company?
– CharlieRB
Mar 18 '16 at 19:43
sorry I know I can't help much! anyway On the main router I have DHCP enabled!
– ciaoben
Mar 18 '16 at 19:46
When you turned off DHCP, you disabled the ability of the router to set IP addresses. They now come from the main router. This explains why you can no longer use
192.168.31.1to access the router. Have you tried to access the router at192.168.178.1?– CharlieRB
Mar 18 '16 at 19:50