11 reputation
2
bio website
location
age
visits member for 7 months
seen Nov 25 at 18:29

Sep
4
comment Routing internet traffic through a site-to-site IPsec tunnel
didn't work. Was able to change the default gateway priority and make everything go through the tunnel but that just ended dropping all traffic. No pings to outside world...
Aug
25
comment Routing internet traffic through a site-to-site IPsec tunnel
checked the routing table, looks like the fortigate has chosen WAN (site A) as the default and therefore isn't sending any packets over the tunnel. Will test and report back. Thanks
Aug
16
comment Routing internet traffic through a site-to-site IPsec tunnel
We did that, packets are going from internal (Site A) --> WAN (Site A), we created a policy to block that specific source computer from going out WAN (Site A), but then the packets would just get blocked, instead of going through the tunnel (internal Site A --> SiteB --> WAN Site B)
Aug
16
asked Routing internet traffic through a site-to-site IPsec tunnel
Jun
16
awarded  Editor
Jun
16
comment Apache SSL redirect loop
original question updated with screenshots and htaccess that caused issue, see lines 2 and 3
Jun
16
revised Apache SSL redirect loop
added 292 characters in body
Jun
16
comment Apache SSL redirect loop
I used the following two lines in the .htaccess i posted above: RewriteCond %{HTTPS} !=on RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L] result was , "This webpage has a redirect loop"
Jun
15
asked Apache SSL redirect loop
May
14
comment configure single /32 ip address to FreeBSD server
We are assigning this to a virtual machine. We have 1 other IP that is a a.b.c.d/26. They stated our other IP's are /32's and we should use the subnet mask 255.255.255.255. They also said "There is no gateway they are /32's. You have to route them back via your host interface."
May
14
awarded  Student
May
14
asked configure single /32 ip address to FreeBSD server