Losing WAN when receiving VOIP call
-
What kind of internet connection are you using and what modem?
-
That's one of the issue I experienced in the past when trying to use Realtek NICs in FreeBSD, a sudden increase in small packets crashed the interface. You can try to use the driver from Realtek instead of the FreeBSD included one, check the hardware forum for it. Best would be to use Intel or Broadcom based NICs.
-
@chpalmer said in Losing WAN when receiving VOIP call:
What kind of internet connection are you using and what modem?
It is a fixed wireless modem from Ubiquiti. I don't have the name of it, though I could ask if that helps.
david
-
@grimson said in Losing WAN when receiving VOIP call:
That's one of the issue I experienced in the past when trying to use Realtek NICs in FreeBSD, a sudden increase in small packets crashed the interface. You can try to use the driver from Realtek instead of the FreeBSD included one, check the hardware forum for it. Best would be to use Intel or Broadcom based NICs.
I have a 4 port Intel card, just don't have a low-profile bracket for it. Ordered one so when it comes in I'll swap it over.
thanks for the suggestion.
david -
You could try the alternative Realtek driver: https://forum.netgate.com/topic/135850/official-realtek-driver-binary-1-95-for-2-4-4-release/
Steve
-
how do I verify I have a Realtek chipset?
NM: google helped me:
pciconf -lvreports all three are Realtek
-
Yes, the reX interface names confirm that.
Steve
-
Was just ruling out a Puma6 equipped modem issue.. UDP traffic on those can cause this.
-
It happened again.
I did verify that the new drivers are loaded
[2.4.4-RELEASE][admin@pfsense.home]/var/log: kldstat Id Refs Address Size Name 1 27 0xffffffff80200000 2d9a7d0 kernel 2 1 0xffffffff82f9c000 7d2c0 if_re.ko 3 1 0xffffffff833f9000 10a0 cpuctl.ko 4 1 0xffffffff833fb000 72b8 aesni.ko 5 1 0xffffffff83403000 2ec0 cryptodev.ko 6 1 0xffffffff83406000 11a0 amdtemp.ko 7 1 0xffffffff83408000 648 amdsmn.ko 8 1 0xffffffff83409000 10800 dummynet.koHere is what I see in the system.log
Oct 28 18:41:23 pfsense check_reload_status: Linkup starting re2 Oct 28 18:41:23 pfsense kernel: re2: link state changed to DOWN Oct 28 18:41:24 pfsense php-fpm[50605]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (xxx.xxx.xxx.xxx ) Oct 28 18:41:24 pfsense check_reload_status: Reloading filter Oct 28 18:41:25 pfsense php-fpm[50605]: /rc.filter_configure_sync: Gateways status could not be determined, considering all as up/active. (Group: WAN_Group1) Oct 28 18:41:26 pfsense check_reload_status: Linkup starting re2 Oct 28 18:41:26 pfsense kernel: re2: link state changed to UP Oct 28 18:41:27 pfsense php-fpm[64170]: /rc.linkup: Hotplug event detected for WAN(wan) static IP (xxx.xxx.xxx.xxx ) Oct 28 18:41:27 pfsense check_reload_status: rc.newwanip starting re2 Oct 28 18:41:27 pfsense check_reload_status: Reloading filter Oct 28 18:41:28 pfsense php-fpm[64170]: /rc.newwanip: rc.newwanip: Info: starting on re2. Oct 28 18:41:28 pfsense php-fpm[64170]: /rc.newwanip: rc.newwanip: on (IP address: xxx.xxx.xxx.xxx) (interface: WAN[wan]) (real interface: re2). Oct 28 18:41:28 pfsense check_reload_status: Reloading filter Oct 28 18:41:28 pfsense php-fpm[42540]: /rc.filter_configure_sync: Gateways status could not be determined, considering all as up/active. (Group: WAN_Group1) Oct 28 18:41:30 pfsense php-fpm[64170]: /index.php: Successful login for user 'admin' from: 192.168.1.175 (Local Database)Not sure if that helps figure out what is going on.
thanks
david -
What brand of wireless bridge radio do you have?
This comment- "I've recently been having an issue that I'm struggling to figure out"
Does this mean that it started to occur suddenly or from the first time you started using a VOIP service?
-
Not really. It shows the link went down and then came back up after 3 seconds.
I would still try to swap out re2 for a different NIC to verify the fault stays on the NIC.
What is it actually connected to? Does that log anything?
You might try adding a switch in between the WAN and whatever it's connected to. The link should never go down with that in place.
Steve
-
@chpalmer said in Losing WAN when receiving VOIP call:
What brand of wireless bridge radio do you have?
This comment- "I've recently been having an issue that I'm struggling to figure out"
Does this mean that it started to occur suddenly or from the first time you started using a VOIP service?
I've had voip on this router over a year, it just started happening.
david
-
Then ask your ISP if anything about your circuit has changed on their end. Just to cover your bases.
-
@stephenw10 said in Losing WAN when receiving VOIP call:
Not really. It shows the link went down and then came back up after 3 seconds.
I would still try to swap out re2 for a different NIC to verify the fault stays on the NIC.
What is it actually connected to? Does that log anything?
You might try adding a switch in between the WAN and whatever it's connected to. The link should never go down with that in place.
Steve
I ordered a low profile bracket and when it comes I'll remove the 2 port realtek and replace with a 4 port Intel.
I have tried swapping re1 for re2, but it never works. I tried it several times and for whatever reason re1 never works. I tired in the GUi and via command line. Now re1 works great through my failover WAN. I don't know why I can't reassign the interface. By that I mean get it to work. Pfsense says it is reassign, but it never assigns the static IP and doesn't work.
The WAN is only connected to my modem/antenna. I run pingplotter and can see that the WAN drops as soon as I answer the phone call. Interestingly I've never had it drop if I let it ring more than once :)
david
-
@chpalmer said in Losing WAN when receiving VOIP call:
Then ask your ISP if anything about your circuit has changed on their end. Just to cover your bases.
I already texted him :)
