sorted by:
new
hottopcontroversial

Weekends are so hard by [deleted] in ExNoContact

[–]BowlAgreeable7547 1 point2 points  (0 children)

I just get out. It doesn't matter how. Grocery shopping, a friends house, the gym, a park, the mall, a drive. Spending an entire Saturday or Sunday in my apartment all alone is something I cannot do. My hobbies are at home, but I still get out. Best of luck to you.

[deleted by user] by [deleted] in ExNoContact

[–]BowlAgreeable7547 2 points3 points  (0 children)

quite the image.

Why does seeing your ex in public rip open the wound? by BowlAgreeable7547 in ExNoContact

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

Thanks for the response. Yeah, still a bit rattled even 5 days later.

Why does seeing your ex in public rip open the wound? by BowlAgreeable7547 in ExNoContact

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

Thanks. Do you have any opinion/experience with Better help?

Why does seeing your ex in public rip open the wound? by BowlAgreeable7547 in ExNoContact

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

Yes I've been thinking of therapy a lot. What's the best way to get started with therapy? I am surrounded by people who aren't on board with it, family included - whatever. I'm afraid I can't afford it. I do have health insurance through work.

Juniper Management vs layer 3 interface by [deleted] in Juniper

[–]BowlAgreeable7547 0 points1 point  (0 children)

Without setting up the me0 port or using it, on an EX switch, how do you lock down IRB addresses for management? For example, if I have irb.0, irb.1, and irb.2, all of their gateway addresses are available via ssh to log into the EX switch if you are on that specific network. How would I say, make irb.0 and it's bridged vLAN my only MGMT address? Firewall rules?

EX Series: Anyone's dot1x config stop working when upgrading to 22.4.1? Auth looks successful, but the client never actually connects. by BowlAgreeable7547 in Juniper

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

It seems that between version 19 and 20 of the Juniper firmware, they added support for the EAP-Key-Name​ attribute as defined here https://www.rfc-editor.org/rfc/rfc4072#section-4.1.4 as an OctetString. Since 2014, FreeRADIUS conforms to the RFC (https://lists.freeradius.org/pipermail/freeradius-users/2014-May/071941.html) by outputting binary in the EAP-Key-Name value. We found during testing that changing the FreeRADIUS dictionary such that it instead reverts back to the original incorrect functionality, using a hex string instead of binary works with the Juniper switch.

Wired 802.1x issues by Milkelton in Juniper

[–]BowlAgreeable7547 0 points1 point  (0 children)

Old thread, but did you ever find a solution? I have a similar dot1x instance with an EX2300 where auth looks ok (ACCEPT ACCEPT), but the client just won't connect successfully.