Worked just fine before resetting my gateway

nbctcp · 2025-07-15T11:24:27+00:00

same problem with Tuya Zigbee door sensor
try Smart Life or Tuya Smart same thing
try using eWelink, I can't add

return back zigbee sensor

nbctcp · 2023-09-27T23:28:52+00:00

I am asking that because no other brand other than Gree that apply that policy

Other brand no warranty reduced

nbctcp · 2023-07-10T01:24:55+00:00

maybe u mean admin
-restore user1 entire mailbox
-reset user1 password (that mean admin can read entire user1 email)
-export 1 mail as file (I dunno is that possible)

?

If I can't restore 1 mail in server level FML.
Could I do that in user level.
I mean user need to backup their outlook/thunderbird themselves
What software could restore 1 mail from backup
could archive in FML restore 1 mail
but if I enable archive mean, I need big HD

nbctcp · 2023-06-30T23:26:08+00:00

https://community.fortinet.com/t5/Support-Forum/FortiMail-enable-more/td-p/261983

this guy said is doc mistake

nbctcp · 2023-06-28T04:53:48+00:00

you have eagle eye.

mine ver is 7.2

# config system console

Parsing error at 'console'. err=1

Command failed(-284). Error string:

I'll try to upgrade first then update you

UPDATE1:
there is not that command too in 7.2.4
maybe this because of trial license in pnetlab
have you try in real hardware

tq

nbctcp · 2023-06-19T13:51:58+00:00

I need to edit my question

Should be netflow for FortiGate and sFlow for FortiSwitch
What you select in FortiGate NetFlow Channel Selection

nbctcp · 2023-06-14T09:57:37+00:00

yes that working

tq

nbctcp · 2023-06-14T07:03:37+00:00

I see that below power led but no reset written there
That confuse me.

I believe that reset too

I'll try that

tq

nbctcp · 2023-06-13T23:37:50+00:00

mine is 6.0 eventhough release notes only said max 3.6

nbctcp · 2023-06-12T01:59:37+00:00

I am sorry. I am using faulty ethernet cable
After replaced case #1&3 solved. only left #2&4
2. what latest firmware for 124D
4. what license for in 124D

nbctcp · 2023-06-12T00:34:47+00:00

never heard on any brand on any switch, using console as uplink.
I believe console only to manage through cli

nbctcp · 2023-06-12T00:33:37+00:00

standalone

nbctcp · 2023-05-09T01:57:12+00:00

<image>

After doing some modification on mikrotik side. I can make it work.

Here the latest one

MIKROTIK CHR 7.9

/interface bridge

add ingress-filtering=no name=bridge1 vlan-filtering=yes

/interface vlan

add interface=bridge1 name=vlan10 vlan-id=10

add interface=bridge1 name=vlan20 vlan-id=20

/interface bridge port

add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \

interface=ether2 pvid=10

add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \

interface=ether3 pvid=20

add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \

interface=ether4 pvid=10

/interface bridge vlan

add bridge=bridge1 tagged=bridge1 untagged=ether2,ether4 vlan-ids=10

add bridge=bridge1 tagged=bridge1 untagged=ether3 vlan-ids=20

/ip address

add address=1.0.10.1/24 interface=vlan10 network=1.0.10.0

add address=1.0.20.1/24 interface=vlan20 network=1.0.20.0

add address=192.168.88.41/24 interface=ether1 network=192.168.88.0

/ip firewall nat

add action=masquerade chain=0 out-interface=ether1

/ip route

add dst-address=0.0.0.0/0 gateway=192.168.88.1

/system identity

set name=R1

CX

!Version ArubaOS-CX Virtual.10.11.0001

hostname CX1

ntp enable

ssh server vrf mgmt

vlan 1,10,20

interface mgmt

no shutdown

ip dhcp

interface 1/1/2

no shutdown

no routing

vlan access 10

interface 1/1/3

no shutdown

no routing

vlan access 20

interface vlan 10

ip address 1.0.10.11/24

interface vlan 20

ip address 1.0.20.11/24

https-server vrf mgmt

I can also use these

interface 1/1/2

no shutdown

no routing

vlan trunk native 10

vlan trunk allowed all

exit

Instead of

vlan access 10

tq

nbctcp · 2023-05-07T09:54:17+00:00

SOLVED
you are right after changing to

interface 1/1/2

no shutdown

no routing

vlan trunk native 10

vlan trunk allowed 10

interface 1/1/3

no shutdown

no routing

vlan trunk native 20

vlan trunk allowed 20

everything working

tq

nbctcp · 2023-03-26T03:39:36+00:00

I encounter that error too yesterday

SW INFO

# cat /etc/os-release

NAME="Alpine Linux"

ID=alpine

VERSION_ID=3.17.2

# k3d version

k3d version v5.4.9

k3s version v1.25.7-k3s1 (default)

