Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: xlr8r on May 08, 2018, 03:56:55 PM
-
ok, i have reads lots on this but yet to find any definitive settings for what i need.
Basically i want my unlocked HG612 to handle the PPPoE connection to BT Infinity on VDSL FTTC and also have my XR500 Netgear router do everything else.
This is to reduce overhead processing on my router. (as in...why not let the modem do some of the work....) ::)
would be grateful for settings if anyone has managed to accomplish this scenario....
thanks
-
Yes, that is do-able but the HG612 is a rather under-powered device once features greater than just a modem-bridge and VLAN end-point are enabled.
-
Yes, that is do-able but the HG612 is a rather under-powered device once features greater than just a modem-bridge and VLAN end-point are enabled.
so... 6 of one, and a half dozen of the other basically....?
so the overheads i would gain on the router , i would lose on the modem...?
-
I would need to login to the device again and see the relevant settings page, but I strongly advise against this.
The Huawei HG612 was locked down in modem only mode for a reason. It just doesn't have the grunt as a router.
When using the HG612 as a modem and only handling the PPP (DHCP, QoS, Firewall all off) I was never able to reach above 60Mb, ever. During heavy usage that would drop frequently to 20Mb.
Your router has a dual core 1.7Ghz CPU.
Why on Earth would you want the HG612 to handle the PPP?
edit: incase you wish to try it
On the left, go to Basic > WAN
Under Port Binding untick LAN 1 and LAN 2
Connection Mode: Route
Connection Type: PPPoE
User name: Your FTTC username
Password: Your FTTC password
from old notes
-
I would need to login to the device again and see the relevant settings page, but I strongly advise against this.
The Huawei HG612 was locked down in modem only mode for a reason. It just doesn't have the grunt as a router.
When using the HG612 as a modem and only handling the PPP (DHCP, QoS, Firewall all off) I was never able to reach above 60Mb, ever. During heavy usage that would drop frequently to 20Mb.
Your router has a dual core 1.7Ghz CPU.
Why on Earth would you want the HG612 to handle the PPP?
edit: incase you wish to try it
On the left, go to Basic > WAN
Under Port Binding untick LAN 1 and LAN 2
Connection Mode: Route
Connection Type: PPPoE
User name: Your FTTC username
Password: Your FTTC password
from old notes
wanted to prove that the XR500 is actually losing 12Mbps by processing PPPoE.
and to test if there was any difference in letting the HG612 handle it instead, just to prove the theory's...
thanks for info will test later and report findings
-
no luck
router couldnt see modem
-
How was the router configured? IPoE or ?
-
How was the router configured? IPoE or ?
thats just it, only options router really offers , Does the internet connection require a login ?
when i choose no, i dont get many options...
(https://s25.postimg.cc/vh383y63z/internet.jpg)
(https://s25.postimg.cc/vspqdi0hr/internet1.jpg)
-
thats just it, only options router really offers , Does the internet connection require a login ?
when i choose no, i dont get many options...
As you have already configured the HG612 to act as the PPPoE client, you should not be configuring the router to do likewise!
Try selecting "No" to the question "Does your Internet connection require a login?" and then see what are the following options further down that page.
Edit -- You have just edited your post whilst I was typing the above . . .
So I would recommend "Get Dynamically from ISP" for "Internet IP Address", "Get Automatically from ISP" for "Domain Name Server (DNS) Address" and "Use Default Address" for "Router MAC Address".
-
As you have already configured the HG612 to act as the PPPoE client, you should not be configuring the router to do likewise!
Try selecting "No" to the question "Does your Internet connection require a login?" and then see what are the following options further down that page.
i posted both images to show settings with yes or no selected.
-
Please go back and look again at my reply, #8, above.
-
There is on other thing to consider . . .
The default IPv4 address of the HG612 is 192.168.1.1 -- that is the address by which you communicate directly to the device, for adjusting its configuration, etc. As a consequence, the XR500 cannot also be configured to use that IPv4 address for its communication channel.
What I am trying to stress is that those two devices (the HG612 & the XR500) must have unique private IPv4 addresses.
-
There is on other thing to consider . . .
The default IPv4 address of the HG612 is 192.168.1.1 -- that is the address by which you communicate directly to the device, for adjusting its configuration, etc. As a consequence, the XR500 cannot also be configured to use that IPv4 address for its communication channel.
What I am trying to stress is that those two devices (the HG612 & the XR500) must have unique private IPv4 addresses.
Hi
currently I have the Xr500 on 192.168.2.1 and the modem on 192.168.2.15
should i be setting the Internet IP address in the router to the ip address of the modem ??
-
I'm not sure exactly what they mean by "the internet IP address in the router" ? Sounds like the outward-facing interface of the router, its WAN address, which no one cares about.
I would say no.
There will need to be somewhere to set the LAN IP address range and the LAN-facing IP address of the router, or else don't set it and get that from the ISP dynamically too, unless that ui option is it already and the terminology is wrong.
-
I'm not sure exactly what they mean by "the internet IP address in the router" ? Sounds like the outward-facing interface of the router, its WAN address, which no one cares about.
I would say no.
There will need to be somewhere to set the LAN IP address range and the LAN-facing IP address of the router, or else don't set it and get that from the ISP dynamically too, unless that ui option is it already and the terminology is wrong.
sorry, forgot to include the LAN settings screenshot earlier...
(https://s25.postimg.cc/7t6kb778f/LAN1.jpg)
-
Can you talk to the internet now if you put the hg612 back to modem-only mode the way god intended?
I agree with J0hn’s advice - it's a bad idea trying to turn the HG612 into a router, let it remain in just modem-only mode. It is doing vastly more work processing DSL and ATM than the router is anyway already.
It should be difficult to get visibility of the modem’s admin web interface through the router. I've just been through this myself. But if you can't ‘see’ the router as in send IP to it and get responses back that doesn't mean that it isn't going to work or that you won't have a working internet connection.
If it is set up anything like my own system then the router talks to the modem using PPPoEoE over ethernet and neither the modem or the router even need to have Ip addresses as you are just asking the modem to export PPP frames carrying who knows what, in fact ‘who knows what’ might not even be IP, and your router and modem are just speaking ethernet to one another, ethernet containing PPPoE containing PPP containing whatever. If the modem or router doesn't even have an ip address on that modem-to-router link then it is if no consequence, PPPoEoE doesn't care and doesn't know about IP. Remember that the router could have (at least) two iP addresses, one for its LAN-facing interface, on your main LAn talking to your computers, and optionally another IP address for the router’s interface on the router-to-modem link. The two addresses, if there are two, are independent of one another, but confusion will probably be caused if they are both in the same overlapping subnet range.
To be able to talk to a modem’s web admin interface a whole lot of things have to be true. Athens modem and router have to have suitable addresses allocated. The router's address on the router-to modem link needs to be in the subnet range that the modem understands (the modem’s config will determine what LAN subnet range it thinks it is living in) otherwise the modem will not know how to reply to incoming requests it receives through the router. The router needs to be set up with a route to the router-to-modem link for whatever admin address you have set on the modem. If not it won't direct your messages intended for the modem’s admin interface to the right place. Getting all of this in place took me quite a bit of fiddling about. [Understatement.]