Messages

1

23.1 Legacy Series / Re: Unbound not caching results?

« on: March 07, 2023, 06:51:17 am »

Websites these days set ridiculous TTLs like 1 minute. It's possible to force minimum TTL time to override what the site dictates. More reading: https://blog.apnic.net/2019/11/12/stop-using-ridiculously-low-dns-ttls/

2

17.1 Legacy Series / Re: Tried 100 Times. Any Help.

« on: March 15, 2017, 06:47:58 am »

How much RAM does the VM have? Did you try increasing it?

3

17.1 Legacy Series / Re: How to prevent SSH bruteforce, DOS attacks

« on: March 15, 2017, 06:41:15 am »

would anyone know if there is a way to prevent...

How To Create SSH Keys With PuTTY to Connect to a VPS | DigitalOcean. This will prevent it.

4

Development and Code Review / Re: Drill down menu system

« on: March 12, 2017, 02:32:24 pm »

Tabs could be in rows instead of overflowing to the side. The main thing is m0n0wall's flavor of centralized collection of pages. Especially the status and diagnostics section.

5

Development and Code Review / Re: Drill down menu system

« on: March 12, 2017, 01:18:30 pm »

My apologies for my initial approach to the matter.
Speaking of the m0n0wall type menu, I hope to see submenus go just one level deep like before. Sub- submenus could be tabs on top?

6

Development and Code Review / Re: Drill down menu system

« on: March 12, 2017, 12:38:31 pm »

The tree like menus are horrible in my opinion. What was achieved by splitting the log pages into fifteen different places? There's not a huge work to be done; just put it back to where it was before. Technical specs for new menu theme - like m0n0wall.

Maybe my frustration in navigating came across as attitude. I have provided adequate details for you to understand what I'm talking about. Probably used a few question marks - to underline my frustration.

7

Development and Code Review / Re: Drill down menu system

« on: March 12, 2017, 12:25:37 am »

The "fastest way" is relative because it's still cumbersome and slow, compared to before it was rejigged. I'd like to propose a feature request for a legacy menu theme.

8

Development and Code Review / Drill down menu system

« on: March 11, 2017, 11:26:18 pm »

The menus are decentralized and cascading replaced by drill down menu, compared to before the fork. I understand there has to be some differentiation, but this seems like a step forward and then two steps back. Has anybody had to quickly check log files for this and that, ever? I tried doing it.

9

Development and Code Review / Re: [RFE] add traffic per rule in the GUI

« on: January 26, 2017, 07:40:44 am »

+1

10

16.7 Legacy Series / Re: [CALL FOR TESTING] MTU > 1492 in PPPoE -- RFC 4638

« on: March 01, 2016, 08:54:31 am »

Okay great. As soon as I type 1508 into the MTU, the "calculated ppp mtu :" changes to 1500. After WAN reconnect, it's working.

Code: [Select]

root@OPNsense:~ # ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1508
        options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:0c:29:70:8a:70
        inet6 fe80::20c:29ff:fe70:8a70%em0 prefixlen 64 scopeid 0x1
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet 1000baseT <full-duplex>
        status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 00:0c:29:70:8a:7a
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::1:1%em1 prefixlen 64 scopeid 0x2
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
pflog0: flags=100<PROMISC> metric 0 mtu 33160
pfsync0: flags=0<> metric 0 mtu 1500
        syncpeer: 0.0.0.0 maxupd: 128 defer: off
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
enc0: flags=0<> metric 0 mtu 1536
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1500
        inet6 fe80::20c:29ff:fe70:8a70%pppoe0 prefixlen 64 scopeid 0x7
        inet 2.97.45.156 --> 92.51.208.1 netmask 0xffffffff
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Code: [Select]

