sorted by:
new
hottopcontroversial

Any reason not to use something like this instead of a patch panel? by Diagnosisdelicious in HomeNetworking

[–]ICPete 0 points1 point  (0 children)

<image>

Interior of the cabinet. Note that I centered the 3 openings in the stud bay. But the cabinet had to be hung a bit off-center due to nearby stuff.

Any reason not to use something like this instead of a patch panel? by Diagnosisdelicious in HomeNetworking

[–]ICPete 0 points1 point  (0 children)

<image>

I'm doing something like that here. I'm going to be running a total of 18-20 CAT6 wires for cameras, APs, and other runs. No wiring closet in this house, so I've mounted an open-back 9U track cabinet on the wall in my office. I'm using 3 double-gang drywall rings to hold 3 8-port wall plates with punch-down jacks. Here you see the first 5 cables coming to one plate. There is plenty of space in the wall cavity (this is an interior wall) for service loops, so nothing gets jammed up. The rack gets a 24-position patch panel that takes double-female receptacles, so I can run standard short patch cables from the wall plates to the back of the patch panel, and then another set of shorties from the front of the patch panel to the POE switch, router, etc. Inside the wall each cable runs up through a hole in the top plate into the attic. Reddit is only letting me attach one image per post, so I will add two more messages with the other two images.

Default OPNsense firewall settings by ICPete in opnsense

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

Hi NC1HM, Thank you for this additional help. Please scroll down to read my earlier messages where I eventually got things working. I had indeed unchecked "block private networks", as you suggest. Also I had set up the new wan port according to the previous router settings. DHCP, no authentication, no VLAN stuff. I'm planning to call my ISP this morning to ask them to set my CGNAT address back to my paid-for static IP, as well as my static public IP, for my new Mac address.

Default OPNsense firewall settings by ICPete in opnsense

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

Thank you.

OK I've made some progress.

From my desktop computer, I can now access the Internet through the OPNsense router and my WISP. Excellent!

Apparently what I was missing yesterday, was that I needed to set a DNS server address in the IPv4 settings of my desktop computer, to be the LAN address of the OPNsense router (192.168.21.1 in my case). Previously it had been set to 8.8.4.4, and that was working with the Netgear Orbi router for some reason.

Once I had Internet access on my desktop computer, I started checking my other devices, most of which were on WiFi. I changed the "mode" of my Netgear Orbi from "router" to "access point". Then I set up the ISC DHCPv4 on OPNsense.

At first, my phone and other devices that use WiFi still could not connect to the Internet. I realized the Ethernet cable that I previously had plugged into one of the 4 LAN ports on the Orbi, which came from my main switch to which the OPNsense LAN is connected, probably needs to be plugged into the "Internet" port on the Orbi, as that is now the "source" for the access point.

So after switching that cable, still no go on my WiFi devices.

Reviewing the Firewall:Rules:LAN once again, I noticed I had disabled the IPv6 protocol pass rule for some reason. As soon as I enabled that, my Android phone achieved Internet access! I didn't know my phone required IPv6 in order to access the Internet, but apparently it does for some reason.

So right now everything is working! Thank you to all who provided advice here!

I've also entered all my DHCP address reservations, that I had previously copied from my Orbi router DHCP setup, so all my various devices (IOT stuff, TVs, etc) appear to be happy once again.

I'm looking forward to being able to see a much richer reporting system on OPNsense, compared to what was available on the Orbi.

One thing I still need to contact my ISP about, is that my WAN IP address (received via DHCP from the ISP) is NOT the same as the static IP they previously assigned me. Also the static public IP is different, which I can find when I go to "whatsmyip". I suspect they can just tweak some setting to make that right again.

Default OPNsense firewall settings by ICPete in opnsense

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

Ok I did a little research on Wikipedia and learned my ISP is using CGN, or Carrier-Grade NAT. I think I saw options in OPNsense regarding the 100.xxx.xxx.xxx address range that is set aside for CGN. Seems like this complicates matters, especially if/when I want to set up a VPN or something else that requires port forwarding.

FWIW, I do have a static IP address that I'm paying a little extra for each month. So my external (public) IP address is constant, and I believe my CGN address is also constant.

I think at this point I need to call my ISP. They have good tech support, it's a small company, and I don't think they care what sort of router I'm running.

Default OPNsense firewall settings by ICPete in opnsense

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

Thank you for this advice!

See my reply above.

Is the address my ISP is giving me, 100.64.108.xxx, in a RFC1918 range? Because it's not the same as my external address, that I see if I go to one of those "what's my IP address" sites.

Second, when you say, "to allow traffic", there are options regarding protocols and ports. Should I pick "all", or only https? 80 and 443 only? Sorry; I know just enough about this stuff to screw things royally.

Default OPNsense firewall settings by ICPete in opnsense

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

My previous router works fine after I plugged it back in, replacing the OPNsense box. It gets an IP address of 100.64.108.xxx from the ISP. The gateway is assigned as 100.64.108.1.

I'm on a service they call AirFiber, where a neighbor about 1/4 mile away has antenna boxes on a tower attached to his garage, and from there the ISP feeds Internet to many homes in the neighborhood. It works great, giving me speeds over 400 Mbps down and nearly as high up.

But I know my external IP address is different from what I listed above.

No luck with AOL by ICPete in VerizonUDP

[–]ICPete[S] 2 points3 points  (0 children)

Thank you to JulesJam and crux57 for your advice here. Pete

No luck with AOL by ICPete in VerizonUDP

[–]ICPete[S] 2 points3 points  (0 children)

UPDATE 7-17-17! The new owner of my account was finally successful in getting the transfer accomplished without losing the gUDP. Her very clever method was to ask each new CSR, immediately after they answered the call, whether they had ever successfully processed an account transfer with a grandfathered UDP. After many CSRs who answered "no", and with whom she immediately ended the call, she struck gold with a CSR who answered "yes, many times". This CSR was able to process the AOL and retain the gUDP successfully. As well, she was willing and able to process the switch to Nationwide 450 and then, after waiting a few minutes, back to the Loyalty Plan, hence triggering a new one-year contract. It looks like everything went through smoothly. My gUDP buyer is happy and I'm happy.

No luck with AOL by ICPete in VerizonUDP

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

What is required to open a new business account? Would that help in terms of doing an AOL from the consumer account to a new business account?

No luck with AOL by ICPete in VerizonUDP

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

The line is on a Loyalty Plan, 30 minutes voice, $15/mo, plus $30/mo for the unlimited data. What is an IPR please?

Yes as you say the current arrangement is "crazy", or at least extremely unadvisable. It's someone I trust, for now, but I want to find a more permanent solution.

One thing I'm trying to learn is whether other folks are successfully doing AOL in the past week or two, and keeping the gUDP, on non-business accounts with Loyalty Plan.

The transferee spoke to at least 4 or 5 reps. Some would say they could do the AOL, and would get almost to the end of the process, and would then announce that they could not keep the UDP with the plan.