Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roseway]

As it happens, a project has just been started to set up a wiki page on the use of the HG612 on a Talk Talk connection, and your O2 information will be a valuable extension to that.

[biohead]

What I found when using my HG612 on a Talktalk connection - man that thing was stable. I live on a longish line (3km+) and it wouldn't be unheard of for an ADSL modem to drop the connection through the night. It was very rare one would hold sync for two nights in a row.

I ran the 612 for a little under a month, and in that time I had 1 dropout. And I've a feeling that one dropout was a cause of me ordering the FTTC install as it occurred shortly after I ordered it.

Regarding my own fttc install, I will swap the ECI for my 612 at some point... it's just a bit too new to start doing that yet 

[LeJimster]

The HG612 is very good indeed at keeping synced.  But it's no different to my ADSL2+ router that I had been using before.  I think the key is the Broadcom chipset and software..  They nailed it with the BCM6348 and since the HG612 uses a faster revision of the same chipset (BCM6368 i believe)..  It's kept all those great features.  I certainly wouldn't have bought it if it had something other than the Broadcom inside it.

[ColinS]

Hello everyone    I too have acquired and unlocked an HG612, primarily to keep a better eye on noise on my BE ADSL2+ line, before I move to Infinity2.
However, I seem to have another issue with DHCP in the box. My HG612 is configured exactly as per the screenshots shown on this thread.  However, it just won't issue an IP address from the pool, and I don't know why.  Monitored the direct connection with Wireshark: the laptop sends out the expected DHCP discoveries, but from the HG612 there is no answer, until it switches to APIPA, then the HG612 does reply.
What's (not) going on?  Can anybody point me in the right direction? (NB: tried different laptops too).
TIA

[burakkucat]

What's (not) going on?  Can anybody point me in the right direction? (NB: tried different laptops too).

Hello Colin, welcome to the Kitz Forum.

I am using a HG612 as a two-port modem/router on my TalkTalk LLU'd line. I have just checked and DHCP is working correctly, for me.

With a statically assigned IP address.

[b*cat@Duo2 ~]$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr A4:BA:DB:C1:20:9E 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a6ba:dbff:fec1:209e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51622 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36403 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:66200744 (63.1 MiB)  TX bytes:4092216 (3.9 MiB)
          Interrupt:16

With a dynamically assigned address.

[b*cat@Duo2 ~]$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr A4:BA:DB:C1:20:9E 
          inet addr:192.168.1.64  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a6ba:dbff:fec1:209e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51650 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36438 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:66211403 (63.1 MiB)  TX bytes:4095635 (3.9 MiB)
          Interrupt:16

Please take a look at the Huawei EchoLife HG612 Home Gateway article in the Kitz Wiki. There you will see a succession of screenshots from my connection. As development of that article is currently ongoing, there are not that many words to be read . . .

On the subject of keeping in-sync, I can confirm that the HG612 has the tendency to "hang on". I have witnessed a SNRM of -1.9 on two separate occasions and it was only at -2 SNRM did the device finally "let go". 

[LeJimster]

I've just checked DHCP with the exact settings in the screenshot and I agree it works fine.  Have you got the device type set to computer on the LAN (DHCP Settings) page?  I don't know if that makes any difference having it set to other devices.

Another thing... If you are using a laptop I presume you are using wireless?  If thats the case, I would be looking at your access point and not the HG612.

[burakkucat]

I've just checked DHCP with the exact settings in the screenshot and I agree it works fine.

 

[ColinS]

Thanks B*K. LeJim, both for the welcome and the helpful advice.  I will go back (yet again) & recheck everything, but it's still bugging me for the moment.  To clarify, in case my poor description is misleading you all:
1) for these testing purposes, I am using a direct ethernet cable from the laptop nic to the HG612 Lan2 (or Lan1 for that matter). No wireless involved.
2) the ADSL2+ link Static IP works absolutely fine.  No DHCP involved on that side for me
3) it's just on the LAN client side that (at the moment) it won't assign an address from the pool.  Darned if I know why yet.
4) I don't want to admit it to myself, but I could swear it used to work (and of course I haven't changed anything ), now it doesn't.  I have tried resetting it back to defaults and 'rebuilding' it, but obviously I must be making the same mistake.
Must try harder - will go back to the drawing board and report back.
Thank you all for making me feel welcome.
Colin

[burakkucat]

No wireless involved.

I should hope not. Otherwise you have a very rare and totally unique Huawei EchoLife HG612 Home Gateway! 

