New Member

Question

Invalidate PPPoE interface on WAN2.7

Forum|Forum|2 years ago
September 15, 2023
12 replies
5682 views

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

FortiGate

spoojary

Staff

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.

VikasAuthor

New Member

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 ?

Toshi_Esumi

SuperUser

Can you share "show sys int wan2" and "show sys int wan2.7", after masking username/ENC password of course.

Toshi

VikasAuthor

New Member

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

Toshi_Esumi

SuperUser

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

bcsk

New Member

It seems like there might be an issue with PPPoE configuration on the Fortigate 60F, possibly related to interface settings or credentials. Double-check the configuration to ensure accuracy and try troubleshooting the PPPoE setup.

Tomdanny

New Member

Observe these steps to invalidate a PPPoE interface on WAN2.7:

Access the web interface of your router or other network equipment.
Go to the section for WAN2.7 configuration.
Search the PPPoE settings for a "Disconnect" or "Invalidate" option.
To end the PPPoE connection on WAN2.7, select this option.
When prompted, affirm the activity.

The PPPoE interface can be invalidated to cut off the connection and unplug it from the internet. If you want to troubleshoot or modify the settings on your network's WAN2.7 interface, you might need to do this.

Saad112233

Visitor III

Moreover, your commitment to staying updated with the latest advancements in the AI space is commendable. It's evident that you strive to be a reliable resource for businesses.. isthereaiforthat

Sign up

Login with SSO

Login to the community

Login with SSO