Netgate Forum

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

T

Snort Won't Start After Upgrade

pfSense Packages
• • • th3r3isnospoon

301

0
Votes

301
Posts

194.7k
Views

C

Locking this thread so it won't get hijacked over and over by numerous different issues, please start new threads instead.
A

Suricata process dying due to hyperscan problem

IDS/IPS
• • • asdjklfjkdslfdsaklj

295

2
Votes

295
Posts

70.1k
Views

T

@SteveITS said in Suricata process dying due to hyperscan problem:

https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting

Thank you for the link. This resolved my problem.

Regards,
Tim
A

ATT Internet AIr

General pfSense Questions
• • • ahole4sure

287

0
Votes

287
Posts

18.7k
Views

G

@stephenw10 I suppose it was static routing before wasn't it, so no outgoing NAT rules...
M

Asterisk 1.8 package

pfSense Packages
• • • marcelloc

281

0
Votes

281
Posts

215.7k
Views

B

Is anybody currently running asterisk on pfsense, if so, which package have you used?
B

New 502 Bad Gateway

2.4 Development Snapshots
• • • BreeOge

281

0
Votes

281
Posts

168.4k
Views

G

I am, for the first time, seeing 502 Bad Gateway. Upgraded today to the latest snapshot on my SG-3100.
I do still have internet service so I will wait a bit until someone says they have an idea.

Restarted via console, loaded very latest snapshot and now waiting to see if the issue pops up again.

As of 8PM, its an issue again. I guess I need to revert to a previous release and wait a bit for the snapshots.
K

Tak Kenal Maka Tak Sayang (Kenalan Masuk Disini)

Indonesian
• • • kambeeng

276

0
Votes

276
Posts

249.0k
Views

A

Nama : Irwansyah
Lokasi : Nias - Sumut - Indonesia
email : arpanet.nias@gmail.com
Jabatan : owner
PFSENSE : 2.4.5
Pekerjaan : kuli warnet
Warnet : ARPANET
YM: -
Facebook : facebook.com/BrowsingGaming
Tweeter: @IrwansyahMar

Salam Kenal buat semua pecinta pfsense , saya baru belajar mohon bimbingan.
Terima kasih.
S

IPtv multicast

Russian
• • • Shraik

270

0
Votes

270
Posts

335.2k
Views

W

Люди добрые подскажите по настройкам Ростелеком
igmpproxy: Warn: The source address 213.140.243.39 for group 233.3.3.35, is not in any valid net for upstream VIF. Apr 24 16:15:57 igmpproxy: Warn: The source address 213.140.243.53 for group 233.3.4.192, is not in any valid net for upstream VIF. Apr 24 16:15:59 igmpproxy: Warn: The source address 213.140.243.39 for group 233.3.3.35, is not in any valid net for upstream VIF. Apr 24 16:17:38 igmpproxy: Warn: select() failure; Errno(4): Interrupted system call Apr 24 16:17:38 igmpproxy: Note: Got a interupt signal. Exiting. Apr 24 16:17:38 igmpproxy: Note: All routes removed. Routing table is empty. Apr 24 16:17:38 igmpproxy: Note: adding VIF, Ix 0 Fl 0x0 IP 0x3200a8c0 ae0, Threshold: 1, Ratelimit: 0 Apr 24 16:17:38 igmpproxy: Note: adding VIF, Ix 1 Fl 0x0 IP 0x01000001 dc0, Threshold: 1, Ratelimit: 0 Apr 24 16:17:38 igmpproxy: Note: joinMcGroup: 224.0.0.2 on ae0 Apr 24 16:17:38 php: /services_igmpproxy.php: Started IGMP proxy service. Apr 24 16:18:10 igmpproxy: Warn: The source address 85.94.1.17 for group 224.2.2.2, is not in any valid net for upstream VIF. Apr 24 16:18:44 igmpproxy: Note: New origin for route 233.3.3.40 is 213.140.243.51, flood -1 Apr 24 16:18:50 igmpproxy: Warn: age_table_entry: SIOCGETSGCNT failing for (213.140.243.51 233.3.3.40); Errno(49): Can't assign requested address Apr 24 16:18:50 igmpproxy: Note: Removing MFC: 213.140.243.51 -> 233.3.3.40, InpVIf: 1 Apr 24 16:18:50 igmpproxy: Warn: MRT_DEL_MFC; Errno(49): Can't assign requested address Apr 24 16:19:02 igmpproxy: Warn: The source address 85.94.1.17 for group 239.77.79.84, is not in any valid net for upstream VIF. Apr 24 16:19:04 igmpproxy: Warn: The source address 85.94.1.17 for group 239.77.79.84, is not in any valid net for upstream VIF. 16:21:03.562422 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.562829 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 300 16:21:03.562848 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 255 16:21:03.565593 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.568043 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 148 16:21:03.568734 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.569626 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.569717 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.569807 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.571848 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.573139 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 63 16:21:03.575007 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.578100 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.578380 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 254 16:21:03.581539 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.581757 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.581850 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.581939 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.583447 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 174 16:21:03.584323 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.587451 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.588604 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 54 16:21:03.590601 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.593706 IP 85.94.1.17.22224 > 224.2.2.2.22224: UDP, length 1068 16:21:03.593883 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.593907 IP 85.94.1.17.22222 > 224.2.2.2.22222: UDP, length 213 16:21:03.593996 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.594094 IP 85.94.1.17.22223 > 224.2.2.2.22223: UDP, length 1068 16:21:03.961190 PPPoE [ses 0xe9ba] IP 87.240.134.115.80 > 109.161.48.88.28060: tcp 305 16:21:04.004262 PPPoE [ses 0xe9ba] IP 87.240.134.115.80 > 109.161.48.88.28060: tcp 0 16:21:04.067814 ARP, Request who-has 1.0.0.2 tell 1.0.0.1, length 28 16:21:04.068800 PPPoE [ses 0xe9ba] IP 10.131.240.4 > 109.161.48.88: ICMP host 10.131.240.4 unreachable - admin prohibited filter, length 36 16:21:04.489995 PPPoE [ses 0xe9ba] LCP, Echo-Request (0x09), id 179, length 14 16:21:04.490055 PPPoE [ses 0xe9ba] LCP, Echo-Reply (0x0a), id 179, length 14 16:21:04.719670 PPPoE [ses 0xe9ba] IP 212.34.106.254.27506 > 109.161.48.88.48832: UDP, length 67
Проблему решил!!! Верней настроил)
M

