Level 2: Rookie

Next hop ping test in diagnostics always fails regardless of which new ip is leased.

NBN plan - FTTB

Product Vendor Technicolor
Product Name Technicolor DJA0231
Software Version 18.1.c
Firmware Version 18.1.c.0543-950-RA
Hardware Version VCNT-A
DSL Version A2pvfbH043q.d26u

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
17 REPLIES 17
Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

Attaching here logs from the diagnotics.  Can't get heads or tails with this.  Any help would be greatful.

hu Jan 14 17:11:04 2021 daemon.notice netifd: Interface 'wan6' is enabled
Thu Jan 14 17:11:04 2021 daemon.notice netifd: Interface 'wan' is enabled
Thu Jan 14 17:11:04 2021 daemon.notice netifd: Network device 'ptm0' link is up
Thu Jan 14 17:11:04 2021 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Jan 14 17:11:04 2021 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Jan 14 17:11:04 2021 daemon.notice netifd: Interface 'wan' has link connectivity
Thu Jan 14 17:11:04 2021 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 14 17:11:04 2021 kern.warn kernel: [ 256.371000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:04 2021 kern.warn kernel: [ 256.375000] (SetConnCfg)Created new connection
Thu Jan 14 17:11:04 2021 daemon.err odhcp6c[10936]: Failed to send RS (Cannot assign requested address)
Thu Jan 14 17:11:04 2021 user.notice ethoam: Starting: /usr/bin/tmsctl 1731 start -i ptm0 -a MEG1 -l 2 -m 2
Thu Jan 14 17:11:04 2021 kern.err kernel: [ 256.624000] NComm Ethernet 802.1AG OA&M: loaded Y1731 mode.
Thu Jan 14 17:11:04 2021 user.notice ethoam: Starting: /usr/bin/tmsctl 1731-2 start -i ptm0 -a MEG2 -l 3 -m 3
Thu Jan 14 17:11:04 2021 daemon.notice netifd: wan (10949): Starting in init
Thu Jan 14 17:11:04 2021 kern.warn kernel: [ 256.696000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:04 2021 user.notice ethoam: Starting: /usr/bin/tmsctl 3ah start -i ptm0 -m 2 -f +vr+lb+le+ac -e
Thu Jan 14 17:11:04 2021 kern.warn kernel: [ 256.723000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:04 2021 kern.info kernel: [ 256.748000] NComm Ethernet 802.3AH OA&M loaded.
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.774000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.801000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.847000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.864000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.893000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.920000] (SetConnCfg)Logical portmask[1] Logical PortId[0]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.975000] (CreateNetworkDevice)portmask[1] ulLogicalPort[0]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.975000] (CreateNetworkDevice)m_LogPhyPortmap[0] updated portmask[1]
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.975000] bcmxtmrt: TxPAF Status = Disabled
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.975000] bcmxtmrt: MAC address: a4 91 b1 a9 1d 6c
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.975000] [DoCreateDeviceReq.789]: register_netdev
Thu Jan 14 17:11:05 2021 kern.warn kernel: [ 256.980000] [DoCreateDeviceReq.794]: register_netdev done
Thu Jan 14 17:11:05 2021 user.notice Hotplug: broadcom_wds_script Starting due to action=add devName=ptm0 interface=ptm0
Thu Jan 14 17:11:05 2021 user.notice Hotplug: broadcom_wds_script Not a WDS interface
Thu Jan 14 17:11:05 2021 daemon.err odhcp6c[10936]: Failed to send DHCPV6 message to ff02::1:2 (Cannot assign requested address)
Thu Jan 14 17:11:05 2021 user.notice Hotplug: broadcom_wds_script Starting due to action=add devName=atm_8_35 interface=atm_8_35
Thu Jan 14 17:11:05 2021 user.notice Hotplug: broadcom_wds_script Not a WDS interface
Thu Jan 14 17:11:05 2021 daemon.notice netifd: wan (10949): Switching to selecting
Thu Jan 14 17:11:08 2021 daemon.notice wansensing: (L2Sense) runs L2Main.check(timeout)
Thu Jan 14 17:11:10 2021 daemon.notice wansensing: L2Main.lua: check interface PHY type VDSL
Thu Jan 14 17:11:10 2021 daemon.notice wansensing: L2Main.lua: interface origL3 L3DHCP
Thu Jan 14 17:11:10 2021 daemon.notice wansensing: (L2Sense) runs L2EntryExit.exit(VDSL,L3DHCP)
Thu Jan 14 17:11:10 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPEntryExit.entry(VDSL)
Thu Jan 14 17:11:10 2021 daemon.notice wansensing: The L3DHCP entry script is configuring DHCP on wan and wan6 interface on l2type interface VDSL
Thu Jan 14 17:11:10 2021 daemon.info wansensing.lua[3545]: tcp-ack-mflows not supported
Thu Jan 14 17:11:10 2021 daemon.notice wansensing: Starting supervision ...
Thu Jan 14 17:11:15 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,timeout)
Thu Jan 14 17:11:15 2021 daemon.notice wansensing: The L3DHCP main script is checking link connectivity on l2type interface VDSL
Thu Jan 14 17:11:15 2021 kern.warn kernel: [ 267.344000] dev = ptm0(0xD42C3000) macAddr=A4:91:B1:A9:1D:6C
Thu Jan 14 17:11:15 2021 kern.warn kernel: [ 267.344000] Line0: VCE macAddr=2:19:8F:7B:46:30, VTU-R macAddr=A4:91:B1:A9:1D:6C
Thu Jan 14 17:11:20 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,timeout)
Thu Jan 14 17:11:20 2021 daemon.notice wansensing: The L3DHCP main script is checking link connectivity on l2type interface VDSL
Thu Jan 14 17:11:25 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,timeout)
Thu Jan 14 17:11:25 2021 daemon.notice wansensing: The L3DHCP main script is checking link connectivity on l2type interface VDSL
Thu Jan 14 17:11:30 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPMain.check(VDSL,timeout)
Thu Jan 14 17:11:30 2021 daemon.notice wansensing: The L3DHCP main script is checking link connectivity on l2type interface VDSL
Thu Jan 14 17:11:30 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPEntryExit.exit(VDSL,L3DHCPSense)
Thu Jan 14 17:11:30 2021 daemon.notice wansensing: The L3DHCP exit script is using transition L3DHCPSense using l2type VDSL
Thu Jan 14 17:11:30 2021 daemon.notice wansensing: Stopping supervision ...
Thu Jan 14 17:11:30 2021 daemon.notice wansensing: (L3DHCPSense) runs L3DHCPSenseEntryExit.entry(VDSL)
Thu Jan 14 17:11:30 2021 daemon.notice wansensing: The L3 DHCP Sense entry script is configuring DHCP on l2type interface VDSL
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan6' is now down
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan' is now down
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan' is disabled
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan6' is disabled
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan' has link connectivity
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Network device 'ptm0' link is down
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Thu Jan 14 17:11:30 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss
Thu Jan 14 17:11:30 2021 user.notice pppoe-relay-hotplug: Interface wan6 ifup-failed
Thu Jan 14 17:11:31 2021 user.notice pppoe-relay-hotplug: Interface wan ifup-failed
Thu Jan 14 17:11:31 2021 daemon.warn odhcpd[3609]: A default route is present but there is no public prefix on wl1_1 thus we don't announce a default route!
Thu Jan 14 17:11:31 2021 daemon.info odhcpd[3609]: Using a RA lifetime of 0 seconds on wl1_1
Thu Jan 14 17:11:31 2021 daemon.warn odhcpd[3609]: A default route is present but there is no public prefix on wl0_1 thus we don't announce a default route!
Thu Jan 14 17:11:31 2021 daemon.info odhcpd[3609]: Using a RA lifetime of 0 seconds on wl0_1
Thu Jan 14 17:11:31 2021 daemon.info odhcpd[3609]: Using a RA lifetime of 1800 seconds on br-lan
Thu Jan 14 17:11:31 2021 user.notice ethoam: Stopping: /usr/bin/tmsctl 1731 stop
Thu Jan 14 17:11:31 2021 user.notice ethoam: Stopping: /usr/bin/tmsctl 1731-2 stop
Thu Jan 14 17:11:31 2021 kern.err kernel: [ 283.686000] NComm Ethernet 802.1AG OA&M: unloaded Y1731 mode.
Thu Jan 14 17:11:31 2021 kern.info kernel: [ 283.725000] NComm Ethernet 802.1AG OA&M: NETDEV_UNREGISTER ptm0
Thu Jan 14 17:11:31 2021 user.notice ethoam: Stopping: /usr/bin/tmsctl 3ah stop
Thu Jan 14 17:11:32 2021 kern.info kernel: [ 283.780000] NComm Ethernet 802.3AH OA&M unloaded.
Thu Jan 14 17:11:32 2021 kern.info kernel: [ 283.821000] NComm Ethernet 802.3AH OA&M NETDEV_UNREGISTER ptm0.
Thu Jan 14 17:11:32 2021 user.notice ethoam: Stopping: /usr/bin/tmsctl 1ag stop
Thu Jan 14 17:11:32 2021 user.notice ethoam: Stopping: /usr/bin/tmsctl 1ag-2 stop
Thu Jan 14 17:11:32 2021 kern.info kernel: [ 283.921000] NComm TMS V6.86 Kernel Module unloaded.
Thu Jan 14 17:11:32 2021 daemon.info intercept[1817]: Removing intercept reason: "wan_down"
Thu Jan 14 17:11:32 2021 daemon.debug intercept[1817]: Already configured. Skipping "stop"
Thu Jan 14 17:11:33 2021 daemon.notice netifd: Interface 'wan6' is enabled
Thu Jan 14 17:11:33 2021 daemon.notice netifd: Interface 'wan' is enabled
Thu Jan 14 17:11:33 2021 daemon.notice netifd: Network device 'ptm0' link is up
Thu Jan 14 17:11:33 2021 daemon.notice netifd: Interface 'wan6' has link connectivity
Thu Jan 14 17:11:33 2021 daemon.notice netifd: Interface 'wan6' is setting up now
Thu Jan 14 17:11:33 2021 daemon.notice netifd: Interface 'wan' has link connectivity
Thu Jan 14 17:11:33 2021 daemon.notice netifd: Interface 'wan' is setting up now
Thu Jan 14 17:11:33 2021 daemon.notice netifd: wan (11503): Starting in init
Thu Jan 14 17:11:33 2021 daemon.err odhcp6c[11502]: Failed to send RS (Cannot assign requested address)
Thu Jan 14 17:11:33 2021 user.notice ethoam: Starting tmsctl
Thu Jan 14 17:11:33 2021 kern.info kernel: [ 285.242000] NComm TMS V6.86 Kernel Module loaded.
Thu Jan 14 17:11:33 2021 user.notice ethoam: Starting: /usr/bin/tmsctl 1731 start -i ptm0 -a MEG1 -l 2 -m 2
Thu Jan 14 17:11:33 2021 kern.err kernel: [ 285.262000] NComm Ethernet 802.1AG OA&M: loaded Y1731 mode.
Thu Jan 14 17:11:33 2021 daemon.info wansensing.lua[3545]: All TMS 1731 setup calls completed Successfully.
Thu Jan 14 17:11:33 2021 user.notice ethoam: Starting: /usr/bin/tmsctl 1731-2 start -i ptm0 -a MEG2 -l 3 -m 3
Thu Jan 14 17:11:33 2021 daemon.info wansensing.lua[3545]: All TMS 1731 setup calls completed Successfully.
Thu Jan 14 17:11:33 2021 user.notice ethoam: Starting: /usr/bin/tmsctl 3ah start -i ptm0 -m 2 -f +vr+lb+le+ac -e
Thu Jan 14 17:11:33 2021 kern.info kernel: [ 285.336000] NComm Ethernet 802.3AH OA&M loaded.
Thu Jan 14 17:11:33 2021 daemon.info wansensing.lua[3545]: All TMS 3AH setup calls completed Successfully.
Thu Jan 14 17:11:33 2021 user.notice ethoam: Stopping: /usr/bin/tmsctl 1ag stop
Thu Jan 14 17:11:33 2021 user.notice ethoam: Stopping: /usr/bin/tmsctl 1ag-2 stop
Thu Jan 14 17:11:33 2021 daemon.info wansensing.lua[3545]: tcp-ack-mflows not supported
Thu Jan 14 17:11:33 2021 daemon.err odhcp6c[11502]: Failed to send DHCPV6 message to ff02::1:2 (Cannot assign requested address)
Thu Jan 14 17:11:34 2021 daemon.notice netifd: wan (11503): Switching to selecting
Thu Jan 14 17:11:34 2021 daemon.err odhcp6c[11502]: Failed to send DHCPV6 message to ff02::1:2 (Cannot assign requested address)
Thu Jan 14 17:11:37 2021 daemon.notice netifd: wan (11503): Switching to requesting (server 58.162.26.65 offered ip 58.168.67.205)
Thu Jan 14 17:11:38 2021 daemon.notice netifd: wan (11503): Switching to bound; server 58.162.26.65 assigned ip 58.168.67.205 (leasetime 3598 T1 1798 T2 3148)
Thu Jan 14 17:11:38 2021 daemon.notice netifd: Interface 'wan' is now up
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: reading /tmp/resolv.conf.auto
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: reading /tmp/resolv.conf.auto
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain test
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain test
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain onion
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain localhost
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain local
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain invalid
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain example.net
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain example.org
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using local addresses only for domain example.com
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using nameserver 2001:8004:0:180:7:e1c0:0:11#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using nameserver 2001:8004:0:a080:7:e1c0:0:10#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using nameserver 61.9.194.49#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using nameserver 61.9.195.193#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10325]: using 3 more local addresses
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain onion
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain localhost
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain local
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain invalid
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain example.net
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain example.org
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using local addresses only for domain example.com
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using nameserver 2001:8004:0:180:7:e1c0:0:11#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using nameserver 2001:8004:0:a080:7:e1c0:0:10#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using nameserver 61.9.194.49#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using nameserver 61.9.195.193#53 [0]
Thu Jan 14 17:11:38 2021 daemon.info dnsmasq[10324]: using 3 more local addresses
Thu Jan 14 17:11:39 2021 daemon.notice wansensing: (L3DHCPSense) runs L3DHCPSenseMain.check(VDSL,timeout)
Thu Jan 14 17:11:39 2021 daemon.notice wansensing: The L3 DHCP Sense script is sensing DHCP on l2type interface VDSL
Thu Jan 14 17:11:39 2021 daemon.notice wansensing: The L3 DHCP Sense script sensed DHCP on l2type interface VDSL
Thu Jan 14 17:11:39 2021 daemon.notice wansensing: (L3DHCPSense) runs L3DHCPSenseEntryExit.exit(VDSL,L3DHCP)
Thu Jan 14 17:11:39 2021 daemon.notice wansensing: The L3 DHCP Sense exit script is using transition L3DHCP using l2type VDSL
Thu Jan 14 17:11:39 2021 daemon.notice wansensing: (L3DHCP) runs L3DHCPEntryExit.entry(VDSL)
Thu Jan 14 17:11:39 2021 daemon.notice wansensing: The L3DHCP entry script is configuring DHCP on wan and wan6 interface on l2type interface VDSL
Thu Jan 14 17:11:39 2021 daemon.info wansensing.lua[3545]: tcp-ack-mflows not supported
Thu Jan 14 17:11:39 2021 user.notice firewall: Reloading firewall due to ifup of wan (ptm0)
Thu Jan 14 17:11:39 2021 daemon.warn odhcpd[3609]: A default route is present but there is no public prefix on wl1_1 thus we don't announce a default route!
Thu Jan 14 17:11:39 2021 daemon.info odhcpd[3609]: Using a RA lifetime of 0 seconds on wl1_1
Thu Jan 14 17:11:39 2021 daemon.warn odhcpd[3609]: A default route is present but there is no public prefix on wl0_1 thus we don't announce a default route!


