I've setup a DHCP server pool to provide 10.0.1/24 and 10.0.4/24 on one
of my interfaces. But I can't get an IP on one of my hosts! I see that
the requests leaves the host and (something) is received by my Fortigate
running "FortiOS v5.6.6 build1630 ...
I have a FG50 (FortiOS v5.4) as my home firewall/gateway/nat as well as
IPSEC VPN endpoint to get access to my home network. The VPN works fine
and all, but on the client (macOS Sierra), I don't get a route "in" to
the VPN. I always have to add that ...
I'd like to connect to my FortiGate 50E at home from work and access all
my resources at home. I've managed to get my OSX laptop to connect and
authenticate properly, but I don't get a route on the laptop, nor is
there a DNS server added. I've recent...
What do you mean by "the same broadcast domain with the primary"? But
even if I delete all but the 10.0.4/24 server entry, still doesn't work.
Same as before - dhclient asks and FGT still receives the request but
doesn't respond to it.
Setting up VLANs on Linux is always such a pain! But even if I did that,
I "only" need it to do PXE boots, and there's no way to setup VLANs in
the firmware of my ancient HP machines.
"a bug in the early firmware versions of MR3".. ? What does MR3 stand
for? I'm running version FGT50E-5.6.6-FW-build1630-180913, and that bug
seems to be in that version. There's apparently no newer version than
that (don't want to go to v6 just yet)...
Does anyone have any other ideas on how I can have my FortiGate publish
(?) the/a route to my internal networks to my (OSX) client? I've tried
both the "set add-route phase1" and "set add-route enable" in both my
phase1-interface and phase2-interface...
