Posts made by Romo

@gjacobse Will be doing this as well, thanks Gene

@dafyre I had only tested from the admin profile but didn't get any screen flashes or blackouts while using screen connect until today, the user left her session open and I remoted in.

I didn't get her blackouts but I did get constant screen flashes that maybe cause the blackouts on her monitors, so that got us thinking that somehow it could a user profile issue. We have deployed the same build to other users and no one else has reported the issue.

So for tomorrow, we have a new local account set for her to test, hopefully, this fixes the issues.

So we have a new computer (ASRock A320M-HDV + AMD A10-9700 RADEON R7, 10 COMPUTE CORES 4C+6G)which was just deployed last friday that keeps getting sudden blackouts. At first those blackouts completely froze the computer, we updated to the lastest driver directly from AMD which fixed the freezing but the user keeps getting the blackouts.

Anyone have any idea what else could be done to fix the issue?

@jaredbusch Would the steps be something like this:

• Change the interface configuration to trust IP DSCP,
• Give IP DSCP 46 (Rtp) a traffic class of 7 (any other thing i'd need to set as a higher traffic class?).
• Choose the Queue management type- Taildrop (default) or WRED (any opinion on which one is better)
• Finally set the Interface Queue Drop Precedence, per interface and per queue (Don't understand this) ?

Don't have any vlan set on the the switches, so probably best bet would be Class of Service->IP DSCP then right?

@dustinb3403 No yet, haven't had access to the switches yet. They do report internal call issues, so thinking maybe setting QoS on the switches might also help.

Has anybody set QoS on the switches? Trying to prioritize VOIP on reported saturated switches. I can see from here https://dl.ubnt.com/guides/edgemax/EdgeSwitch_AdminGuide.pdf#ConfQoS.indd%3AAnchor 1%3A285 the edgeswitches do offersome options but not clear on what works better as I have not done QoS on switches before.

Maybe this helps?

https://git-scm.com/docs/git-filter-branch

To rewrite the repository to look as if foodir/ had been its project root, and discard all other history:

git filter-branch --subdirectory-filter foodir -- --all

Thus you can, e.g., turn a library subdirectory into a repository of its own. Note the -- that separates filter-branch options from revision options, and the --all to rewrite all branches and tags.

Yeah they don't look to similar

@dbeato that's true, hadn't seen that before. Well they changed that as well, older free accounts did have access to IMAP.

@jaredbusch Really? Don't they offer IMAP access?

Still at $3, they are cheaper than the rest on the cheapest plan.

• Amazon Workmail is $4/month

• G Suite is $50/year ($4.16)

• Office 365 -Exchange Online $4/month (annual commitment)

• Zoho Mail $3 ( annual commitment)

The Z is different typography, at least for my eye.

Yes, the phone thing is such a pain.

I think they did, the free plan was also for 25 users and now it back to only 5.

Finished updating a Sage 50 client and troubleshooting why it wouldn't start properly again.

@fateknollogee Free for standalone KVM hosts, this seems interesting. Please share your testing results =).

Finished setting up a vpn from a Watchguard to a Fortinet, on to other tickets

Here is our issue https://wiki.strongswan.org/issues/431, it was fixed 3 years ago when version 5.3 of strongSwan came out.

I had not found what strongSwan version we were using, I just assumed we were using something newer. Then I found that our edge router is using strongSwan 5.2.2.

Here is our version.

Status of IKE charon daemon (strongSwan 5.2.2, Linux 3.10.107-UBNT, mips64):
  uptime: 3 days, since Aug 06 22:12:40 2018
  malloc: sbrk 376832, mmap 0, used 295456, free 81376
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled:

From here https://community.ubnt.com/t5/EdgeMAX-Feature-Requests/Upgrade-to-strongswan-5-6-x/idi-p/1507341 we see a change to strongSwan 5.5.x has been accepted don't know when it will be available.

strongSwan 5.3 + can now handle identical policies by reusing the same reqid. This allows identical CHILD_SAs to the same host.

So that probably means multiple machines behind NAT could also work when the fix is implemented.

@dbeato said in Help troubleshooting L2TP over IPSEC VPN connections.:

@romo said in Help troubleshooting L2TP over IPSEC VPN connections.:

@dbeato Yes

Okay, was looking at that error on other OpenVPN clients that had issues on older versions.

It looks like it is a Strongswan issue, as a temporary fix it should be resolved by manually restarting the IPSec VPN (restart vpn). Unfortunately, during working hours it seems to be too disruptive to use for properly connected users. At least without having tested the effects of the restart for connected users.

The strange thing is the connection is acting as if two computers were trying to access the VPN server behind the same NAT when according to the user it is only a single device.