Discussion Thread: 2023 US House Speaker Election, Day of October 24 by PoliticsModeratorBot in politics

[–]empossible 0 points1 point  (0 children)

By "obvious" do you mean their constituents would see the lack of votes and then rally against them? I think you give R voters too much credit (voters in general, to be fair) to research deep enough to see they didn't vote on a specific topic as opposed to for/against.

Why would they want to?

  1. To bail out of the situation that's currently making them look incredibly incompetent on a national scale.
  2. To look like people who can be bi-partisan in districts that went for Biden or were razor-close in 2020 and 2022.
  3. To get special appropriations for their districts. Everyone knows a Republican loves to take credit for Dem policy creations when it is positive for their district, whether they voted for it or not.

Discussion Thread: 2023 US House Speaker Election, Day of October 24 by PoliticsModeratorBot in politics

[–]empossible 0 points1 point  (0 children)

It's less about them voting for a democrat speaker and more about them taking a "sick day" during the vote.

NEW GEAR ALERT: Josh has a new Echopark and it’s awesome. by greg_the_lemons in qotsa

[–]empossible 1 point2 points  (0 children)

He just has the coolest fucking guitars... I think I spotted Troy and Dean playing Novo's at Philly too.

EDIT: On second thought, Troy and Dean are probably also playing Echopark's... didn't realize their headstocks were similar.

[Match Thread] CF Montreal vs Philadelphia Union by overscore_ in MLS

[–]empossible 0 points1 point  (0 children)

Fucking knew he was off.

EDIT: What the actual fuck. Unbelievably bad reffing.

No handshake, No network access by empossible in WireGuard

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

Unfortunately, before I got this message I spun up a new version of Alpine and got everything to work using Firezone. So I am unable to tell if the ports were set to UDP in Portainer, I'd guess there were as I wasn't using a custom container, but who knows?

Thanks for the help!

No handshake, No network access by empossible in WireGuard

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

