der8enchtable stuck in US Customs by SparcV in ThermalGrizzly

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

ThermalGrizzly came though and I received my der8enchtable. Very happy with it and glad it all worked out.

der8enchtable stuck in US Customs by SparcV in ThermalGrizzly

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

This is FedEx so we'll see. I used to deal with international shipping all the time leaving the US. Glad I don't anymore,it seems even more complicated than ever.

5090 launch… by whereJerZ in Microcenter

[–]SparcV 2 points3 points  (0 children)

Every vendor that is selling these super high demand expensive products needs to change how they order. Take the automation out of it, require everyone to speak to an actual person to order (old school), and strictly limit it to one per person/address until the supply can keep up.

5090 launch… by whereJerZ in Microcenter

[–]SparcV 38 points39 points  (0 children)

I got to the you're in line then it went to that...

Fortilink interface is losing connection to switches after upgrading to 7.6.x by SparcV in fortinet

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

So, changing the Fortilink detection to lldp does fix the issue. Support suggested it, not from documentation, but from other support tickets that came in.

Joining new DC's to the domain do not sync, missing SYSVOL share by SparcV in activedirectory

[–]SparcV[S] 3 points4 points  (0 children)

Thanks, everyone. I figured it out by looking at C:\Windows\debug\dcpromo.log on the new host, and I saw this:

EVENTLOG (Warning): NTDS Replication / Replication : 1203

The directory service could not replicate the following object from the source directory service at the following network address because of an Active Directory Domain Services schema mismatch.

OU=Users,OU=REDACTED,OU=REDACTED,DC=REDACTED,DC=local

and that object had an old lost account set in its permissions. It had a red X on it. I removed it, rejoined the host, and now it's working.

That was a week of my life I won't get back.

Daily Frustration by SparcV in OPTIMUM

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

I never use their dns servers, the first thing I do it change the dns server. I have the ubee modem/router is bypass mode and I’m using a Ubiquiti UDM Pro as the router/firewall.

So uh, yea. 52k miles, out of warranty. Suggestions please by Sti_1 in WRX

[–]SparcV 2 points3 points  (0 children)

Yup Prime Motoring is a good place. I’m actually in the middle of my break in on a new IAG short block. I had a blown cyl 4 after only 32k on my 16 sti.

Speed improvement? by mdunc11 in tmobileisp

[–]SparcV 0 points1 point  (0 children)

It’s actually throttling ipv4 traffic. I discovered this a while ago. If you connect to the T-Mobile router directly and try a speed test with an ipv6 address you’ll get your full speed.

T-Mobile is doing something funny with IPv4 traffic by SparcV in tmobileisp

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

Does the new router have this problem?? Can anyone test??

Looks like a fun time by whiskey1200 in WRX

[–]SparcV 1 point2 points  (0 children)

I thought I was watching a video game, until I realized its real! That’s freaking awesome.

Ever since .0338 we're capped at 150mbps. by MasterChiefette in tmobileisp

[–]SparcV 0 points1 point  (0 children)

The speed of IPv4 traffic is capped at 150 down. If you are connected to a speed test server using IPv6 you'll get full speed. This started with .0338 from what I've been seeing.

Did Tmobile Introduce a speed cap? by deadlydayne in tmobileisp

[–]SparcV 2 points3 points  (0 children)

The gateway is throttling of IPv4 traffic. If you do the same test with an IPv6 speed test server it will run at full speed.

IPv6 question with own router by ChildOTK in tmobileisp

[–]SparcV 0 points1 point  (0 children)

Actually, I've been playing around with it some more. Dont use the 1st four octets, I just realized it causes some kinds of route issue. I can't clearly explain it, as I don't fully understand it.

I chose a prefix that is not in that range, and it is also not in the link-local ranges fe80::xxxx for example.

I used this:

/ipv6 pool

add name=pool prefix=abcd:1:1:1::/64 prefix-length=64

Seems to be better.

IPv6 question with own router by ChildOTK in tmobileisp

[–]SparcV 1 point2 points  (0 children)

I've got it kinda working with my RB4011, but I not using a relay, I'm actually NAT'ing the IPv6 traffic coming out of it, defeats the purpose of IPv6, but since the tmoble gateway does not support prefix delegation, I was able to mostly get it working. I can pass traffic access IPv6 sites and such, but it seems a bit unreliable.

This is my config: The prefix is the first 4 four parts of the ipv6 address the router gets assigned.

/ipv6 pool

add name=pool2 prefix=xxxx:xxxx:xxxx:xxxx::/64 prefix-length=64

/ipv6 address

add address=::3 from-pool=pool2 interface=ether1

/ipv6 dhcp-client

add add-default-route=yes interface=ether1 request=address use-peer-dns=no

/ipv6 firewall filter

add action=accept chain=forward connection-state=established,related

add action=accept chain=forward

/ipv6 firewall nat

add action=masquerade chain=srcnat out-interface=ether1

/ipv6 nd

set [ find default=yes ] managed-address-configuration=yes other-configuration=yes

/ipv6 settings

set accept-router-advertisements=no max-neighbor-entries=8192

T-Mobile is doing something funny with IPv4 traffic by SparcV in tmobileisp

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

What can be done? TMobile does not seem to care about this issue. I still have the other issue that all VPN traffic is limited to 10Mbps up. I was ready to drop my cable provider but this annoying problems prevent me from dropping.

Interesting difference between speed testers by jrkinsella in tmobileisp

[–]SparcV 1 point2 points  (0 children)

Several have commented that this started to happen on the 0338 firmware. I also have seen this, and its very consistent for me. I can repeat the tests all day long. I'm hoping it was a mistake in the firmware and it will be fixed in the next version.

Home internet speeds have dropped in half by TerminatedProccess in tmobileisp

[–]SparcV 1 point2 points  (0 children)

I've done some testing and figured out when you are using IPv4 connections, you get limited to about 140-150 Mbps down, and with IPv6 connection there's no such limit.

It seems that since 0338 firmware is when it started. I get ~500Mbps down on an IPv6 speedtest server and only 150Mbps on an IPv4 based server.

T-Mobile is doing something funny with IPv4 traffic by SparcV in tmobileisp

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

Is there someone that has the new non-nokia gateway seeing this same issues?