Mar 1 10:34:19 ppp: [wan] IFACE: Rename interface ng0 to pppoe0
Mar 1 10:34:19 ppp: [wan] IFACE: Up event
Mar 1 10:34:13 ppp: [wan] 2.97.48.166 -> 92.50.208.1
Mar 1 10:34:13 ppp: [wan] IPCP: LayerUp
Mar 1 10:34:13 ppp: [wan] IPCP: state change Ack-Sent --> Opened
Mar 1 10:34:13 ppp: [wan] SECDNS 8.8.8.8
Mar 1 10:34:13 ppp: [wan] PRIDNS 8.8.4.4
Mar 1 10:34:13 ppp: [wan] IPADDR 2.97.48.166
Mar 1 10:34:13 ppp: [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)
Mar 1 10:34:13 ppp: [wan] SECDNS 8.8.8.8
Mar 1 10:34:13 ppp: [wan] PRIDNS 8.8.4.4
Mar 1 10:34:13 ppp: [wan] IPADDR 2.97.48.166
Mar 1 10:34:13 ppp: [wan] IPCP: SendConfigReq #3
Mar 1 10:34:13 ppp: [wan] SECDNS 8.8.8.8
Mar 1 10:34:13 ppp: [wan] PRIDNS 8.8.4.4
Mar 1 10:34:13 ppp: [wan] 2.97.48.166 is OK
Mar 1 10:34:13 ppp: [wan] IPADDR 2.97.48.166
Mar 1 10:34:13 ppp: [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)
Mar 1 10:34:13 ppp: [wan] IPV6CP: LayerFinish
Mar 1 10:34:13 ppp: [wan] IPV6CP: state change Req-Sent --> Stopped
Mar 1 10:34:13 ppp: [wan] IPV6CP: protocol was rejected by peer
Mar 1 10:34:13 ppp: [wan_link0] LCP: protocol IPV6CP was rejected
Mar 1 10:34:13 ppp: [wan_link0] LCP: rec'd Protocol Reject #63 (Opened)
Mar 1 10:34:13 ppp: [wan] SECDNS 0.0.0.0
Mar 1 10:34:13 ppp: [wan] PRIDNS 0.0.0.0
Mar 1 10:34:13 ppp: [wan] IPADDR 0.0.0.0
Mar 1 10:34:13 ppp: [wan] IPCP: SendConfigReq #2
Mar 1 10:34:13 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 1 10:34:13 ppp: [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)
Mar 1 10:34:13 ppp: [wan] IPCP: state change Req-Sent --> Ack-Sent
Mar 1 10:34:13 ppp: [wan] IPADDR 92.50.208.1
Mar 1 10:34:13 ppp: [wan] IPCP: SendConfigAck #119
Mar 1 10:34:13 ppp: [wan] 92.50.208.1 is OK
Mar 1 10:34:13 ppp: [wan] IPADDR 92.50.208.1
Mar 1 10:34:13 ppp: [wan] IPCP: rec'd Configure Request #119 (Req-Sent)
Mar 1 10:34:13 ppp: [wan] IPV6CP: SendConfigReq #1
Mar 1 10:34:13 ppp: [wan] IPV6CP: state change Starting --> Req-Sent
Mar 1 10:34:13 ppp: [wan] IPV6CP: Up event
Mar 1 10:34:13 ppp: [wan] SECDNS 0.0.0.0
Mar 1 10:34:13 ppp: [wan] PRIDNS 0.0.0.0
Mar 1 10:34:13 ppp: [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Mar 1 10:34:13 ppp: [wan] IPADDR 0.0.0.0
Mar 1 10:34:13 ppp: [wan] IPCP: SendConfigReq #1
Mar 1 10:34:13 ppp: [wan] IPCP: state change Starting --> Req-Sent
Mar 1 10:34:13 ppp: [wan] IPCP: Up event
Mar 1 10:34:13 ppp: [wan] IPV6CP: LayerStart
Mar 1 10:34:13 ppp: [wan] IPV6CP: state change Initial --> Starting
Mar 1 10:34:13 ppp: [wan] IPV6CP: Open event
Mar 1 10:34:13 ppp: [wan] IPCP: LayerStart
Mar 1 10:34:13 ppp: [wan] IPCP: state change Initial --> Starting
Mar 1 10:34:13 ppp: [wan] IPCP: Open event
Mar 1 10:34:13 ppp: [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Mar 1 10:34:13 ppp: [wan_link0] Link: Join bundle "wan"
Mar 1 10:34:13 ppp: [wan_link0] Link: Matched action 'bundle "wan" ""'
Mar 1 10:34:13 ppp: [wan_link0] LCP: authorization successful
Mar 1 10:34:13 ppp: [wan_link0] MESG: Login ok
Mar 1 10:34:13 ppp: [wan_link0] PAP: rec'd ACK #1 len: 13
Mar 1 10:34:13 ppp: [wan_link0] LCP: LayerUp
Mar 1 10:34:13 ppp: [wan_link0] PAP: sending REQUEST #1 len: 22
Mar 1 10:34:13 ppp: [wan_link0] PAP: using authname "USERNAME"
Mar 1 10:34:13 ppp: [wan_link0] LCP: auth: peer wants PAP, I want nothing
Mar 1 10:34:13 ppp: [wan_link0] LCP: state change Ack-Sent --> Opened
Mar 1 10:34:13 ppp: [wan_link0] MAGICNUM 0x9d0944b8
Mar 1 10:34:13 ppp: [wan_link0] MRU 1500
Mar 1 10:34:13 ppp: [wan_link0] LCP: rec'd Configure Ack #2 (Ack-Sent)
Mar 1 10:34:13 ppp: [wan_link0] MAGICNUM 0x9d0944b8
Mar 1 10:34:13 ppp: [wan_link0] MRU 1500
Mar 1 10:34:13 ppp: [wan_link0] LCP: SendConfigReq #2
Mar 1 10:34:13 ppp: [wan_link0] PROTOCOMP
Mar 1 10:34:13 ppp: [wan_link0] LCP: rec'd Configure Reject #1 (Ack-Sent)
Mar 1 10:34:13 ppp: [wan_link0] LCP: state change Req-Sent --> Ack-Sent
Mar 1 10:34:13 ppp: [wan_link0] MAGICNUM 0x1b021611
Mar 1 10:34:13 ppp: [wan_link0] AUTHPROTO PAP
Mar 1 10:34:13 ppp: [wan_link0] MRU 1500
Mar 1 10:34:13 ppp: [wan_link0] LCP: SendConfigAck #62
Mar 1 10:34:13 ppp: [wan_link0] MAGICNUM 0x1b021611
Mar 1 10:34:13 ppp: [wan_link0] AUTHPROTO PAP
Mar 1 10:34:13 ppp: [wan_link0] MRU 1500
Mar 1 10:34:13 ppp: [wan_link0] LCP: rec'd Configure Request #62 (Req-Sent)
Mar 1 10:34:13 ppp: [wan_link0] MAGICNUM 0x9d0944b8
Mar 1 10:34:13 ppp: [wan_link0] MRU 1500
Mar 1 10:34:13 ppp: [wan_link0] PROTOCOMP
Mar 1 10:34:13 ppp: [wan_link0] LCP: SendConfigReq #1
Mar 1 10:34:13 ppp: [wan_link0] LCP: state change Starting --> Req-Sent
Mar 1 10:34:13 ppp: [wan_link0] LCP: Up event
Mar 1 10:34:13 ppp: [wan_link0] Link: UP event
Mar 1 10:34:13 ppp: [wan_link0] PPPoE: connection successful
Mar 1 10:34:13 ppp: [wan_link0] PPPoE: rec'd PPP-Max-Payload '1500'
Mar 1 10:34:13 ppp: PPPoE: rec'd ACNAME "AL301"
Mar 1 10:34:07 ppp: [wan_link0] PPPoE: Connecting to '1'
Mar 1 10:34:07 ppp: [wan_link0] PPPoE: Set PPP-Max-Payload to '1500'
Mar 1 10:34:07 ppp: [wan_link0] LCP: LayerStart
Mar 1 10:34:07 ppp: [wan_link0] LCP: state change Initial --> Starting
Mar 1 10:34:07 ppp: [wan_link0] LCP: Open event
Mar 1 10:34:07 ppp: [wan_link0] Link: OPEN event
Mar 1 10:34:07 ppp: [wan] Bundle: Interface ng0 created
Mar 1 10:34:07 ppp: web: web is not running
Mar 1 10:34:07 ppp: process 99678 started, version 5.8 (root@srv-opnsense-build64 22:05 23-Feb-2016)
Mar 1 10:34:07 ppp: 
Mar 1 10:34:07 ppp: Multi-link PPP daemon for FreeBSD
Mar 1 10:34:03 ppp: process 89947 terminated
Mar 1 10:34:03 ppp: [wan_link0] Link: Shutdown


11

16.7 Legacy Series / Re: [CALL FOR TESTING] MTU > 1492 in PPPoE -- RFC 4638

« on: March 01, 2016, 08:15:54 am »

Updated, did setup wizard after factory reset, twice. The Interface>WAN shows "calculated ppp mtu : 1492"

12

16.7 Legacy Series / Re: [CALL FOR TESTING] MTU > 1492 in PPPoE -- RFC 4638

« on: February 29, 2016, 10:09:34 am »

Couldn't get it to work. I did a reboot and checked ifconfig after setting MTU 1500 in (1)Interfaces>Wan, and (2)Interfaces>PTP>pppoe-advanced. I didn't try setting 1&2 together. I didn't see anything in the GUI; I'm on the latest dev.

I noticed that the MTU info field in Interfaces>Overview>Wan/lan is missing.

13

General Discussion / Re: Gateway Monitoring

« on: October 06, 2015, 08:59:17 am »

apinger looks for (1) bad quality connection, and (2) link down. The No.1 caused such issues^ for me. This setting gives me stable connection, instead of several or more reconnections a day.

Latency threshold: 700-999
Packetl loss threshold: 80-95
Probe interval: 10
Down: 50
Avg Delay Qty: 20
Avg packet loss qty: use calculated value
Loss probe value: use calculated value

14

General Discussion / Re: WISH LIST for OPNsense

« on: June 10, 2015, 12:17:47 pm »

Mostly found in FTTx(fibre) and in some cases (v)DSL. It's an extension to PPPoE that makes up for the PPPoE overhead & thus to have MTU like LAN - therefore less segmentation. This is assuming that the WAN port is gigabit capable because the MTU is set to 1508. It's prevalent in UK and rest of the world.

RFC 4638 - Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)

OpenBSD RFC 4638 support for pppoe

15

General Discussion / Re: WISH LIST for OPNsense

« on: June 10, 2015, 07:28:50 am »

I'm not sure whether this classifies as a wish for FreeBSD or OPNsense, but here it is - baby-jumbo frames in PPPoE.