Level 21: Augmented
Level 21: Augmented

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

Hi - do you mean Traceroute in the Diagnostics/Network Tools which shows all elements of the connection path for external IP addresses or web sites for Destination Hosts entries. Can you use the same commands successfully in a CMD window on your PC and are you using only one modem in your network.

Level 24: Supreme Being
Level 24: Supreme Being

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

Is this what you see on the Diagnostics > Connection tab or do you also have next hop ping fails? If yours

 

 58.1xx.xx.xx
 2001:8003xx:xx:xx:xx
 Success
 Not all pings were answered or not connected
 Not all pings were answered or not connected
 Not all pings were answered or not connected
 Not all pings were answered or not connected
 Not all pings were answered or not connected
 
If you have next hop ping fails and the phone works NBN has probably configured your connection as voice only.
Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

Attaching here screenshots of my modem

Level 24: Supreme Being
Level 24: Supreme Being

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

It looks like Telstra has not programed your connection correctly. The IPv4 address is a Telstra IP address, there should also be an IPv6 address. If you disconnect DSL port and wait about 3 minutes do you have internet access?

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

I tried that too, and still no IPV6 and no internet access.

Level 24: Supreme Being
Level 24: Supreme Being

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

Either Telstra has programmed your connection incorrectly or the modem is faulty. Is Telstra doing anything to rectify the problem? 

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

