Hi All,
PpoE works fine on Cisco router but doesn't work on Fortigate 60 F, getting below error.
update_interfaces()-423: Update PPPoE interfaces
update_interfaces()-427: Invalidate PPPoE interface wan2
update_interfaces()-427: Invalidate PPPoE interface wan2.7
update_interfaces()-481: Found PPPoE interface wan2
update_interfaces()-563: PPPoE parameters of wan2 unchanged.
update_interfaces()-481: Found PPPoE interface wan2.7
update_interfaces()-563: PPPoE parameters of wan2.7 unchanged.
pppoe_read_intf_link_sock()-406: interface=internal1 event=1
Two suggestions:
1- make absolutely sure you have the password correct (i.e., paste it)
2- some ISPs deliver on a VLAN, that is, tagged. If your modem doesn't remove tags this might be the issue.
Aslo check for other ports and try wan connection.
Hello Siddhanth,
Thank you for your reply
1- Yes, password is correct
2- ISP is tagging on VLAN7 , same VLAN tagging works on Cisco.
Do you see anymore issue? or the only option is to check by changing port ?
Kidzaad.pk is your go-to haven for adorable and trendy kids' garments. Discover a world where fashion meets comfort, designed exclusively for the young ones. From playful patterns to comfortable essentials.
Can you share "show sys int wan2" and "show sys int wan2.7", after masking username/ENC password of course.
Toshi
Hello Toshi, I dont have device access as of now, but below is what I have configured
config system interface
edit "wan2"
set vdom "root"
set mode ppoe
set allowaccess ping https fgfm
set type physical
set role wan
next
edit "wan2.7"
set vdom "root"
set mode pppoe
set allowaccess ping https fgfm
set device-identification enable
set monitor-bandwidth enable
set role wan
set username xxxxxxxxx
set password xxxxxxxx
set interface "wan2"
set vlanid 7
next
end
config router static
edit 11
set dst 0.0.0.0 0.0.0.0
set gateway x.x.x.x
set device wan2.7
next
end
First, remove pppoe from wan2. Only thing you want to configure is changing the default dhcp to static so that it won't pull any IP on the non-tagged interface. Leave the rest unchanged.
VLAN 7 interface seems to be ok.
If it still doesn't work, sniff packets at "wan2.7" if you can see any meaningful traffic. If not, sniff it at "wan2" interface to see if it's actually tagged with VLAN 7. Below is the output on my 40F. All traffic is tagged with VLAN 201 (Lumen).
fg40f-utm (root) # diag sniffer packet wan
interfaces=[wan]
filters=[none]
pcap_lookupnet: wan: no IPv4 address assigned
1.483471 802.1Q vlan#201 P0
1.483484 802.1Q vlan#201 P0
1.483591 802.1Q vlan#201 P0
1.503170 802.1Q vlan#201 P0
1.503255 802.1Q vlan#201 P0
1.555205 802.1Q vlan#201 P0
1.842814 802.1Q vlan#201 P0
1.845574 802.1Q vlan#201 P0
2.410312 802.1Q vlan#201 P0
2.414190 802.1Q vlan#201 P0
2.414276 802.1Q vlan#201 P0
2.414573 802.1Q vlan#201 P0
Toshi
Thanks Toshi, will check this on Monday and let you know
One more thing. PPPoE generally pulls the default route into routing-table. If you DON'T want it but want to use a static route, you need to set "set defaultgw disable" on "wan2.7" interface. But I would suggest removing the static default route first and let PPPoE pull the default GW.
Once you confirmed it's working, you can change it to manipulate the default route(s) with static ones.
Toshi
By the way, the current static route is technically illegal or conflicting with your interface config. If PPPoE, there shouldn't be a static gateway because PPPoE pulls it. Instead it needs to have "set dynamic-gateway enable". That's why I'm suggesting removing it.
Toshi
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1740 | |
1108 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.