New Member

Question

60E-DSL - vDSL IPOE Service Issue

Forum|Forum|7 years ago
December 11, 2018
15 replies
23679 views

https://kb.fortinet.com/kb/documentLink.do?externalID=FD41696

I have been following the above link when trying to connect a 60E-DSL unit running 5.6.7 firmware to the Telstra NBN.

The service is an IPOE/Dynamic one so no username and password. I also have an NBN service at home with another ISP which is also IPOE. I am unable to get the fortigate to connect to the service. I tried testing it with a standard ADSL2 PPPOE service at the office and it works, so I know the DSL port is ok. If I flash the pre-release firmware which is used in the KB above, I can see upload / download line rates, but both ISP services remain offline. Has anyone had any success getting the 60E-DSL unit to talk to a IPOE based VDSL service?

Thanks,

Terry

andy_vickerstaff

New Member

Hey Terry,

The latest firmware 6.0.4 now allows you to select VDSL from the GUI and I have got this to work on a TPG IPoE service setting the IP address as static.

I haven't as yet got this to work for a Telstra service but am looking to try this out again soon.

Have you managed to progress this at all?

Andy

liammasson33

New Member

Nice Post! I appreciate to you for this post. Really you are the best.

SecurityMinded

New Member

Did you ever get to the bottom of the IPoA on the 60E-DSL?

I've just started testing the same setup and cannot get the line to come up and provide an IP address.

The line works fine with the ISP equipment.

terry_jjrAuthor

New Member

I have just patched to 6.0.4 and will take the unit home for testing tonight. I am with AussieBB and they use IPOE as well. Getting the firmware for the DSL units is weird. I cant seem to download it from the support site, I have to wait for the unit to detect it and then get the update via the firewallls firmware update page. Very strange.

I will test with my home isp tonight and see what happens. Thanks

bens

New Member

I have also been attempting to get a FG60E-DSL working on an Optus NBN VDSL2 IPoE service. I am not getting to showtime, but at the same time it hasn't caused my port to lock-down.

I get a reasonable (but not great) sync speed with the original Optus supplied Sagemcom modem (60-80/20-25Mbit on a 100/40 Service) and I get a successful connection from a Netgear DM200 (which is currently in bridge mode connected to the FG60E WAN port). From what I've gathered from Optus my line to the Node is around 500M (which is strange because the node is only 200M away). I believe Optus have possibly set a non-standard profile on the port to improve stability. I'm running the latest available code, 6.0.5, are there any debugs I can run to get any information about the sync process and what might be stopping a successful negotiation? I'm happy to test with any development code if required if it's needed to get more verbose debugging etc, this is not on a production network.

Thanks,

Ben

bens

New Member

I attempted to do some debugging last night but I will either need some more guidance around debug levels/commands available in the GA firmware or I'll need a development version to test with to get anything meaningful. The output was very verbose but during negotiation there is not very much information presented which is relevant.

I used the following debug commands:

# diagnose debug application dsl -1

# diagnose debug enable

The only information I could discern was that the modem was cycling through the following states:

SILENT[512]

HANDSHAKE[768]

FULL_INIT[896]

EXCEPTION[1]

IDLE_REQUEST[255]

A value labelled as "n" also flipped between 278 (when SILENT/EXCEPTION) and 4185 (all other states).

This matches with my previous observations which indicated that the modem was cycling through sync attempts and failing each time.

I also gained access to the DM200 (which is a Lantiq XWAY VRX220 SoC) in Bridge Mode through the Fortigate and found it does not Sync quite as well as the Broadcom chipset used by the Optus Sagemcom, I get the following statistics:

Downstream Speed: 65.12Mbit

Downstream Attenuation: 21.2dB

Downstream SNR: 11.40dB

Upstream Speed: 14.46Mbit

Upstream Attenuation: 25.5dB

Upstream SNR: 12.30dB

I have limited experience with line quality evaluation but I believe the above indicates the line is not the best, but definitely serviceable. I'm not sure which chipset the FG60E-DSL is using, but the fact that the Lantiq seems to have no issues (besides the lower sync speed) seems to indicate a stable negotiation should be possible.

colinvs

New Member

Hi Terry/Ben,

Have you managed to fix the issue? I have a FortiWiFi 60E-DSL running v6.0.5 now and am about to do a cut-over to Telstra NBN so would like to check out whether it's still an issue before going onsite.

Thanks.

Colin

bens

New Member

Hi Colin,

I still have not achieved successful line sync with my device on my service but given others experiences this is likely limited to the quality/condition of my line/service. It does appear that a successful sync is more difficult to achieve than with the other VDSL2 modems I have tried.

All I can confirm is that, when using 6.0.5, the modem did not cause any error conditions/lock-outs on the line/port and that the DHCP lease is successfully negotiated and maintained on the ethernet port when using another VDSL2 device (Netgear DM200) in bridge mode.

Regards,

Ben

Sign up

Login with SSO

Login to the community

Login with SSO