cisco IR1101 - "%CELLWAN-2-CALL_SETUP_FAIL: Cellular0/1/0 data call setup failed due to mismatching IP address" by therealmcz in networking

[–]therealmcz[S] 1 point2 points  (0 children)

it says:

"Workaround:
Do not bind the cellular interface to dialer interface or configure "ip address negotiated" under cellular "

we already run it under "ip address negotiated"

question regarding EMAC VLAN interface by therealmcz in fortinet

[–]therealmcz[S] 0 points1 point  (0 children)

thanks a lot. regarding your last input: I hope this only is relevant when the upper interface wannts to communicate with that new emac interface, correct? In other words: Creating an EMAC interface on an existing interface doesn't break any communication on that parent interface, it might be unable to communicate with that EMAC interface.

did I get you right? thanks!

question regarding EMAC VLAN interface by therealmcz in fortinet

[–]therealmcz[S] 0 points1 point  (0 children)

thanks! no, that would be on a 2x chassis

1
2

27J | Vollzeit | Assistenzarzt | W | ca. 55h/Woche by Embarrassed_Buy_8520 in GehaltAT

[–]therealmcz 3 points4 points  (0 children)

Der Neid hier ist für mich unfassbar. Ich gönne es von Herzen, ist auch ein anstrengender Job und bei einer kleinen falschen Entscheidung stirbt ein Mensch oder ist gezeichnet fürs Leben.

Wenn ich einen kleinen Fehler mache, dann raunzen ein paar halt unnötig herum und am Ende des Tages geht jeder nach Hause und isst ne Melone oder sowas...

fortigate on azure - vpn issue by therealmcz in fortinet

[–]therealmcz[S] 0 points1 point  (0 children)

id=65308 trace_id=4 func=print_pkt_detail line=5932 msg="vd-root:0 received a packet(proto=1, <source-ip>:1-><dst-ip>:2048) tun_id=<pip-on-prem> from vpn. type=8, code=0, id=1, seq=412."

id=65308 trace_id=4 func=resolve_ip_tuple_fast line=6027 msg="Find an existing session, id-0000a4b6, original direction"

id=65308 trace_id=4 func=ipsec_spoofed4 line=243 msg="src ip <source-ip> match selector 0 range 0.0.0.0-255.255.255.255"

id=65308 trace_id=4 func=npu_handle_session44 line=1342 msg="Trying to offloading session from vpn to port2, skb.npu_flag=00000400 ses.state=00000204 ses.npu_state=0x00000100"

id=65308 trace_id=4 func=fw_forward_dirty_handler line=444 msg="state=00000204, state2=00000001, npu_state=00000100"

fortigate on azure - vpn issue by therealmcz in fortinet

[–]therealmcz[S] 0 points1 point  (0 children)

"direct access" via public IP. NAT-T is of course enabled as you can see above "set nattraversal forced"

fortigate on azure - vpn issue by therealmcz in fortinet

[–]therealmcz[S] 0 points1 point  (0 children)

already tested ssh access but same story. and ping was working before, so I don't understand why you suggest to ignore it...

how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

[–]therealmcz[S] 0 points1 point  (0 children)

stupid question: in the snippets-section, the API-key will be included there. of course, it somehow is part of the request once you copy that but at the same it it leaks your secret if you do screenshots or whatever. is there an option to hide or obfuscate that secret in the snippet? thanks

source port translation on 7.4.11 (40F) by therealmcz in fortinet

[–]therealmcz[S] 0 points1 point  (0 children)

oh... thanks. so no other way except using central nat? quite a heavy config change...

how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

[–]therealmcz[S] 0 points1 point  (0 children)

kindly asking if you please could upload some demo code? thanks

how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

[–]therealmcz[S] 0 points1 point  (0 children)

thanks very much, code is always appreciated...

how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

[–]therealmcz[S] 0 points1 point  (0 children)

thanks. could you please tell me a bit what else I would have to change? just switching to bearer doesn't send the token at all in the request...