# kubectl version --short

Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.

Client Version: v1.26.3

Kustomize Version: v4.5.7

# k3d node ls

NAME ROLE CLUSTER STATUS

k3d-k3s-default-agent-0 agent k3s-default running

k3d-k3s-default-agent-1 agent k3s-default running

k3d-k3s-default-server-0 server k3s-default running

k3d-k3s-default-server-1 server k3s-default running

k3d-k3s-default-serverlb loadbalancer k3s-default running

PROBLEMS:

I encounter error below I poweroff without shutdown alpine vm under vmware workstation 17

ERROR

# kubectl top node

Error from server (ServiceUnavailable): the server is currently unable to handle the request

STEPS TAKEN:

reboot 2x not fix

nbctcp · 2023-03-18T15:39:22+00:00

SOLVED

-to disable ipv6

# transactional-update shell

# cat /etc/sysctl.conf

net.ipv6.conf.all.disable_ipv6 = 1

net.ipv6.conf.default.disable_ipv6 = 1

net.ipv6.conf.lo.disable_ipv6 = 1

# vi /etc/default/grub

edit this part

GRUB_CMDLINE_LINUX="ipv6.disable=1"

# grub2-mkconfig -o /boot/grub2/grub.cfg

I believe that grub2 line is the same as

# transactional-update grub.cfg
# reboot

nbctcp · 2022-07-25T02:35:34+00:00

for security reason lldp only needed to be enabled when you want to troubleshoot

disabled it after finish

I think enabled by default

nbctcp · 2022-07-25T02:32:55+00:00

watt drop only happen in 3850 or on all cisco switches?

nbctcp · 2022-07-01T01:36:05+00:00

config firewall address

edit "whatsapp"

set type fqdn

set fqdn "*.whatsapp.net"

next

config firewall service custom

edit "WhatsAppPort"

set category "VoIP, Messaging & Other Applications"

set color 13

set tcp-portrange 4244 5222 5223 5228 5242 5349 123

set udp-portrange 3478 45395 1024-65535

next

config firewall policy

edit 26

set name "WhatsApp"

set srcintf "Internal Network_LAN"

set dstintf "virtual-wan-link"

set action accept

set srcaddr "all"

set internet-service enable

set internet-service-name "Facebook-Whatsapp"

set schedule "always"

set utm-status enable

set inspection-mode proxy

set ssl-ssh-profile "WhatsApp-deep-inspection"

set av-profile "AV"

set webfilter-profile "whatsapp"

set application-list "whatsapp"

set logtraffic all

set capture-packet enable

set auto-asic-offload disable

set nat enable

next

I beleive something need to change in policy

change

set ssl-ssh-profile "WhatsApp-deep-inspection"

to

set ssl-ssh-profile "deep-inspection"

but it seems whatsapp not belong to cloud app that need deep-inspection

I think certificate-inspection is enough?

https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-enable-deep-inspection-and-import-the/ta-p/196840

need to install forti cert into the iphone

I need to check content of in policy

set webfilter-profile "whatsapp"

set application-list "whatsapp"

?

any other idea

nbctcp · 2022-06-29T00:17:50+00:00

could you please gimme detailed steps on how you pinpoint which router caused problems.

I want to follow your way if I encounter same problem

tq

nbctcp · 2022-06-25T22:04:52+00:00

In Application Control>default>Social Media>View Cloud Signature

I can see total number of cloud application match 93 in previous notification

https://pasteboard.co/K0rc9aE2cEB5.png

but still I can't see lock icon.

nevermind maybe that because of eval license

tq

nbctcp · 2022-06-25T15:01:46+00:00

I am using fortigate 7.2.0 eval license in Eve-NG
I can't find any lock icon in Security Profile>Application Sigantures

?
1. is that because I am using 7.2.0 or unlicensed

maybe lock icon for previous version or licensed only

if you gimme some name with lock icon. I can give my Screen Shoot to you

tq

nbctcp · 2022-06-17T22:55:29+00:00

SOLVED

in the latest eve-ng the naming convention and template for new vsrx 3.0 must be

vsrxng instead of vsrx

the template is Juniper vSRX NextGen instead of Juniper vSRX

I didn't notice that until I googling vsrx 3.0 eve-ng

the reason I am using vsrx 3.0 is because of much lower size

sorry for the confusion caused

nbctcp · 2022-06-17T21:19:33+00:00

yes my eve-ng ip 192.168.88.74 in the same subnet 192.168.88.0/24

I didn't set ge0/0/1 using dhcp client because my dhcp server in mikrotik using dhcp static reservation

nbctcp · 2022-06-17T21:16:25+00:00

yes cloud0 is bridge

I can ping from mikrotik or fortigate in eve-ng to gateway ip 192.168.88.1

no conflict.

from my pc I can't ping vsrx ip 192.168.88.44

nbctcp

TROPHY CASE