If I am reading your clarification correctly, when your PC or laptop is connected to the HG612 using a statically assigned IP address all is well. When you attempt to connect your PC or laptop, configured as a DHCP client, to the HG612 (which is running as a DHCP server) the connection does not take place.

Assuming that you have the HG612 configured as shown on the LAN Settings page, then the problem must be with the configuration of your PC or laptop.

Perhaps if you go to sleep with that thought in you mind, when you next wake the solution might be "just there"? 

[roseway]

There is a difference betweem LeJimster's DHCP settings and B*Cat's, though I don't know if it's relevant. In the middle of the DHCP server settings, the device type is set differently, and the IP address range below that line is set to 0.0.0.0 in B*cat's version.

[ColinS]

Thanks to both B*K, and Roseway.
Roseway, I spotted that difference too, as well as some apparent differences in the makeup of the screenshots between the two (perhaps SP06 I don't know?). However, as per your hint, I have tried it both with a 'secondary pool' range for specific device types i.e. computer, and without.  For the moment it still seems deaf!
B*K: of course I am inclined to believe you are right, but a) I get the same effect with a different PC using a different version of the OS (which I won't mention) and b) using either PC, but a different router (in this case the TG784), its DHCP works.  So, it's certainly puzzling!
B*K, for comparison with your helpful info (BTW I have the HG612 v3B with the ASBOs SP10 firmware), here's mine:
br0       Link encap:Ethernet  HWaddr BC:76:70:B6:9F:11
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6039 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3647 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:750715 (733.1 KiB)  TX bytes:978758 (955.8 KiB)

eth0      Link encap:Ethernet  HWaddr BC:76:70:B6:9F:11
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6049 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3636 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:862893 (842.6 KiB)  TX bytes:1001500 (978.0 KiB)
          Interrupt:40 Base address:0x6a00

And that's even with the static IP address (actually 192.168.1.2) obviously or a) there would be no traffic, and b) I couldn't get this info!!!!
I will try to capture some screenshots and the Wireshark trace and post them, but before I do, let's see if I am doing something really obviously stupid and invalid in my tests:
I'm 'bench-testing' this (DHCP issue), so I haven't bothered to connect up the ADSL as I know that works and, well, ADSL has to be down sometimes and the modem still work!!
While I (hope) I have faithfully followed the given instructions, apart from unbinding LAN1 from the ptm I haven't 'deleted' any of the default VDSL stuff.  Is that necessary?!!
Thanks to all for their patience while I get myself sorted out on this.

[ColinS]

OK, thank you everyone.  I have it sorted now (at least for the moment).  On the principle of "what's the very least I need to do to make this work?", I:
1) reflashed the HG612 with Asbo's unlocked SP10 firmware
2) reset the configuration data in the modem todefaults
3) ticked enable on DHCP server on the Basic/LAN page
4) set my NIC to use DHCP
and voila, it works.
Now I'll carefully reintroduce the ADSL2+ EoIPoA data needed for Be, ad hopefully that's the end of this story.
Next steps are to put the TG784 configured as to use an Ethernet WAN in place of my laptop, and see if that works along the lines of the way BT's HH3 does.

[LeJimster]

Lol, even with my guide, it seems like it can still be a big pain in the ass. GL getting it to work .

[burakkucat]

Lol, even with my guide, it seems like it can still be a big pain in the ass.

 

[burakkucat]

OK, thank you everyone.  I have it sorted now (at least for the moment).  On the principle of "what's the very least I need to do to make this work?", I:
1) reflashed the HG612 with Asbo's unlocked SP10 firmware
2) reset the configuration data in the modem todefaults

A five-second-plus push of the Reset button would have got you back to that state a lot quicker.    But I guess you wanted to be sure.

3) ticked enable on DHCP server on the Basic/LAN page
4) set my NIC to use DHCP
and voila, it works.

That is good to know.  :clap2:

Now I'll carefully reintroduce the ADSL2+ EoIPoA data needed for Be, ad hopefully that's the end of this story.

Hopefully all will go well.

Next steps are to put the TG784 configured as to use an Ethernet WAN in place of my laptop, and see if that works along the lines of the way BT's HH3 does.

Erm . . . If you are going to do that, then you do not want to configure the HG612 as a DHCP server,    you need to have it in bridged mode and use the TG784 as the DHCP server. A DHCP server after a DHCP server will put you in a double NAT situation.