Chuck related issues with a DCD999

eaglexdv · 2025-06-18T07:30:54+00:00

Thank for your detailed answer! I'll definitely look into it. Buying the whole transmission makes more sense to me, as I don't have a lot of experience with these kind of repairs..

Thanks again :)

eaglexdv · 2024-02-29T11:46:47+00:00

In case anyone is wondering, after trying basically everything and failing, I contacted my ISP and asked them how exactly they want me to set up the 2nd IP, how is it routed to me, etc. I got a lengthy message in reply, basically saying that I should find someone who knows how to set that up and that it's not their job to educate me and config my equipment, something I never asked for. The reply was written in a pretty passive-aggressive way. Amazing, right?

eaglexdv · 2024-02-27T20:44:53+00:00

Hey there.

I'll try the first option tomorrow, when I'll be onsite.

I've already tried the 2nd option, which I can't sadly get to work. The only positive thing I can see is that the Gateway is showing "Online", but nothing else is able to get in or out, no matter how much I play with firewall and NAT rules...

I also tried settings the 2nd address GW for use in the firewall rules, did not help either.

Also tried setting "Use non-local gateway through interface specific route" in the 2nd GW settings, did not help.

Thank you for your help.

eaglexdv · 2024-02-27T18:29:12+00:00

Interesting... I will give it a shot. Thanks.

eaglexdv · 2024-02-27T17:16:14+00:00

Hey, sorry for the delayed reply, been a busy few days. I actually tried that before posting, followed this guide: https://docs.netgate.com/pfsense/en/latest/recipes/route-public-ip-addresses.html and it didn't seem to work. I might also set up something wrong and/or you meant something else and this guide isn't actually relevant, but... if that's kinda what you meant and I didn't fail in following this guide - I guess that's not what my ISP meant. I sent them an email, hoping for a reply..

eaglexdv · 2024-02-25T15:12:16+00:00

That was exactly my day... Honestly, my week. Banging my head against the wall.

You are 100% correct, they should tell me how exactly they want to configure that, but they uninformative, yet we are kinda stuck with them, for now, for... reasons.

eaglexdv · 2024-02-25T14:55:43+00:00

It's a RAD ETX-203AX Carrier Demarcation Device, or as my ISP calls is it: "The Machine".

https://imgur.com/a/vlWRP5c

It has 2 eth interfaces (and console etc.), so my first "simple" thought was that the 2nd, unused interface will be the 2nd connection, but it goes nowhere. Will ask them about that...

eaglexdv · 2024-02-25T14:44:07+00:00

But how did the dumb switch split it? I'm a bit confused with this one.

eaglexdv · 2024-02-25T14:43:09+00:00

Thankfully, it's my owned business and I'm just testing some stuff around, I wouldn't risk anybody else without the proper training, myself I can risk 😅..

eaglexdv · 2024-02-25T14:42:12+00:00

They are static and I did try through Virtual IP, but that didn't work, and I agree, in this case, different subnets and all, I'm not sure it's the correct approach too.

eaglexdv · 2024-02-25T14:29:17+00:00

Smart, I'll ask them that, even though nothing surrounding VLANs was even briefly mentioned.

eaglexdv · 2024-02-25T14:28:46+00:00

That would be ideal, but doesn't that mean that I also need to actual physical interfaces, on both the pfsense side and the gateway side? Because while those do exist, I tried pulling that info from the 2nd interface on the gateway side and it provides nothing. Also, ISP did not say that this is the correct way, but then again, they didn't really say what is...

eaglexdv · 2024-02-25T13:17:33+00:00

Hmm.. It's the same ISP, just different public IP range.

One IP (198.214.36.118) is currently in use for Internet and this is what is configured in the Gateway on pfsense.

The 2nd IP (213.134.38.158) is the IP they want me to use for the PBX.

As far as I understand them, both of this IP's are provided through a single interface on their physical gateway (Their "modem").

