16
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
17
22.7 Legacy Series / Re: No carrier after install
« on: August 21, 2022, 05:25:58 pm »Quote
What I find ironic, is the big providers stick to cable/DSL because they say fiber is too expensive to lay, too expensive to maintain, etc. While the small providers that specialize in fiber internet charge lower prices, are profitable and growing. Albeit slowly since they can only grow in new housing developments. No one seems to be interested in building in established neighborhoods.
Established companies have more regulations and potential blow back for putting fiber in only in profitable new neighborhoods and skipping over the ones they already service. New companies don't suffer any local/federal/political/contractual ramifications for actively expanding into those same areas because they don't have the "baggage" of preexisting older neighborhood customers.
18
22.7 Legacy Series / Re: VlanXX shows up as vlan01 ?
« on: August 21, 2022, 05:18:06 pm »Im also a bit confused here. All my VLANs previously created under Interfaces – Other Types – VLAN are shown under Devices like:Read the message from @franco I linked above. Previously created Vlans keep the old naming convention (for now per him) new vlans get the new naming convention.Code: [Select]lagg0_VLAN10
New created VLAN with 22.7.2 is shown under Device just as vlan01
lagg0_VLAN15
lagg0_VLAN18
etc.
19
22.7 Legacy Series / Re: Good ad blocking solution
« on: August 20, 2022, 02:19:15 am »
Lots of people use the community repository. No need for apprehension there. I use it for adguard and would have no issue suggesting others go that route for adblocking.
20
22.7 Legacy Series / Re: VlanXX shows up as vlan01 ?
« on: August 19, 2022, 11:54:52 pm »
Intentional change starting at 22.1.
https://forum.opnsense.org/index.php?topic=27696.msg134489#msg134489
https://forum.opnsense.org/index.php?topic=27696.msg134489#msg134489
21
22.7 Legacy Series / Re: multi-wan failover problem
« on: August 19, 2022, 11:51:59 pm »for today's software...yes...unfortunately release is no longer the actual release.Been that way from the start when a company has a free early consumer release and a delayed business release. One of those 2 is more battle-tested at the expense of the other.
22
22.7 Legacy Series / Re: 22.7.2 Wireguard service won't start
« on: August 19, 2022, 05:17:57 pm »
@somebod3983 all you need to do to use the WireGuard kernel module is run the command below at the OPNsense cli. No need to uninstall go. May need to restart the service to reestablish any ongoing connections. All current peers and setting in the WireGuard settings gui will be used without any others action needed.
Code: [Select]
pkg install wireguard-kmod
23
22.7 Legacy Series / Re: lack of support for opnsense hardware
« on: August 19, 2022, 04:54:12 pm »not thanks. my clients..either home or business are not used by me to beta test my vendors products. I now know the release policy of OpNSense..lesson learned..all the more reason to do your homework and know your vendors release model. OPNsense, Proxmox many others use this public release and followed months behind by a business release model. For companies that don’t or can’t stay in business charging enterprise markups, most opensource type software with a free variant, this is a valid model to use.
24
22.7 Legacy Series / Re: multi-wan failover problemd
« on: August 19, 2022, 04:39:57 pm »I know how it works now....not too long ago release meant release...not it's kinda done but the users are the final beta test which has infested the rest of the software community. Firewalls and other critical infrastructure..imo...should hold themselves to a higher standard and open source ones used to hold themselves to even higher ones. You what they say about assumptions...especially code quality across the entire spectrum now...Assumptions always bite you in the ass.trying to understand why you would not use the free 22.4 1-year business license that comes with your hardware purchase. It’s there to keep you, your business, your customers and OPNsense safe. Let free home users beat on 22.7 for many months until OPNsense is convinced all the unforeseen show stoppers are cleaned up. Then you be will justified in coming at them if you experience this in the business release.
25
22.7 Legacy Series / Re: lack of support for opnsense hardware
« on: August 19, 2022, 04:34:33 pm »If you want to RMA please do. I don't see your point for multiple reasons:@hescominsoon is there a reason you choose not to use the more conservative and stable business release? Your issue is exactly one of the reasons it’s available and often months behind the public releases. You jumped on the relative bleeding edge for a mission critical device.
1. You keep confusing hardware and software.
2. Your issues with 22.7 are strange when you have a free 22.4 1-year business license with your hardware.
3. Software improvements require qualified input and may take time to materialize outside your immediate setup requirements.
Cheers,
Franco
Let the home users be your business’ and OPNsense’s beta testers (relative to mission critical production your job/reputation is on the line use) not you and your customers.
26
22.7 Legacy Series / Re: OPNsense running in Proxmox on new Topton N6005 and keeps crashing.
« on: August 18, 2022, 07:16:34 am »
@chenganir not using Topton, but currently running OPNsense as Proxmox vm with uefi/q35 and Linux bridges for wan/lan as it’s just easier.
Not sure about your question. The short version would be To pick two unused physical ports and create Linux bridges with them. Use VirtIO. Give these bridges to OPNsense. Give Proxmox a cidr in the OPNsense lan subnet on the vmbr used for lan. Connect your VM’s there. If you have a switch plug it into the physical port/bridge port used for lan.
Not sure what you mean by going through the management bridge?
Not sure about your question. The short version would be To pick two unused physical ports and create Linux bridges with them. Use VirtIO. Give these bridges to OPNsense. Give Proxmox a cidr in the OPNsense lan subnet on the vmbr used for lan. Connect your VM’s there. If you have a switch plug it into the physical port/bridge port used for lan.
Not sure what you mean by going through the management bridge?
27
22.7 Legacy Series / Re: None of my VLAN interfaces are working after upgrade to 22.7
« on: August 10, 2022, 03:25:14 pm »Thanks for the advice, I will do this the moment I get home. As for the requirement, my installation goes back quite a few major releases, way before 22.1.x maybe even, and it was never requested to assign a parent interface and I can't believe I will be the only one.Soon after 22.1 was introduced, someone made a YouTube walkthrough on this requirement, if that helps.
https://youtu.be/69cNH9UX_es
28
22.7 Legacy Series / Re: WAN failover scenario.
« on: August 10, 2022, 03:16:10 pm »
One option linked below to a weirdly similar post.
https://forum.opnsense.org/index.php?topic=29723.0
https://forum.opnsense.org/index.php?topic=29723.0
29
22.7 Legacy Series / Re: WAN failover scenario
« on: August 06, 2022, 08:05:13 pm »
Create 2 separate gateway groups.
Gateway group 1 - Wan1 is tier 1 and Wan2 is tier 2 (primary Wan1 failover to Wan2)
Gateway group 2 - Wan2 is tier 1 and Wan1 is tier 2 (primary Wan2 failover to Wan1)
Now that you have 2 failover groups, Follow this link https://docs.opnsense.org/manual/how-tos/multiwan.html and choose the appropriate gateway group for each subnet firewall default allow rule and DNS.
Gateway group 1 - Wan1 is tier 1 and Wan2 is tier 2 (primary Wan1 failover to Wan2)
Gateway group 2 - Wan2 is tier 1 and Wan1 is tier 2 (primary Wan2 failover to Wan1)
Now that you have 2 failover groups, Follow this link https://docs.opnsense.org/manual/how-tos/multiwan.html and choose the appropriate gateway group for each subnet firewall default allow rule and DNS.
30
22.7 Legacy Series / Re: WAN port issues for AT&T Pace 5268AC gateway
« on: August 03, 2022, 04:42:57 am »
Hmm, I suspect the Pace should not need any special MAC address, as long as it was rebooted since last working connection and I assume you have rebooted.
Just guessing but did you have to input a mac address into the setting on the pace to get IP passthrough up and running? I seem to remember something like that from my bgw-210. Since the first thing the pace is connected to is a switch now, you might have to use the mac address of that switch port, in the pace and/or the opnsense Wan mac clone.
Just guessing but did you have to input a mac address into the setting on the pace to get IP passthrough up and running? I seem to remember something like that from my bgw-210. Since the first thing the pace is connected to is a switch now, you might have to use the mac address of that switch port, in the pace and/or the opnsense Wan mac clone.