Slow DNS after 22.05

DHCP and DNS
• • • mihaifpopa

270

1
Votes

270
Posts

115.7k
Views

I

I've just updated to 23.01-RELEASE (arm) and the problem I threw into this lengthy debate appears to have gone away now.
P

New Alix board for 2013

Hardware
• • • phil.davis

265

0
Votes

265
Posts

215.8k
Views

J

Locking the topic, thanks for all the information everyone!

If you wish to add something unique then start a new thread about a specific topic regarding the APU.
Q

Seamless roaming

Off-Topic & Non-Support Discussion
• • • Qinn

265

0
Votes

265
Posts

76.0k
Views

J

@jegr

here
https://community.ui.com/releases/UAP-Firmware-4-3-23-11354/f55174e8-ec75-4ab6-b11a-822e04e5aa34?page=1

beta.png

Notice where they said they wanted beta feedback ;)

To be honest its a bit of a snafu if you ask me... Lets see if it gets removed since they released that version now..

edit: Looks like they got it sorted... I only see 5.x firmware now new 5.43.19 came out
new.png
D

NUT Package (2.8.1 and above)

UPS Tools
• • • dennypage

265

5
Votes

265
Posts

104.0k
Views

D

@incith The next release is expected switch over to the 2.8.2 production release of NUT.
S

Intel Mini-ITX Atom 8-core Hardware Build Recipe Available Here

Hardware
• • • Sir Loin

264

0
Votes

264
Posts

137.8k
Views

I

@Dazdigo:

Super micro did the same to me. They did clear the cmos but the IPMI hostname I set was the same so they are sending the same board back.

Cool. You just have to cover shipping costs to them? All you have send back is board itself, right?
M

Sarg 2.3.6 para pfsense

Portuguese
• • • marcelloc

259

0
Votes

259
Posts

119.8k
Views

L

Eu utilizava o LightSquid e na implantação da nova versão do pfSense(2.1.3) optamos por utilizar agora o SARG.
Fiquei com 2 dúvidas sobre o mesmo:

Na opção "Proxy Server", caso eu selecione SQUID eu perco as os logs das ACLS feitas no SquidGuard? Qual o padrão colocar quando tenhos os 2 pacotes instalados(Squid3-dev e SquidGuard3)?

O RealTime do LightSquid gerava o consumo de banda dos sites no exato momento de acesso. O SARG tem algum meio de habilitar isto?

