(SOLVED) Link State Up Down
-
I have two intel pro1000's coming, they will be going in stat. I am going to be testing the D-link tomorrow, I tend to think the problem is with the Realtek rl() driver and card quality in FreeBSD/pfsense 2.1.3.
I just want to make sure that I am not overlooking something simple.
I will test the d-link, and put in the two new cards. I will also check on the speed negotiation as well, that's a good idea too. Anything else I should try?
-
Giving an update.
I changed the speed to 100 duplex. I also moved my network traffic off the firewall. I kept the two static IP's for the phone connected to the firewall. I am getting them dropping calls either way. It doesn't seem to happen as often with less traffic on the line (understandably).
I am replacing the cards in my pfsense box with the intel pro1000 cards I ordered. But I don't know, or haven't figured out, if the Realtek cards are acting strange under the load, or if the D-Link is acting weird for the same reason. It does appear that once a packet or two gets rejected the calls all behave like they have been hung up. The continuous ping I have been running shows two missed pings, then back to normal.
-
Is there a graph for dropped packets with time? I know what times it drops out, and I know what happens when it drops (rl1 shows DOWN, then UP) But I don't know what I should be looking for when looking for the reason that it disconnects/reconnects.
-
Still doing it with the new adapters, is only on the LAN side. It must be the router outside my firewall. Any ideas to check it?
Jun 13 16:21:37 check_reload_status: Linkup starting em1
Jun 13 16:21:37 kernel: em1: link state changed to DOWN
Jun 13 16:21:38 check_reload_status: Linkup starting em1
Jun 13 16:21:38 kernel: em1: link state changed to UP
Jun 13 16:21:39 php: rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.0.1 )
Jun 13 16:21:41 php: rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.0.1 )
Jun 13 16:21:41 check_reload_status: rc.newwanip starting em1
Jun 13 16:21:44 php: rc.newwanip: rc.newwanip: Informational is starting em1.
Jun 13 16:21:44 php: rc.newwanip: rc.newwanip: on (IP address: 192.168.0.1) (interface: LAN[lan]) (real interface: em1).
Jun 13 16:21:44 check_reload_status: Reloading filter -
Sorry for going off-topic, but where did you get that log?
If I were you, I would connect a client to LAN side of router and do ping host -t
-
I have personally experienced a few d-link routers with bad PSUs that did 'weird' stuff.
Try removing the d-link router or running it purely as a switch. You'll only have one subnet, though it's not obvious reading back whether that's what you have anyway.Steve
-
OrientalSniper: its under Status/System Logs, its the main log. There are several other logs in there too.
Steve, I am going to try it with a gigabit switch. That makes sense. I do only have one subnet, so it should work. For the short-term I may leave the data side of the network off the firewall and focus on getting the phones constant, maybe I will put it all on that switch and see if it still goes bonkers. People don't complain about the internet dropping nearly as hard as they complain about having phone calls drop.
-
Are you using the DIR-615 purely to get extra ports to connect to the pfSense LAN interface then? As a wireless access point also?
If so you should just chnage it into an access point and switch by connecting the pfSense LAN directly to one of the D-Link LAN jacks and disabling DHCP on the D-link. Removing any routing/firewall function from the D-link is one less thing that might be causing a problem. See:
https://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSenseSteve
-
It's like you can see my setup. I actually was using the dir615 as a wireless access point with the Wan port disconnected just like you said. I had DHCP turned off and had the two phone, one data, and the LAN from pfsense all hooked up to LAN ports with nothing on the wan. Basically using it as a switch with wireless access. I should have mentioned that.
I still think the dir615 is still the failing component.
I went back in today and put in a Netgear Gigabit switch, everything was testing ok. No packet loss and i was able to stay on a call for over an hour. I won't know for certain until the system is under high load on Monday. I connected the dir615 to my data network strictly as an access point.
Thank you for hanging with me on this one, I appreciate it more than you can imagine.
-
Some wireless routers have an access-point only mode, that might be worth investigating. The D-link might be doing something odd if it thinks its WAN is down all the time. If the Netgear works out OK it seems you've found the problem. :) You can always connect the D-link to it get wifi back.
Steve
-
Finally back with one week of testing.
I replaced my wireless router with a gigabit switch and then connected the router back into the network as a wireless access point farther downstream.
Seems to have worked well. The router must have gotten all weird with heavy load.
Thank you all for suggestions and help. It was the difference between failure and getting this thing fixed.
