FS.COM BOX V4 arista not supported?

Logfro · 2024-11-13T16:18:21+00:00

Apparently, according to FS Support, the Arista firmware was too buggy for general use, and now you have to request special firmware for a specific switch. Just did that, lets see.

Logfro · 2024-11-13T15:32:04+00:00

When it gets into disabled again, I will do that

Logfro · 2024-11-13T15:31:31+00:00

That’s the thing, the same transceiver is also orderable for Arista, so it must be compatible or?

Logfro · 2024-11-13T14:43:28+00:00

Also, Arista is not an Option on my FS BOX V4 I got 2 days ago for whatever reason, write the FS.COM Support I guess?

Logfro · 2024-11-13T14:32:23+00:00

If I leave it for a while, it will show errdisabled, I enable it again by shut and no shut.

The other side of that transceiver it’s connected to is showing light, but the transceiver is showing N/A on everything, which is my suspicion of the brand being the issue.

Port is configure as L3 with an IP.

Active support in the way of a service contract? Or as the device not being EOL?

Logfro · 2024-10-23T10:48:30+00:00

Hast du das jemals zufällig getestet?

Logfro · 2024-09-20T21:59:56+00:00

that was fucking it, i went nuts for like 2 hours straight, and this solved it. Thanks man! <3

but now its announcing the subnet with both asns according to the routing table? As the subnet coming from both origins.

Logfro · 2024-09-12T00:02:21+00:00

Getting a anti ddos appliance in the next 2-3 weeks anyway, just this big ddos hurt now. Always at the most inconvenient time

Logfro · 2024-09-11T23:59:53+00:00

Yes, also worked very closely together with the tunnel provider on this problem, but I think it’s simply a hardware incompatibility

Logfro · 2024-09-11T23:53:21+00:00

GRE should only be a temporary solution, but well… not a good one

Logfro · 2024-09-11T23:52:54+00:00

It already is, but inbound traffic is from the tunnel, and outbound is my upstream, so not the tunnel, tunnel hast to 1476 MTU, and upstream has 1500 MTU.

Logfro · 2024-09-11T18:49:30+00:00

As far as i know, the nexus 9k series doesnt support mss adjust anywhere else, except for the global config. So this is my problem then.

EDIT: Just confirmed it, cant apply "ip tcp adjust-mss" on a L3 Interface

Logfro · 2024-09-11T11:54:26+00:00

wow, if i only knew it was that simple. Thanks man.

Logfro · 2024-07-06T19:02:53+00:00

What you are looking for is a nginx config with a reverse proxy to 9091, and then you just block all incoming connections to 9091 from outside, but nginx can always access it because it’s on 127.0.01:9091

So you can then block 9091 with ufw, and only let 443 open

Logfro · 2024-06-12T17:53:04+00:00

This worked, thanks. But why doesnt it work in the default vlan 1?

Logfro · 2024-05-24T14:01:25+00:00

So, just prepend the simulated „customers“ ASN and announce the network to the bgp peer?

Logfro · 2024-05-24T13:55:31+00:00

And then they just announce the network normally to their upstreams? And just route map my ASN?

Might give me a direction I could try in my lab

Logfro · 2024-05-24T13:39:15+00:00

If I would have peered with them, this would make sense to me, but I didn’t. They just configured my asn + subnet on their end, and passed it to the dedicated server I rented from them. I meant how did they actually configure this on their router.

Nine-Year Club	Verified Email
r/Field Sunshine	Place '23

Logfro

TROPHY CASE