When I called their 13 39 33 (given by  the marketing person on twitter '@telstra') ,  I'm on hold for 40 mins now on the call. The IVR said they have a ticket number. 

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

I'm also inclined to think that the routing profile associated to my PPP credentials are not in order on Telstra's app servers.  Because everytime I try to restart  and get a new ip either a 101.x.x.x or 52.x.x.x , still has no IPV6 included.

Level 24: Supreme Being
Level 24: Supreme Being

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

Have you tried using the messaging function in the get help section of the My Telstra app or online at Telstra - Internet - Contact us

Leave a message thar you wished to be contacted by a consultant. This fault can only be fixed by Telstra and at the moment they don't seem to be doing anything.

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

Yes, I have left them a message via those methods and still waiting.

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

quick update:  After 4 days of no NBN internet , and troubleshooting with  Telstra support via chat, and running on the 4G backup mode(just remove the vdsl cable and the smartmode gen2 will switch to 4G backup mode) , little did I know it had a 15GB data limit, and I ran out of it on day3. 

 

Now ,  I have asked Telstra support to reinstate my 4G backup mode and according to them, I can always ask for this unthrottling should the 15GB data run out.   I am now scheduled to have a Telstra technician to come on monday 18-01.  

Will keep posting updates.

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

 

Posting here for proof of understanding with Telstra as to where the fault will be found.

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