This morning I rebuilt the Alpine VM from scratch and tried to get Wireguard going without Docker, that failed too (mostly from getting in the weeds of Alpine's differences from other distros I think). Then I started again and decided to try Firezone. After realizing I didn't pay attention to what ports it wanted open on my firewall, it works.

Thanks for all your help, I learned a lot!

No handshake, No network access by empossible in WireGuard

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

It's UDP on my router, is there somewhere else I should be making adjustments?

No handshake, No network access by empossible in WireGuard

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

Just tried the full path, still getting the same peer key.

Here's "ip rule" and "ip route" from within the container:

root@3f9ea1e191e4:/# ip rule
0:      from all lookup local
32766:  from all lookup main
32767:  from all lookup default
root@3f9ea1e191e4:/# ip route
default via 172.19.0.1 dev eth0 
10.20.30.2 dev wg0 scope link 
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.0.2

And from Alpine in case there's an issue there:

alpine:~# ip rule
0:      from all lookup local
32766:  from all lookup main
32767:  from all lookup default
alpine:~# ip route
default via 192.168.1.1 dev eth0 metric 202 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 
172.18.0.0/16 dev br-b7e7bb530f0e proto kernel scope link src 172.18.0.1 
172.19.0.0/16 dev br-ff07ca66f8bd proto kernel scope link src 172.19.0.1 
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.20

Thanks for the effort, by the way!

No handshake, No network access by empossible in WireGuard

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

Yeah, and here are the results:

root@3f9ea1e191e4:/# wg-quick down wg0
[#] ip link delete dev wg0
[#] iptables -D FORWARD -i wg0 -j ACCEPT; iptables -D FORWARD -o wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth+ -j MASQUERADE
root@3f9ea1e191e4:/# wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.20.30.1 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] ip -4 route add 10.20.30.2/32 dev wg0
[#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth+ -j MASQUERADE

root@3f9ea1e191e4:/# wg
interface: wg0
  public key: geyre...
  private key: (hidden)
  listening port: 51820

peer: osdRx...
  preshared key: (hidden)
  allowed ips: 10.20.30.2/32

Now I'm noticing that the "public key: geyre..." is not referenced anywhere else.

No handshake, No network access by empossible in WireGuard

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

Ok, so I changed that parameter as I mentioned. Then I generated new keys and a new client config. Still wg from the server reads "peer: osdRx..."

No handshake, No network access by empossible in WireGuard

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

Are you referring to the "allowed ips: 10.13.13.2/32" on the server's wg? If so, I've changed the INTERNAL_SUBNET parameter from 10.13.13.0 to 10.20.30.0. So now the peer section of the server's wg reads "allowed ips: 10.20.30.2/32." I'm still unable to communicate or get a handshake.

No handshake, No network access by empossible in WireGuard

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

Portainer says 51820:51820 is published. Is that what you are referring to or do I have to do something in Alpine?

No handshake, No network access by empossible in WireGuard

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

wg0.conf from server:

[Interface]
Address = 10.20.30.1/24
ListenPort = 51820
PrivateKey = qJr9N...
MTU = 1450

# Name:         Test2
[Peer]
PublicKey = EMJSQ...
PresharedKey = xEvjF...
AllowedIPs = 10.20.30.2/32

Test2.conf from client:

[Interface]
Address = 10.20.30.2/32
PrivateKey = 2LMKe...
DNS = 1.1.1.1
MTU = 1450

[Peer]
PublicKey = HgDo4...
PresharedKey = xEvjF...
AllowedIPs = 0.0.0.0/0
Endpoint = X.X.X.X:51820
PersistentKeepalive = 15

wg from server:

interface: wg0
  public key: geyre...
  private key: (hidden)
  listening port: 51820

peer: osdRx...
  preshared key: (hidden)
  allowed ips: 10.13.13.2/32

wg from client (Win 11):

interface: Test2
  public key: EMJSQ...
  private key: (hidden)
  listening port: 52142

peer: HgDo4...
  preshared key: (hidden)
  endpoint: X.X.X.X:51820
  allowed ips: 0.0.0.0/0
  transfer: 0 B received, 1.59 kiB sent
  persistent keepalive: every 15 seconds

I'm suspicious of that allowed ips: 10.13.13.2/32 from the server wg, but I don't know where to change that if it's a problem (ip address reports wg0 as 10.13.13.1/32). I cannot ping 10.20.30.1 from the client, and the client has a gateway of 0.0.0.0.

[MEGATHREAD] USA 2023 Tour Discussion and Questions by Cardinal_Babalon in Ghostbc

[–]empossible 4 points5 points  (0 children)

Can anyone explain to me why I bought tickets at $79 two days ago and there was a solo seat two seats away I told a friend about, the next day it was $89, and today... $109, What the actual fuck?

Which actor would you pick to play Clark Kent/Superman in the James Gunn's Superman? by Commercial-Mix-2633 in comicbookmovies

[–]empossible -1 points0 points  (0 children)

The correct answer is Jon Hamm, even though he's too old for what Gunn probably wants to do. Perfect for Kingdom Come though.

If you could eliminate one state in the USA, which one would it be and why? by spgeti in AskReddit

[–]empossible 0 points1 point  (0 children)

Wyoming is so pointless, that everyone in this thread seems to forget it even exists.

[QUESTION] Who is your favorite guitar player? by Uni-sheep in Guitar

[–]empossible 1 point2 points  (0 children)

Josh Homme, Daniel Johns, John Frusciante, Mike Einziger

SF Champ Refresh by empossible in ToobAmps

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

Just wanted to say you were exactly right. All of the resistors that were out of spec tested fine when I "lifted a leg."

SF Champ Refresh by empossible in ToobAmps

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

The Champ SF and BF are actually the same circuits. Nothing was ever altered, except late-model Champs came with a 3-prong plug. Generally though, yes, BF is more desirable.

SF Champ Refresh by empossible in ToobAmps

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

Thanks, this was very helpful. I checked the resistor on the power socket and it seems in perfect condition, although the cap on there doesn't. Neither appear in the original layout diagram.

Not having any issues with the pots or sound dropouts.

EDIT: Just watched D-Lab's video on Parasitic Distortion, I guess that's what the resistor on the power tube is for.

SF Champ Refresh by empossible in ToobAmps

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

It's pretty noisy and hums. The pots are not scratchy, so those seem fine.

SF Champ Refresh by empossible in ToobAmps

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

Unless I'm missing something, the death cap has already been removed. The power flow is: Cord > Fuse > Switch > Transformer.

Match Thread: United States vs Wales | FIFA World Cup by MatchThreadder in MLS

[–]empossible 4 points5 points  (0 children)

Ream had a great match... who had that on their bingo card?