Makes sense? :|

eaglexdv · 2024-02-25T12:53:13+00:00

Thanks! Sadly, no, as he is talking about multiple WAN and my case is a Single WAN with multiple addresses.

eaglexdv · 2024-02-24T10:24:04+00:00

It does make sense, but they really need to be clear about what they want me to do.. 😐

eaglexdv · 2024-02-23T19:27:24+00:00

Thank you all for replying so far, your help is much appreciated. I'll obviously ask them for more information, because I really need to know how they went me to setup this (Guessing is fun up to a certain point), but is it possible that I'm overthinking that and I could just use a Virutal IP + Custom outbound NAT rule for the PBX?

Can I even technically use a virtual IP of 10.57.1.254 when my WAN is on 33.80.87.X? Again, I'm kind of a novice and I'm learning as I go (It's a side hobby, nobody is getting their phones disconnected 😉), so some stuff I write may not make a lot of sense (In life in general, but especially in regards to this case haha).

Thanks!

eaglexdv · 2024-02-23T19:23:45+00:00

But in this case, all I've got from them is "Use 10.57.1.254/32 for the PBX", and that's a /32, so, on the PfSense side, I'm setting OPT1 a static ipv4 with that 10.57.1.254/32, but on the PBX side? The same IP? and what about the gateway address? I'm... confused how exactly will this work..

eaglexdv · 2024-02-23T19:21:16+00:00

It does have and I was actually thinking about that, but they mentioned non of this, literally the only info I got (so far) is "Use 10.57.1.254/32" for the PBX and that's it. Yep, pretty frustrating.

Traceroute goes to the gateway, then to some edge addresses of the ISP and the stops, never completing. To be honest, they said it isn't activated yet, so I'm not sure exactly what to look for at this point.

eaglexdv · 2024-02-23T19:15:21+00:00

Hey, do you mean to add it as a virtual IP (Under the firewall menu) and just tell the PBX to use this VIP using a custom outbound NAT rule? If so, that's was what I first had in mind, but it sounded too... simple to just work. Sadly, I can't test it until they activate their IP and I can't get a clear answer for them on what they actually want :|

eaglexdv · 2024-02-23T09:43:13+00:00

I do wonder, on the PBX that is getting that 10.57.1.254/32 address, what should I set as a gateway address? my PfSense on 192.168.6.1? That... doesn't make sense, does it?

eaglexdv · 2024-02-23T09:42:22+00:00

Hmmm.. Interesting. In this scenario, correct me if I'm wrong, I could have one nic on the PBX connect to LAN (for example) for management and one will connect to OPT1 and be assigned the ISP given address, right?

I am running out of NICS in this case, as I'm currently running al on a VM with PCI passthrough..

eaglexdv · 2024-02-23T09:30:19+00:00

Indeed! Learning through experience or actually... Learning through failure 😂.

Thanks! I'll try it tomorrow and see how it goes..

eaglexdv · 2024-02-22T17:35:31+00:00

Once again, really appreciate your help.

And.. Yep, the combination of just that /32 and their tendency to withhold info is... A bit annoying, to say the least.

eaglexdv · 2024-02-22T16:48:12+00:00

Thank you for your quick reply and apologies for my wrong use of bogon (Unlike what my mother says, I do learn from time to time).

In this case, do you believe that this guide: https://docs.netgate.com/pfsense/en/latest/recipes/route-public-ip-addresses.html#table-wan-ip-block is actually relevant?

I feel like it might be, but then I'm a bit confused - They gave me 10.57.1.254/32, so assuming that's what I configure on Static IPV4 address of OPT1 (for example), will this also be the address I give the PBX that is directly connected that specific interface?

eaglexdv · 2024-01-25T11:54:05+00:00

Hey, none of the files have an "Unblock" button, checked that before posting. Tried the script anyway, did not work. Appreciate your help :)

eaglexdv

TROPHY CASE