update:  Telstra engineer came found no errors with the NBN line as he did a SYNC test.   Replace the modem with another one  with these specs:   Arcadyan LH1000 .

Plugged in in the wall socket still with the default PPP credentials  newdsluser@bigpond.com

 

IPV4 and IPV6 is now present , but the speed is throttled to bps.  Can only do ping.

 

Calling Telstra to remove the throttle.

 

 

Level 2: Rookie

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

day6:   
Still no internet on the fixed line(i.e. NBN50) . 
Can only do ping.   
Still running on 4G backup mode as needed. 
No support help yet via MyTelstraApp.
Unable to call 13 39 33.   
Got an SMS from Telstra saying NBN is performing upgrades in this area. Nevertheless, the speed should not be dropped like this.  It is as if there is a firewall on the other end of the modem at the Telstra/NBN side.

At least I got a new modem from the technician, where the front lights are working (white,  orange, blue, green).

Level 25: The Singularity
Level 25: The Singularity

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

You shouldn't be using the default PPP credentials (they won't work). You need to enter in your credentials.

Never be afraid to back yourself when trying new things, just always make sure you have 3 escape routes if things go wrong.
Level 24: Supreme Being
Level 24: Supreme Being

Re: Next hop ping test in diagnostics always fails regardless of which new ip is leased.

The connection type is an NBN connection. Should work with the default PPP credentials. On the Broadband settings page what does it show as the current mode? Should be IPoVDSL routed mode. Similar to image below.

Set it & forget it

With direct debit there’s no need to give paying your bill another thought.

Avoid queuing up and never worry about late fees again.

Setup direct debit