A couple of thoughts.
1. Usually if you are given a static ip address by your ISP, you don't put it in manually.
(You case may be different, but unlikely)
Your pppoe connection should just keep getting the static IP address from the ISP (while you pay them)
You could check your assigned ip addresses in winbox, ip address
Is there a dynamic one on the pppoe-out1 (has a d flag)? Does it match your 91.xxx address?
If it does, just disable the static 91.xxx address you have put in.
Note: The above doesn't apply if you have been given a second ip address, or group of addresses.
Though I am doubtful you ordered a full /24 range indicated by the 91.xxx/24,
Commonly ISP's will give you (for money) additional /29 (with 4 IP's) and /28 (with 8 IP's) address ranges.
**********************
2. As per @TheCat12 The default firewall rules and configuration is usually a good start.
If you have a safe place you can setup your mikrotik (eg. Perhaps even just with internet cable disconnected)
Use winbox, perhaps connecting via mac address.
Use files in winbox, and make a backup of your current config.
Then reset to factory defaults (keeping users)
Then when it has reset to factory defaults, use quickset (once only is wise) to change connection type to pppoe (ideally on ether1),
(and adjust ip and dhcp server settings if required)
disable all unwanted ip services
probably disable ip firewall Services sip helper
If you now check interfaces / interface lists, you should have the pppoe-out connection being WAN.
Also ether1 being WAN,
(if you put the pppoe-out on a different port to ether1, I would recommend making that different port a WAN port,
also check that the port is no longer attached to the bridge)
Also check ether1's ip dhcp-client is now disabled.
Note: I have ONCE had an issue where reset to factory defaults on a HapAC2 gave no firewall rules, I tried to reset it multiple times.
Not sure why this happened.
There was a log entry I finally noticed complaining about broken script.
I upgraded to a newer routerOS, and the problem went away.
Things like this are very rare, but you might be lucky![:(]( "Sad")
1. Usually if you are given a static ip address by your ISP, you don't put it in manually.
(You case may be different, but unlikely)
Your pppoe connection should just keep getting the static IP address from the ISP (while you pay them)
You could check your assigned ip addresses in winbox, ip address
Is there a dynamic one on the pppoe-out1 (has a d flag)? Does it match your 91.xxx address?
If it does, just disable the static 91.xxx address you have put in.
Note: The above doesn't apply if you have been given a second ip address, or group of addresses.
Though I am doubtful you ordered a full /24 range indicated by the 91.xxx/24,
Commonly ISP's will give you (for money) additional /29 (with 4 IP's) and /28 (with 8 IP's) address ranges.
**********************
2. As per @TheCat12 The default firewall rules and configuration is usually a good start.
If you have a safe place you can setup your mikrotik (eg. Perhaps even just with internet cable disconnected)
Use winbox, perhaps connecting via mac address.
Use files in winbox, and make a backup of your current config.
Then reset to factory defaults (keeping users)
Then when it has reset to factory defaults, use quickset (once only is wise) to change connection type to pppoe (ideally on ether1),
(and adjust ip and dhcp server settings if required)
disable all unwanted ip services
probably disable ip firewall Services sip helper
If you now check interfaces / interface lists, you should have the pppoe-out connection being WAN.
Also ether1 being WAN,
(if you put the pppoe-out on a different port to ether1, I would recommend making that different port a WAN port,
also check that the port is no longer attached to the bridge)
Also check ether1's ip dhcp-client is now disabled.
Note: I have ONCE had an issue where reset to factory defaults on a HapAC2 gave no firewall rules, I tried to reset it multiple times.
Not sure why this happened.
There was a log entry I finally noticed complaining about broken script.
I upgraded to a newer routerOS, and the problem went away.
Things like this are very rare, but you might be lucky
Statistics: Posted by rplant — Wed Apr 16, 2025 5:05 am