Recent posts

#1

German - Deutsch / Re: Neues setup - Fragen zur S...

Last post by Patrick M. Hausen - Today at 10:27:18 PM

Die Verantwortung für deine Konfiguration liegt bei dir. Du wirst hier keine "semi-offizielle" Abnahme bekommen. Nicht in einem Community-Forum und kostenlos. Ich mache sowas gerne gewerblich über meine Firma.

Just saying.

#2

German - Deutsch / Re: Neues setup - Fragen zur S...

Last post by name89214 - Today at 10:15:48 PM

So, ich habe nochmal meine Einstellungen auf Werkseinstellungen zurückgesetzt und neu begonnen.

Zunächst mal bis hier hin meine Basiskonfiguration. Internet auf LAN funktioniert. Das sollte für Telekom VDSL so passen - ansonsten lasst es mich bitte wissen.

Einstellungen nach Anleitung "IPv6 for generic DSL dialup" https://docs.opnsense.org/manual/how-tos/ipv6_dsl.html

• System > General > System: Domain = home.arpa
• Interfaces > LAN > Static IPv4 address = 192.168.1.2/24
• Interfaces > WAN > Generic configuration: IPv6 Configuration Type = DHCPv6
• Interfaces > WAN > DHCPv6 client configuration: Request prefix only = check
• Interfaces > WAN > DHCPv6 client configuration: Send prefix hint = check
• Interfaces > WAN > DHCPv6 client configuration: Prefix delegation size = 56
• Interfaces > LAN > Generic configuration: IPv4 Configuration Type = Static IPv4
• Interfaces > LAN > Generic configuration: IPv6 Configuration Type = Track interface (legacy)
• Interfaces > LAN > DHCPv6 client configuration: Request prefix only = check
• Interfaces > LAN > Track IPv6 Interface: Parent interface = WAN
• Interfaces > LAN > Track IPv6 Interface: Assign prefix ID = 0

Einstellungen nach Anleitung "PPPoE ISP Setup" https://docs.opnsense.org/manual/how-tos/pppoe_isp_setup.html

• Interfaces > WAN > Generic configuration: IPv4 Configuration Type = DHCP
• Interfaces > WAN > Generic configuration: IPv4 Configuration Type = None
• Interfaces > WAN > Generic configuration: IPv6 Configuration Type = DHCPv6
• Interfaces > WAN > Generic configuration: IPv6 Configuration Type = None
• Interfaces > Devices > VLAN > add:
  
  • Device = vlan0.1.7
  • Parent = igb0 (ab:12:...) [WAN] 
  • VLAN tag = 7
  • Description = vlan0.1.7
• Interfaces > Devices > Point-to-Point > add:
  
  • Link Type = PPPoE
  • Link interface(s) = vlan0.1.7
  • Description = igb0_vlan_PPPoE 
  • Username = abc
  • Password = 123
• Interfaces > Assignments: assign Device = pppoe0 (vlan0.1.7)-igb0...
• Interfaces > igb0_vlan7_PPPoE: Enable = check
• Interfaces > igb0_vlan7_PPPoE: IPv4 Configuration Type = PPPoE

Ansonsten noch kleinere settings wie beep, theme, ...

Zu

• Interfaces > WAN > Generic configuration: IPv4 Configuration Type = DHCP None
• Interfaces > WAN > Generic configuration: IPv6 Configuration Type = DHCPv6 None

In letzterer Anleitung "PPPoE ISP Setup" (https://docs.opnsense.org/manual/how-tos/pppoe_isp_setup.html) sollte man sowohl IPv4 als auch IPv6 config type als None setzen - entgegen der ersten Anleitung "IPv6 for generic DSL dialup" (https://docs.opnsense.org/manual/how-tos/ipv6_dsl.html).

Passt das so?



Die Tage mache ich mich ans Eingemachte wie Firewall, DNS, DHCP etc. und poste dann nochmal ein update. Besten Dank euch schon mal!

#3

Q-Feeds (Threat intelligence) / Re: Help fixing 'erroneous' Q-...

Last post by Patrick M. Hausen - Today at 10:00:35 PM

They have a false positive reporting form in your TIP.

#4

Hardware and Performance / Re: AX88179B USB NIC: 57 -> 97...

Last post by patient0 - Today at 10:00:17 PM

If you want to get it fixed, you report it to upstream FreeBSD, https://bugs.freebsd.org. With a way to reproduce the issue, link to this forum thread, using less words if you can. Not sure how many people read a short story like that.

#5

General Discussion / Re: Help needed to update boot...

Last post by Patrick M. Hausen - Today at 09:59:02 PM

1. Update your LSI controller firmware? Update your SSD firmware? Place the vendor update tools on the EFI partition from your running FreeBSD OS, boot into EFI shell via IPMI, update $STUFF.

2. No obscure "dd" incantations to update the boot loader. FAT32, documented directory structure, done.

3. Manage boot order with "efibootmgr" from the running OS - no need to ever go to the BIOS for that.

First points that come to my mind.

#6

Q-Feeds (Threat intelligence) / Re: Help fixing 'erroneous' Q-...

Last post by Taunt9930 - Today at 09:41:04 PM

AHH, brilliant - thanks both - I missed that. Didn't think to search for 43.131.0.0. (Yes, I'm on plus).

What's the best way to whitelist/bypass for that single address? I notice you can add domain whitelist in qfeeds, but not sure you can add an IP?

#7

26.7 Series / Re: Call for testers - new CPU...

Last post by nero355 - Today at 09:37:34 PM

How many more times do I need to repeat this?

#JustPeopleOnTheInternetTheseDays... 😉

Nothing we can do about it sadly :(

#8

General Discussion / Re: Help needed to update boot...

Last post by nero355 - Today at 09:26:42 PM

For "real servers" EFI is the best invention since sliced bread. Nothing else, please.

Why exactly ?!

Apart from regular PCs and Laptops doing that fancy fast booting stuff for Consumers there is nothing that I can think of that I actually like about it to be honest...

#9

General Discussion / Re: Sonicwall TZ300 compatibil...

Last post by nero355 - Today at 09:20:29 PM

If correct, Mips64 would be a show stopper in any case.

If there is one mistake I will never make again then it has to be buying hardware that (almost) completely depends on Offloading Chips and usually MIPS based stuff does exactly that! :(

#10

General Discussion / Re: Help needed to update boot...

Last post by Patrick M. Hausen - Today at 09:15:04 PM

Again there is not really a pro or a contra for one method or the other. At least IMHO for a small appliance. For "real servers" EFI is the best invention since sliced bread. Nothing else, please.