Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
irfanink
New Contributor

PPPoe Configuration

i have 60E device and i want to configure PPPoE .I have username and password as ISP provide me . and also mention unnumbered IP ( Any ip from Network for Management) but its show me failed and its didn't work 

4 REPLIES 4
ede_pfau
SuperUser
SuperUser

Sorry, this request is below the scope of the forums.

For sure, PPPoE does work, always has. There are not so many parameters you can set, and nearly only 2 you have to: username and password. I would speculate that your problem lies here but that's only speculation: too few information here.

 

Of course, you would need an external modem to interface with the line, in bridge or pass-through mode. We do not know any detail other than that it doesn' work...


Ede

"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
GoDannY

In addition to what Ede said it may be that you have to add a suffix to the user-credentials - like some providers add a number like 0001 to the username string. You might want to research that requirements.

 

Regards,

Daniel 

t_salmi
New Contributor

I have the same problem can someone help us?

 

Sush
New Contributor

I have very similar issue with Fortigate 60E. PPPoE connection from ISP with a static IP on the unnumbered IP field however Fortigate seems to ignore the unnumbered address and just uses the dynamic IP address received during PPP negotiation.

 

During a google search, I found that some people who had this issue were able to get it fixed using the below command set pppoe-unnumbered-negotiate disable

 

However when I set the pppoe-unnumbered-negotiate to disable my PPPoE connection goes to failed state

 

I have raised a P2 ticket with Fortinet and its been 4 days and they are still sitting on the ticket with no resolution. There are lots of threads which report unnumbered IP address issue with PPPoE on fortigate devices going back to 2-3 years. So, I'm guessing Fortinet is not planning on fixing this issue.

Labels
Top Kudoed Authors