Muito obrigado!
S

BOUNTY: Web GUI reprogramming

Bounties
• • • Supermule

256

0
Votes

256
Posts

156.8k
Views

K

Hi techguy,

I'm not working anymore on this theme, but if I remember well I've done a package or at least I can upload the files If u want to try. I'll update this post with the link probably tomorrow.
Z

How to get Bell Fibe in Quebec/Ontario (Internet and IPTV) working with pfSense

General pfSense Questions
• • • zax123

253

3
Votes

253
Posts

130.8k
Views

S

Code carried over from the old forum was incorrect. Check now.
Q

Sonos speakers and applications on different subnets (VLAN's)

General pfSense Questions
• • • Qinn

250

13
Votes

250
Posts

120.4k
Views

G

@nelox - for me it doesn't work at all, but maybe because I have a locked down vlan set up with default drop.

Specifically, my controllers on vlan A are whitelisted and can see and connect to anything on vlan B (where the Sonos players are). So technically there's no need to open ports from controller to Sonos Players. My issue is the other way around.

When you open the app and it goes through the multicast discovery, the Sonos player try to respond back via UDP to the controller. But unless I explicitly allow this UDP traffic from Player to Controller, it won't work, and I can see it in my logs. And given UDP is stateless, pfSense can't use the connection state, so unless I have an explicit rule, it won't work.

I tested this extensively, and in my case Sonos players usually use UDP source port in the 35000-42000 range, so that's what I used to allow traffic in pfSense.

Caveat that I'm not using UPnP, so maybe that explains the difference.
N

pfSense 22.05 breaks VLANS, restoring pfSense 22.01 fixes the issue

L2/Switching/VLANs
• • • NRgia

247

0
Votes

247
Posts

61.5k
Views

S

You should start your own thread with the details then.

Steve
X

PPPoE reconenction fix - mpd fix ($100)

Expired/Withdrawn Bounties
• • • xbipin

243

0
Votes

243
Posts

168.1k
Views

B

I believe I’m having this issue, and have been for some time now. I always wondered why sometimes PPP would drop, and I’d drive out to site only to do a reboot and everything works. Sometimes I’d even have people put on site reboot for me, but it wouldn’t work. Is there any update on this issue?

Below log is newest on top, so read in reverse.
Feb 21 09:25:12 ppp 98216 [wan] IFACE: Down event Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: LayerDown Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: SendTerminateReq #38 Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: state change Opened --> Closing Feb 21 09:25:08 ppp 98216 [wan] IPV6CP: Close event Feb 21 09:25:08 ppp 98216 [wan] IPCP: LayerDown Feb 21 09:25:08 ppp 98216 [wan] IPCP: SendTerminateReq #76 Feb 21 09:25:08 ppp 98216 [wan] IPCP: state change Opened --> Closing Feb 21 09:25:08 ppp 98216 [wan] IPCP: Close event Feb 21 09:25:08 ppp 98216 [wan] Bundle: Status update: up 0 links, total bandwidth 9600 bps Feb 21 09:25:08 ppp 98216 [wan_link0] Link: Leave bundle "wan" Feb 21 09:25:08 ppp 98216 [wan_link0] LCP: state change Opened --> Stopping Feb 21 09:25:08 ppp 98216 [wan_link0] LCP: peer not responding to echo requests Feb 21 09:25:08 ppp 98216 [wan_link0] LCP: no reply to 5 echo request(s) Feb 21 09:24:58 ppp 98216 [wan_link0] LCP: no reply to 4 echo request(s) Feb 21 09:24:48 ppp 98216 [wan_link0] LCP: no reply to 3 echo request(s) Feb 21 09:24:38 ppp 98216 [wan_link0] LCP: no reply to 2 echo request(s) Feb 21 09:24:27 ppp 98216 [wan_link0] LCP: no reply to 1 echo request(s
R

TP-LINK Smart Switches anyone?

Hardware
• • • robi

239

0
Votes

239
Posts

156.4k
Views

B

Thanks guys. I now see the distinction between Port Trunking and Ethernet Trunking. In a sense one is the inverse of the other?

And Derelict, I will give your test suggestion a work out as soon as I can.
N

pfSense on Watchguard M370

Hardware
• • • networkBob

235

1
Votes

235
Posts

73.8k
Views

S

You should see speedshift active on there already if the CPU supports it. Pretty sure the default CPU in the M670 does. That's superior to speedstep in almost every way.