Содержание
- Pfsense dpinger sendto error 64
- Pfsense dpinger sendto error 64
- Pfsense dpinger sendto error 64
- Pfsense dpinger sendto error 64
Pfsense dpinger sendto error 64
Evening, I have worked with Comcast to ensure router is working correctly and it is. But when I plug in to cable modem into my WAN port I get this message sendto error: 64 and no connection. I have set it to DHCP and Static many times and get the same results. Could use some help!
if you connect to the modem with a simple laptop or desktop computer, what do you see?
@mcsedude «I have set it to DHCP and Static many times and get the same results.»
by the way what does the ISP say is the connection method to the modem?
(PPPoE, dynamic IP, fix IP, IPoE, etc.)
(because it is useless to switch between DHCP and FIXED IP, if it is not the connection method)
+++edit:
an important point might even be to negotiation the pfSense box and modem ethernet port speed
Cats bury it so they can’t see it!
(You know what I mean if you have a cat)
Thank you for your response, I actually got it working. it was actually 65 error. How I got fixed it by putting 1500 into the MTU and set WAN interface hard code to 1 gig auto. It is working great now and I did a quick backup! I am actually running static IP that was assign to me by Comcast.
Источник
Pfsense dpinger sendto error 64
pfSense v2.4.4-RELEASE-p3 (amd64)
Настроен MultiWAN.
Временно отключен один из каналов.
В логах ежесекундно сыпется dpinger . sendto error: 64 
Как уменьшить количество запросов для уменьшения объёма логов?
Пробовал для шлюза так, не помогло. 
158.58.131.160 — это шлюз отключенного WAN? Если так — возможно это dpinger проверяет доступность шлюза. Probe interval у вас как раз 1000 миллисекунд.
158.58.131.160 — это шлюз отключенного WAN? Если так — возможно это dpinger проверяет доступность шлюза. Probe interval у вас как раз 1000 миллисекунд
Верно, 158.58.131.160 — это шлюз отключенного WAN.
Но 1000 миллисекунд это уже я выставил, по умолчанию там было 500.
Изменение настроек, относительно «по умолчанию», никак не влияет на интервал dping в логах.
- Обновить пф.
- Не пинговать шлюз для проверки — пинговать, напр., гуглоднс. Потому что шлюз пров-а может быть доступен, а инета может не быть.
- 1000 миллисек = 1 сек. Поставьте больше.
@ChudoBrychkin
Здр.
Самое простое , это отключить на время проверку шлюза , который физически отключен . Именно на это и указывает ошибка 64.
Источник
Pfsense dpinger sendto error 64
lan ip : 192.168.5.1/24
host ip :192.168.5.2 /24
wan ip :192.168.10.240/24
default gateway: 192.168.10.1/24
no one in 192.168.10.0 network can ping and i couldnot ping them either , unticked those two private ip blocking rules in wan interface .
gateway is shown offline but it actually works
00:14:41.245015 ARP, Request who-has 192.168.10.1 tell 192.168.10.240, length 46
00:14:41.247736 ARP, Reply 192.168.10.1 is-at 28:3b:82:fb:9a:e0, length 46
this is what packet capture shows
i have also written allow any any in both lan and wan interfaces
i tried manual nat rules and auto generated nat rules , no change
but i can ping pfsense lan and wan from the host:192.168.5.2
what am i missing ?
Ensure you stated the gateway in the WAN interface settings.
gateway is shown offline but it actually works
This basically means that the gateway doesn’t respond to pings.
If so go to System > Routing and edit the gateway to disable monitoring or set a public monitoring IP which is pingable.
It should work well with automatic outbound NAT rules.
@viragomann thanks for the response .
already tried no change still unable to connect to internet
@athish
Is the gateway status online now? If not that is the first you have to care for.
@viragomann the gateway status is offline . trying to find the reason
@athish
I wrote above, you can simply disable gateway monitoring!
@viragomann disabling gateway monitoring will show the status of the gateway online but i would be still unable to get internet . actually i already tried it.
Are you getting carrier grade NAT from your ISP? Or is there some other equipment you haven’t mentioned?
PfSense running on Qotom mini PC
i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
UniFi AC-Lite access point
I haven’t lost my mind. It’s around here. somewhere.
@athish
The gateway status must not be offline. Otherwise it is not used.
So disable the gateway monitoring and set the outbound NAT into automatic mode.
Then try a ping from pfSense itself to a public IP like 8.8.8.8 in Diagnostics > Ping. Does this fail?
@viragomann yes , i tried these already .it failed .
@athish
So I assume something in your 192.168.10.0/24 network is wrong.
Can you ping / access the gateway or public IP outside from other devices?
Are the network settings on pfSense correct?
What shows Status > interfaces?
Something in the system log?
@viragomann @jknott no , i am using the fire wall inside a private network . the gateway 192.168.10.1 is the l3 switch connecting me to internet
@viragomann other devices connected to 192.168.10.1 are getting internet . both pfsense interfaces are up . if i directly connect my pc to 192.168.10.1 .i am getting access
@viragomann
Dec 10 23:08:14 dpinger GW_WAN 192.168.10.1: sendto error: 64
Dec 10 23:08:14 dpinger GW_WAN 192.168.10.1: sendto error: 64
Dec 10 23:08:15 dpinger GW_WAN 192.168.10.1: sendto error: 64
Dec 10 23:08:15 dpinger GW_WAN 192.168.10.1: sendto error: 64
Dec 10 23:08:16 dpinger GW_WAN 192.168.10.1: sendto error: 64
Dec 10 23:08:16 dpinger GW_WAN 192.168.10.1: sendto error: 64
Dec 10 23:08:17 dpinger GW_WAN 192.168.10.1: sendto error: 64
this is what system logs gateways section says
@viragomann Dec 11 00:18:05 php-fpm 313 /interfaces.php: Unbound /var/unbound/root.key file is corrupt, removing and recreating.
DO ANYONE KNOW WHAT DOES IT MEAN
@athish system logs
Dec 11 03:59:13 kernel arpresolve: can’t allocate llinfo for 192.168.10.1 on rl0
Dec 11 03:59:14 kernel arpresolve: can’t allocate llinfo for 192.168.10.1 on rl0
Dec 11 03:59:14 kernel arpresolve: can’t allocate llinfo for 192.168.10.1 on rl0
Источник
Pfsense dpinger sendto error 64
I don’t think I have a pfsense issue here however, I am hoping I can get some help with narrowing down this issue or get some help with configuration.
My Setup is a Fiberline to my BellAliant Fiberop HomeHub 3000 -> Lan port to pfsense WAN. In hh3k, I have advance DMZ set to the mac address of pfsense and pfsense is getting an ext IP address.
About once a day I am dropping internet however, the ext ip is still showing in pfsense. Doing a release and renew is getting me the same ip but I can’t route out.
If I connect directly to my hh3k I can get internet access, so we know that it’s likely something with dmz or pfsense (I think)
Tonight I dropped around 12:30AM and rebooting pfsense, release/renew did not help. To fix I need to release ip, restart my hh3k, and pfsense gets a new ip. Looking at the monitor, I went to 100% packetloss
I’ve been playing around with the gateway on pfsense like data payload, using ext ip and even the hh3k internal ip (192.168.2.1) however, it does not seem to be helping.
Attaching pastbin of my General, Gateway and routing log
https://pastebin.com/ebFNr1Qq
Many
igb0: link state changed to DOWN
and
igb0: link state changed to UP
in there.
Try :
Give «dpinger» ** more time — change the IP (not a close to local one, but more upstream) or even disable it for a while, during testing..
** The System > Routing tab.
These options : 
Link UP/DOWN issues could also be a bad connector/cable/NIC. So swap NIC/Cable.
edit : and read this https://forum.netgate.com/topic/57419/kernel-arpresolve-can-t-allocate-llinfo-for-192-168-100-1-cable-modem
No «help me» PM’s please. Use the forum.
Thanks for the replay. I changed my Monitor IP from the internal Router to the ext gateway ip again and also enabled the «Disable Gateway Monitoring Action» for now as it seems i can send 0 payload icmp packets (ping -l 0 gateway_IP) to the actual gateway this time around.
You advised to give it more time. Do you mean the default 10/20 % values? I’ve set it to 80/99% today, but I assume that might be too high right? For now, I guess it does not really matter as I’ve Disable Gateway Monitoring Action.
8hour 
This morning I found that at the exact same time, I start to receive alerts again of 100% packet loss at 12:30. This time I had disabled the gateway actions and increased the log buffer. I did not see any outage as I was in bed, but it seemed to be working this morning when. It also looks like I got a new wanip at 01:04 and 01:50.
Because I see «sendto error: 65» and «sendto error: 64», I assume I was offline for that time?
So what exactly does the gateway monitor do if it was enabled vs disabled and recovering on its own?
An hour later, i get a new wanip
Maybe this is a coincidence however, both times before everything goes down, Suricata started to update.
So I finally found the cause for this issue, Its Suricata or my hardware + Suricata is not playing nice. Currently, Suricata is set to update at 00:30, which was what caught my eye. I changed the time to something different the issue moved to +- a few minuets. Next up, I went into Suricata and did some updates, changes, saves and that also causes the network to drop.
The only workaround when I drop, is to restart the Bell Home Hub 3000 (hh3k).
I’ve since uninstalled Suricata and installed Snort and the issues gone. Any ideas here? The plan is still to replace the dual E5520’s for one 6000 series to get Crypto support.
CPU Type Intel(R) Xeon(R) CPU E5520 @ 2.27GHz
16 CPUs: 2 package(s) x 4 core(s) x 2 hardware threads
AES-NI CPU Crypto: No
Memory usage
4% of 18377 MiB
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
Is there a way to restart or cycle the interface to see if that alone will also cause issues? i no-longer have Suricata installed at this point.
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
Is there a way to restart or cycle the interface to see if that alone will also cause issues? i no-longer have Suricata installed at this point.
Sure, you can disable and then re-enable the interface on the INTERFACES menu in pfSense. That will not use netmap, though. That will simply cycle the interface down and back up.
Источник
Topic: Unable to get dpinger to work on WAN ipv6 link local address (Read 10193 times)
New user to opnsense.
My WAN ipv6 gateway is a link local address and dpinger shows the gateway down.
In the Gateway Logs I see:
2020-05-25T20:46:37 dpinger: WAN_DHCP6 fe80::201:5cff:fe76:b846%hn0: sendto error: 65
If I try to ping I get:
# /sbin/ping6 -S 'fe80::21f:e1ff:fe10:e676%hn0' -c '3' 'fe80::201:5cff:fe76:b846'
PING6(56=40+8+8 bytes) fe80::21f:e1ff:fe10:e676%hn0 --> fe80::201:5cff:fe76:b846%hn0
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
--- fe80::201:5cff:fe76:b846 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
It seems to me that something is wrong with the route for link local on the WAN interface?
Logged
What’s your ISP?
Can you check in your /tmp/ folder. and look for a *_routerv6 file, does it exist?
p.s following your thread on the pfSense forum — multiple-ipv6-capable-connections, interesting.
« Last Edit: May 26, 2020, 08:20:53 am by marjohn56 »
Logged
OPNsense 21.7 — Qotom Q355G4 — ISP — Community Fibre 1Gbps.
Team Rebellion Member — If we’ve helped you remember to applaud
Also, can you post the output of netstat -6rW. Obfuscate any gua addresses, just interested in the default route.
Logged
OPNsense 21.7 — Qotom Q355G4 — ISP — Community Fibre 1Gbps.
Team Rebellion Member — If we’ve helped you remember to applaud
I have the same problem with the ipv6 link-local address. I changed it to one of the google dns ipv6 addresses and it has worked since, modulo other problems with dpinger.
Logged
What’s your ISP?
Can you check in your /tmp/ folder. and look for a *_routerv6 file, does it exist?
p.s following your thread on the pfSense forum — multiple-ipv6-capable-connections, interesting.
ISP is Time Warner/Spectrum in Southern California.
The file hn0_routerv6 does exist, its contents are:
fe80::201:5cff:fe76:b846
which is the gateway of the ISP
Logged
Also, can you post the output of netstat -6rW. Obfuscate any gua addresses, just interested in the default route.
root@OPNsense:~ # netstat -6rW
Routing tables
Internet6:
Destination Gateway Flags Use Mtu Netif Expire
default fe80::201:5cff:fe76:b846%hn0 UG 111414 1500 hn0
localhost link#1 UH 0 16384 lo0
64:ff9b::/96 fd04:6ddc:fe8e:2364:15:5dff:feff:2b04 UGS 35 1500 hn4
64:ff9b::424a:d401 fd04:6ddc:fe8e:2364:15:5dff:feff:2b04 UGHS 42464 1500 hn4
dns.google fe80::201:5cff:fe76:b846%hn0 UGHS 42480 1500 hn0
2605:e000:abcd:ef10::/64 link#6 U 27147 1500 hn1
2605:e000:abcd:ef10:15:5dff:feff:2b00 link#6 UHS 0 16384 lo0
2605:e000:abcd:ef20::/64 link#7 U 0 1500 hn2
OPNsense link#7 UHS 0 16384 lo0
2605:e000:abcd:ef30::/64 link#8 U 6858 1500 hn3
2605:e000:abcd:ef30:15:5dff:feff:2b02 link#8 UHS 0 16384 lo0
2605:e000:abcd:ef64::/64 link#9 U 0 1500 hn4
2605:e000:abcd:ef64:15:5dff:feff:2b03 link#9 UHS 0 16384 lo0
OPNsense link#5 UHS 0 16384 lo0
fd04:6ddc:fe8e:2310::/64 link#6 U 0 1500 hn1
OPNsense link#6 UHS 0 16384 lo0
fd04:6ddc:fe8e:2330::/64 link#8 U 2851 1500 hn3
OPNsense link#8 UHS 0 16384 lo0
fd04:6ddc:fe8e:2364::/64 link#9 U 44377 1500 hn4
OPNsense link#9 UHS 0 16384 lo0
fe80::%lo0/64 link#1 U 0 16384 lo0
fe80::1%lo0 link#1 UHS 0 16384 lo0
fe80::%hn0/64 link#5 U 25 1500 hn0
fe80::21f:e1ff:fe10:e676%hn0 link#5 UHS 0 16384 lo0
fe80::%hn1/64 link#6 U 1614 1500 hn1
fe80::15:5dff:feff:2b00%hn1 link#6 UHS 0 16384 lo0
fe80::%hn2/64 link#7 U 0 1500 hn2
fe80::15:5dff:feff:2b01%hn2 link#7 UHS 0 16384 lo0
fe80::%hn3/64 link#8 U 4126 1500 hn3
fe80::15:5dff:feff:2b02%hn3 link#8 UHS 0 16384 lo0
fe80::%hn4/64 link#9 U 3482 1500 hn4
fe80::15:5dff:feff:2b03%hn4 link#9 UHS 0 16384 lo0
root@OPNsense:~ #
Logged
I have the same problem with the ipv6 link-local address. I changed it to one of the google dns ipv6 addresses and it has worked since, modulo other problems with dpinger.
That is what I have done temporarily, but it should work.
Link Local Addresses are the most common gateways that I have seen.
It worked with pfsense, so something different here.
Logged
Can you do:
# ps auxw | grep dpinger
post the v6 entry… ta..
Logged
OPNsense 21.7 — Qotom Q355G4 — ISP — Community Fibre 1Gbps.
Team Rebellion Member — If we’ve helped you remember to applaud
Sorry.. read the last message from you just after I posted. Can you post the none working and the working ps -auxw ….
« Last Edit: May 26, 2020, 07:38:15 pm by marjohn56 »
Logged
OPNsense 21.7 — Qotom Q355G4 — ISP — Community Fibre 1Gbps.
Team Rebellion Member — If we’ve helped you remember to applaud
Can you do:
# ps auxw | grep dpinger
post the v6 entry… ta..
root 50166 0.0 0.1 11008 2468 - Is 10:40 0:00.01 /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP6 -B fe80::21f:e1ff:fe10:e676%hn0 -p /var/run/dpinger_WAN_DHCP6.pid -u /var/run/dpinger_WAN_DHCP6.sock -C /usr/local/etc/rc.syshook monitor -s 1s -l 2s -t 60s -A 1s -D 500 -L 20 -d 0 fe80::201:5cff:fe76:b846%hn0
Logged
Just to eliminate the firewall, I added a rule to WAN passing LLA to LLA out,
Then tried pinging using WAN interface, I can see in the firewall log, it passing out, but no response.
Logged
Sorry.. read the last message from you just after I posted. Can you post the none working and the working ps -auxw ….
Working using Google DNS as the monitor:
root@OPNsense:~ # ps auxw | grep dpinger
root 369 0.0 0.1 6912 2356 - Is 10:37 0:00.02 /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP6 -B 2605:e000:ffc0:3a:3583:9dcc:d43b:b16e -p /var/run/dpinger_WAN_DHCP6.pid -u /var/run/dpinger_WAN_DHCP6.sock -C /usr/local/etc/rc.syshook monitor -s 1s -l 2s -t 60s -A 1s -D 500 -L 20 -d 0 2001:4860:4860::8844
Non-Working using default gateway:
root 50166 0.0 0.1 11008 2468 - Is 10:40 0:00.01 /usr/local/bin/dpinger -f -S -r 0 -i WAN_DHCP6 -B fe80::21f:e1ff:fe10:e676%hn0 -p /var/run/dpinger_WAN_DHCP6.pid -u /var/run/dpinger_WAN_DHCP6.sock -C /usr/local/etc/rc.syshook monitor -s 1s -l 2s -t 60s -A 1s -D 500 -L 20 -d 0 fe80::201:5cff:fe76:b846%hn0
Logged
Even more bizarre is this > My primary router works to my ISP using the link local address — ping or dpinger. My secondary test router to the primary router using link-local address does not 
.
Logged
OPNsense 21.7 — Qotom Q355G4 — ISP — Community Fibre 1Gbps.
Team Rebellion Member — If we’ve helped you remember to applaud
I am not sure if this is a valid test or not, but I opened 2 windows of opensense. One is doing packet capture my link local ip (fe80::21f:e1ff:fe10:e676) as host to capture.
the other window tried to ping. This is result:
# /sbin/ping6 -S 'fe80::21f:e1ff:fe10:e676%hn0' -c '3' 'fe80::201:5cff:fe76:b846'
PING6(56=40+8+8 bytes) fe80::21f:e1ff:fe10:e676%hn0 --> fe80::201:5cff:fe76:b846%hn0
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
ping6: wrote fe80::201:5cff:fe76:b846 16 chars, ret=-1
--- fe80::201:5cff:fe76:b846 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
The capture was empty.
Logged
Well a lightbulb came on… VLANs… my primary LANs are all VLANs. So I was then able to ping out from the primary to the test router OK, but of course, not the other way.
Anyway.. I’ll play with this tomorrow…
Logged
OPNsense 21.7 — Qotom Q355G4 — ISP — Community Fibre 1Gbps.
Team Rebellion Member — If we’ve helped you remember to applaud
Yogurt-Filled Chocolate Cauldrons
Cute chocolate «cauldrons» hold a cool, creamy orange-flavored yogurt in this recipe. The unfilled cups…
Provided by Taste of Home
Demi-Glace
This is my technique for veal demi-glace, and there’s not much to it. I’m going for a pure veal stock…
Provided by Chef John
Easy Butterfinger Cake
OMG!!! I had to make this cake this past Sunday for my Mary Kay party.. It was a huge hit. It was also…
Provided by vicky hunt
Pork Neck Slow Cooker Stew
Good food doesn’t always have to cost a fortune! Your family will love this. Full of flavor and easy…
Provided by Melissa Baldan
Steamed Parsley Red Potatoes
This is a very good potato dish , I stem baby red potatoes and smother them in real butter and parsley…
Provided by Karla Everett
Homemade Chicken Pot Pie
Sure you can make a quick Chicken Pot Pie using already made pie crust, canned soups, vegetables and…
Provided by Julia Ferguson
Red Velvet Pound Cake
This delicious red velvet pound cake is the perfect combination of flavors. Make sure the cake has cooled…
Provided by Taste of Home
Boudreaux’s Zydeco Stomp Gumbo
Dis is da toe curlin Texicajun hybrid of a classic dish. This will put a smile on everyone’s face that’s…
Provided by Lupe Boudreaux
Pesto Baked Pork Chops
This is a tender and delicious baked pork chop recipe, with an Italian flair.
Provided by larvia57
Previous
Next
MY FIX FOR PFSENSE DISCONNECTING WAN CONNECTION …
WebMy fix for pfSense disconnecting WAN connection every 30 minutes on the clock, dpinger in the log, but dhclient is the culprit. by Nick on October 29, 2021 I’ve literally tried everything, downgrading to an older version …
From meteen.info
See details »
SENDTO ERROR: 64 | NETGATE FORUM
WebJul 11, 2020 sendto error: 64 Installation and Upgrades 2 3 2.2k Log in to reply M mcsedude Jul 11, 2020, 8:56 PM Evening, I have worked with Comcast to ensure router …
From forum.netgate.com
Estimated Reading Time 1 min
See details »
R/PFSENSE — PFSENSE ERROR WITH ALL WAN LINKS — SENDTO ERROR: 55
WebBasically what pfSense is telling you is you is that it has a lot of packetloss on the VPN connection… That is because your WAN connection is also going down or with a lot of …
From reddit.com
See details »
DPINGER PROBLEMS. “SENDTO ERROR: 13”? : R/PFSENSE — REDDIT
WebAnimals and Pets Anime Art Cars and Motor Vehicles Crafts and DIY Culture, Race, and Ethnicity Ethics and Philosophy Fashion Food and Drink History Hobbies Law Learning …
From reddit.com
See details »
SYSTEM LOG ERROR: OPT1GW SENDTO ERROR 64 : R/PFSENSE — REDDIT
WebYet another update… added a Noctua NF-A14 FLX fan connected to a TP-Link TL-POE10R PoE splitter for active cooling of the Enterprise 8 PoE switch. Temperature went down …
From reddit.com
See details »
MULTI WAN PROBLEM WITH 2ND GATEWAY (DPINGER: WAN2_DHCP …
WebApr 5, 2019 Re: Multi WAN problem with 2nd gateway (dpinger: WAN2_DHCP 8.8.4.4: sendto error: 22. hmm, you are correct. WAN2 is a 4G LTE modem in bridge mode with …
From forum.opnsense.org
See details »
GATEWAY — SEND TO ERROR 65 | NETGATE FORUM
WebApr 20, 2016 pfSense WAN did not lose link and still has a valid lease so there is no reason for it to ask for a renewal Rebooting your modem to fix whatever your ISP did is …
From forum.netgate.com
See details »
SONIC.NET • «SENDTO ERROR: 65» ON PFSENSE ROUTER
WebFeb 25, 2021 I’ve seen this error before but it’s been quite a while. Assuming you’ve rebooted your ONT/modem and pfSense, have you checked to ensure the WAN …
From forums.sonic.net
See details »
ROUTING — GATEWAY SETTINGS | PFSENSE DOCUMENTATION
WebJan 19, 2023 To conserve bandwidth, the dpinger daemon sends a ping with a payload size of 0 by default so that no data is contained within the ICMP echo request. However, …
From docs.netgate.com
See details »
DPINGER SEND TO ERROR 65 : R/PFSENSE — REDDIT
WebAnimals and Pets Anime Art Cars and Motor Vehicles Crafts and DIY Culture, Race, and Ethnicity Ethics and Philosophy Fashion Food and Drink History Hobbies Law Learning …
From reddit.com
See details »
GATEWAY LOG ENTRIES SHOWING HUNDREDS OF «DPINGER» PROCESS WITH …
WebBase on Netgate documentation under the section «Payload» by default dpinger sends ping with a payload size of zero. Some ISP doesn’t like that. I believe this is what is …
From reddit.com
See details »
SEND TO ERROR 65 : R/PFSENSE — REDDIT
WebSoon as I reboot pfsense box the Internet is fine but before doing so I did attempt disabling the wan interface and re-enabling it to see if the internet would stick but upon doing that …
From reddit.com
See details »
Related Search
Sendto error 64 pfsense
pfSense v2.4.4-RELEASE-p3 (amd64)
Настроен MultiWAN.
Временно отключен один из каналов.
В логах ежесекундно сыпется dpinger . sendto error: 64
Как уменьшить количество запросов для уменьшения объёма логов?
Пробовал для шлюза так, не помогло.
158.58.131.160 — это шлюз отключенного WAN? Если так — возможно это dpinger проверяет доступность шлюза. Probe interval у вас как раз 1000 миллисекунд.
158.58.131.160 — это шлюз отключенного WAN? Если так — возможно это dpinger проверяет доступность шлюза. Probe interval у вас как раз 1000 миллисекунд
Верно, 158.58.131.160 — это шлюз отключенного WAN.
Но 1000 миллисекунд это уже я выставил, по умолчанию там было 500.
Изменение настроек, относительно «по умолчанию», никак не влияет на интервал dping в логах.
- Обновить пф.
- Не пинговать шлюз для проверки — пинговать, напр., гуглоднс. Потому что шлюз пров-а может быть доступен, а инета может не быть.
- 1000 миллисек = 1 сек. Поставьте больше.
@ChudoBrychkin
Здр.
Самое простое , это отключить на время проверку шлюза , который физически отключен . Именно на это и указывает ошибка 64.
Источник
Sendto error 64 pfsense
I don’t think I have a pfsense issue here however, I am hoping I can get some help with narrowing down this issue or get some help with configuration.
My Setup is a Fiberline to my BellAliant Fiberop HomeHub 3000 -> Lan port to pfsense WAN. In hh3k, I have advance DMZ set to the mac address of pfsense and pfsense is getting an ext IP address.
About once a day I am dropping internet however, the ext ip is still showing in pfsense. Doing a release and renew is getting me the same ip but I can’t route out.
If I connect directly to my hh3k I can get internet access, so we know that it’s likely something with dmz or pfsense (I think)
Tonight I dropped around 12:30AM and rebooting pfsense, release/renew did not help. To fix I need to release ip, restart my hh3k, and pfsense gets a new ip. Looking at the monitor, I went to 100% packetloss
I’ve been playing around with the gateway on pfsense like data payload, using ext ip and even the hh3k internal ip (192.168.2.1) however, it does not seem to be helping.
Attaching pastbin of my General, Gateway and routing log
https://pastebin.com/ebFNr1Qq
Many
igb0: link state changed to DOWN
and
igb0: link state changed to UP
in there.
Try :
Give «dpinger» ** more time — change the IP (not a close to local one, but more upstream) or even disable it for a while, during testing..
** The System > Routing tab.
These options :
Link UP/DOWN issues could also be a bad connector/cable/NIC. So swap NIC/Cable.
edit : and read this https://forum.netgate.com/topic/57419/kernel-arpresolve-can-t-allocate-llinfo-for-192-168-100-1-cable-modem
No «help me» PM’s please. Use the forum.
Thanks for the replay. I changed my Monitor IP from the internal Router to the ext gateway ip again and also enabled the «Disable Gateway Monitoring Action» for now as it seems i can send 0 payload icmp packets (ping -l 0 gateway_IP) to the actual gateway this time around.
You advised to give it more time. Do you mean the default 10/20 % values? I’ve set it to 80/99% today, but I assume that might be too high right? For now, I guess it does not really matter as I’ve Disable Gateway Monitoring Action.
8hour
This morning I found that at the exact same time, I start to receive alerts again of 100% packet loss at 12:30. This time I had disabled the gateway actions and increased the log buffer. I did not see any outage as I was in bed, but it seemed to be working this morning when. It also looks like I got a new wanip at 01:04 and 01:50.
Because I see «sendto error: 65» and «sendto error: 64», I assume I was offline for that time?
So what exactly does the gateway monitor do if it was enabled vs disabled and recovering on its own?
An hour later, i get a new wanip
Maybe this is a coincidence however, both times before everything goes down, Suricata started to update.
So I finally found the cause for this issue, Its Suricata or my hardware + Suricata is not playing nice. Currently, Suricata is set to update at 00:30, which was what caught my eye. I changed the time to something different the issue moved to +- a few minuets. Next up, I went into Suricata and did some updates, changes, saves and that also causes the network to drop.
The only workaround when I drop, is to restart the Bell Home Hub 3000 (hh3k).
I’ve since uninstalled Suricata and installed Snort and the issues gone. Any ideas here? The plan is still to replace the dual E5520’s for one 6000 series to get Crypto support.
CPU Type Intel(R) Xeon(R) CPU E5520 @ 2.27GHz
16 CPUs: 2 package(s) x 4 core(s) x 2 hardware threads
AES-NI CPU Crypto: No
Memory usage
4% of 18377 MiB
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
Is there a way to restart or cycle the interface to see if that alone will also cause issues? i no-longer have Suricata installed at this point.
If Snort works, then just use it instead of Suricata. There is no meaningful security difference between the two packages.
Were you running Suricata with Inline IPS Mode? If so, then netmap is probably the issue as it will restart an interface when netmap mode is activated. So each time Suricata stopped and started it would activate netmap which in turn will cycle the interface. The Inline IPS Mode of blocking in Suricata uses Netmap. The Legacy Blocking Mode in Suricata works the same as Snort and uses libpcap instead of netmap.
Is there a way to restart or cycle the interface to see if that alone will also cause issues? i no-longer have Suricata installed at this point.
Sure, you can disable and then re-enable the interface on the INTERFACES menu in pfSense. That will not use netmap, though. That will simply cycle the interface down and back up.
Источник
Sendto error 64 pfsense
My friend’s new install of pfSense so far had experienced two nights around 9.25pm a scenario where WAN still has an IP but is offline and the log is sento error 64. The doc says:
sendto error: 64
64 EHOSTDOWN
Host is down.
A socket operation failed because the destination host was down.
In this case, the firewall is unable to reach the a target host directly connected at layer 2 (No ARP response), or it received a similar error response from an upstream source. Generally this only happens due to remote problems, indicating that the target is actually down or the L1/L2 link to the target is down.
Is there anything we could do at L1/L2 level on our end to prevent this? A reboot restores WAN. My friend is not pfSense savvy and will find this annoying for his wife. So, I am wondering whether a DHCP time increase could resolve
pfSense+ 22.01 Lenovo Thinkcentre M93P SFF Quadcore i7 Raid-ZFS 128GB-SSD 32GB-RAM PCI-dual Intel i350 NIC.
Like it says that means there’s something not responding to ARP. Does the gateway IP disappear from the ARP table when that happens?
A DHCP lease time decrease is more likely to resolve it I would think. Though it could be something more basic like something upstream losing link. If you disconnect/reconnect the WAN does it start working again?
@stephenw10 I see if it does it again tonight and if it does, I’ll check the ARP table and disconnect/reconnect. Some say disable monitoring or auto negotiate or manual MTU, but auto negotiate (speed and duplex) and MTu are already default.
pfSense+ 22.01 Lenovo Thinkcentre M93P SFF Quadcore i7 Raid-ZFS 128GB-SSD 32GB-RAM PCI-dual Intel i350 NIC.
Well, late yesterday up till 19 minutes and 44 sec pass midnight, we were getting lots of sent to error 65 and some latency alarm; so, this morning spoke with ISP and it was their fault doing some update. We have fiber and no modem. It appears all is good.
pfSense+ 22.01 Lenovo Thinkcentre M93P SFF Quadcore i7 Raid-ZFS 128GB-SSD 32GB-RAM PCI-dual Intel i350 NIC.
Источник
Sendto error 64 pfsense
Evening, I have worked with Comcast to ensure router is working correctly and it is. But when I plug in to cable modem into my WAN port I get this message sendto error: 64 and no connection. I have set it to DHCP and Static many times and get the same results. Could use some help!
if you connect to the modem with a simple laptop or desktop computer, what do you see?
@mcsedude «I have set it to DHCP and Static many times and get the same results.»
by the way what does the ISP say is the connection method to the modem?
(PPPoE, dynamic IP, fix IP, IPoE, etc.)
(because it is useless to switch between DHCP and FIXED IP, if it is not the connection method)
+++edit:
an important point might even be to negotiation the pfSense box and modem ethernet port speed
Cats bury it so they can’t see it!
(You know what I mean if you have a cat)
Thank you for your response, I actually got it working. it was actually 65 error. How I got fixed it by putting 1500 into the MTU and set WAN interface hard code to 1 gig auto. It is working great now and I did a quick backup! I am actually running static IP that was assign to me by Comcast.
Источник
Sendto error 64 pfsense
Hello there! I’ve into an issue for a while with no real solution or clear explanation of what is happening with the installation. First of all my installation includes these next items:
Dell r430 server
KVM
pfsense 2.4.3
I have a few interfaces and one of them has several VLANs associated with it. After running the firewall for a while the parent interface IP address, which is hosted on the firewall(pfsense), becomes unreachable and sequentially all VLANs associated with become unreachable. Therefore I’m seeking for real help with this issue.
Also I have to tell that the interface of KVM’s pfsense parent is set to «direct», and «bridge».
Kindly check the attachments for a snapshot of the VLANs when they become offline.
Thanks in advance
Do you have disabled the hardware checksum offloading as described here https://doc.pfsense.org/index.php/Virtualizing_pfSense_on_Proxmox?
What kind of virtual NICs are you using?
Something respective in the logs?
Thanks for the reply.. I will enable that option(disabling hardware offloading) and observer for it.
Thank you once again!
Did it help? *(disabling checksum offload) — because it did not seem to help in my case.
Thanks for the suggestion. Till now it seems that the issue has been fixed! I’m still observing the firewall and I will update this thread in case there is an update. Thank you once again for the quick and smart suggestion.
Hello there! Unfortunately the issue occurred again today. But this time it took a relatively long time in comparison to the other periods I’ve been observing for a while. Regarding your question about the kind of VNICs I am using, I use this configuration for the interfaces
and you asked for logs but I couldn’t determine which logs you exactly need. Therefore, could you please be more specific regarding the logs that you need.
Thanks in advance
I meant the system log. Status > System Logs > System > General
If there are some issues related to interface drop-outs you should find log entries there.
pfSense works better with an e1000 NICs than with the rtl, but don’t know, if that helps here.
I can’t use «e1000» NICs as the firewall VLANs become offline after applying the changes for the new option(which is «e1000»). Any suggestion?
As far as I know, the e1000 supports VLAN. .
I’m using virtIO NICs with my virtualized pfSense on KVM without no issue, since I’ve deactivated checksum offloading. And I’ve also defined multiple VLANs on one NIC.
I am still trying to fix this problem although I’m not pretty sure whether it has been solved! Anyway, may you share with me your KVM configuration regarding the interfaces parts?
Here’s the interface setting of the virtual machine interface, where I’m running multiple vLANs on in pfSense:
BOOTPROTO=’none’
BRIDGE=’yes’
BRIDGE_FORWARDDELAY=’0′
BRIDGE_PORTS=’eth2′
BRIDGE_STP=’off’
BROADCAST=»
ETHTOOL_OPTIONS=»
IPADDR=»
MTU=»
NAME=»
NETMASK=»
NETWORK=»
REMOTE_IPADDR=»
STARTMODE=’auto’
BOOTPROTO=’none’
BROADCAST=»
DHCLIENT_SET_DEFAULT_ROUTE=’no’
ETHTOOL_OPTIONS=»
IPADDR=»
MTU=»
NAME=’I211 Gigabit Network Connection’
NETMASK=»
NETWORK=»
REMOTE_IPADDR=»
STARTMODE=’auto’
PREFIXLEN=»
Thank you for sharing this with me. I will double check the settings of mine as well as of yours and update my settings accordingly. I will update this thread if there is any update.
Hello there! Unfortunately the problem occurred again today. For those of you who are asking for «system logs» here are what I got
May 16 09:21:20 dpinger WB_MAJ_BNS1 172.16.6.24: sendto error: 64
May 16 09:21:20 dpinger WB_RD2 172.16.6.2: sendto error: 64
May 16 09:21:20 dpinger WB_EDU 172.16.6.21: sendto error: 64
May 16 09:21:20 dpinger WB_RD3 172.16.6.3: sendto error: 64
May 16 09:21:20 dpinger WB_OFF 172.16.6.22: sendto error: 64
May 16 09:21:20 dpinger WB_RD1 172.16.6.1: sendto error: 64
May 16 09:21:20 dpinger WB_OOF_BNS 172.16.6.28: sendto error: 64
May 16 09:21:20 dpinger WB_WAHO 172.16.6.27: sendto error: 64
May 16 09:21:20 dpinger LANs_Bridge 172.16.101.10: sendto error: 64
May 16 09:21:20 dpinger WB_RD2 172.16.6.2: sendto error: 64
May 16 09:21:20 dpinger WB_MAJ_BNS1 172.16.6.24: sendto error: 64
May 16 09:21:20 dpinger WB_EDU 172.16.6.21: sendto error: 64
May 16 09:21:20 dpinger WB_RD3 172.16.6.3: sendto error: 64
May 16 09:21:20 dpinger WB_OFF 172.16.6.22: sendto error: 64
May 16 09:21:20 dpinger WB_RD1 172.16.6.1: sendto error: 64
May 16 09:21:19 dpinger WB_OOF_BNS 172.16.6.28: sendto error: 64
May 16 09:21:19 dpinger WB_WAHO 172.16.6.27: sendto error: 64
May 16 09:21:19 dpinger LANs_Bridge 172.16.101.10: sendto error: 64
May 16 09:21:19 dpinger WB_MAJ_BNS1 172.16.6.24: sendto error: 64
May 16 09:21:19 dpinger WB_RD2 172.16.6.2: sendto error: 64
May 16 09:21:19 dpinger WB_EDU 172.16.6.21: sendto error: 64
May 16 09:21:19 dpinger WB_RD3 172.16.6.3: sendto error: 64
May 16 09:21:19 dpinger WB_OFF 172.16.6.22: sendto error: 64
Источник