A little support for a home user.

badfrogg

Looks like you're saying that the Realtek RTL8111E need to have a different driver loaded. That is not something I feel comfortable doing. The router works 99% of the time and that is much better then 0% if I screw it up. Also the original post is from 2009. Will the driver still be compatible?

Think I will just have to buy a proper router. It would have been cool to make this old scrap work though.

NollipfSense

@badfrogg If you can just add an Intel NIC, that's all you need. It appears that you have two empty PCI slots available ... you can add an Intel pro/1000 or i350, cheap on eBay and it's plug & play ... you should be able to handle that ... nothing wrong with the computer, it just has terrible NIC. I would use the PCIe slot and if you can remove the Realtek card that would be great.
https://www.ebay.com/sch/i.html?_from=R40&_trksid=p2060353.m570.l1313.TR11.TRC1.A0.H0.XIntel+NIC.TRS0&_nkw=Intel+NIC&_sacat=0

badfrogg

I did finally try this again. I built another system using much better parts...


May 31 08:53:17	kernel		arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx on em0
May 31 08:53:17	kernel		arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx on em0
May 31 08:53:17	kernel		arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx on em0
May 31 08:53:17	kernel		arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx on em0

And I have pretty much the exact same problem as far as I can tell. Internet drops once or twice a day for a minute or two. I used a dell branded pro / 1000 card (dual) nic card and the mother board is an Intel DQ77KB with an i7-3770S and 16gb ddr3.

I could not afford to spend money on a new router just yet. I got this stuff out of the recycle bin too.

If anyone could help it would be awesome.

badfrogg

I searched "arpresolve: can't allocate llinfo for" and I don't think it is a hardware problem. Seems like its is a WAN DHCP thing and some compatibility issue with my cable modem and pfsense. People with Natgate branded boxes are having the same issue. But none of those posts seem to ever result in a clear way of fixing it. Some folks say that buying a static IP or changing ISPs does it. Some say that spoofing the MAC on the WAN does it. Some buy a different modem or change its firmware. Most threads just end in no resolution though.

Is pfsense just not meant for residential use?

DaddyGo

Every system is different...but you have looked at some good topics in the forum so far (MAC spoofing, compatibility issue with my cable, etc.)
@badfrogg Is pfsense just not meant for residential use?

not pfSense is much more serious than that!

at what speed do you connect to your modem?
(if you find out, turn off auto - negotional)

badfrogg

Thanks. I haven't seen that recommended before. Will give it a try.

So, what I was asking about pfsense is more along the lines of, is it not meant to be compatible with a residential ISP modems and an ISP with DHCP?

DaddyGo

It's not that simple.
PfSense uses generally accepted tested packages for DHCP, but this does not mean that there should be no problems.

for example:

This is usually not a fault of pfSense
rather, ethernet controller to ethernet controller issue (modem eth. port to pfSense WAN interface eth, port

edit: many cable ISPs use a MAC ACL
plus MAC usability rules can be set up by the ISP (tied to time, frequency, etc.)

for you, since this is an intermittent error, ethernet controller compatibility is the possible error

badfrogg

I wish I understood. Regardless, thanks for taking the time to respond. I thought it would be good to play around and DIY a router but it is quite a bit more over my head then I realized.

badfrogg

Can I take away from this that it is likely a software issue and that buying a branded Netgate box would likely not fix this problem?

DaddyGo

check this, pls:

and try to preserve the speed negotiation
by not allowing auto-negotiation

Netgate dedicated hardware is a good choice, but it may not solve your problem.
The cause must be investigated first...

DaddyGo

and try not to use the Realtek or noname ethernet controller on pfSense interfaces ...
use these:

Intel I340 / I350 / i210-At / i211

edit: unfortunately, you cannot select the ethernet controller in the ISP CPE (this is given already by ISP)

badfrogg

![alt text](image url)

Got it. Will disable auto.

I am using an intel pro/1000 dual card now. But the problem is identical to the old box that ha the Realtek NIC.

Should I disable IPv6?

DaddyGo

@badfrogg said in A little support for a home user.:

Can I take away from this that it is likely a software issue and that buying a branded Netgate box would likely not fix this problem?

Definitely NOT a software bug

DaddyGo

I don't use IPv6 on my home network, it's unnecessary yet, but my service provides it ensure anyway

BTW, I use it in my work as it is needed in those systems...

if you don't need it much IPv6 for something (lot of IoT, etc.), turn it off

behemyth

That is an ARP issue - thats what arpresolve is doing i assume. ARP is Layer 2. What interface is EM0? Is that your WAN interface? You can go under interfaces to see what interface that is tied to. I dont know why you would be having an ARP issue between your cable modem and the WAN port, that is really odd.

If you google that error, they talk about that generally means the device cant find its gateway. That is why I'm asking what interface EM0 is. Your using a non-netgate box, so that interface might not be your WAN.

If this interface is not your WAN, then you have the wrong network (IP Space) assigned to that interface. If you have 1.1.1.0/24 assigned to an interface and the gateway is on 1.1.2.0/24, your going to have that exact issue.

badfrogg

EM0 is connected to my Cable Modem. EM1 is connected to my home switch.

What do you mean by VM? I have pfsence booting directly from an SSD. It was the serial img.

behemyth

Yah I updated my comment. Is your WAN interface using DHCP, or are you assigning a static IP?

badfrogg

I have Spectrum Cable Internet. It is DHCP. 400 downand 50 up.

behemyth

OK, I use Comcast - the only thing you should have set on your WAN is DHCP for IPv4, and then DHCP for v6 if spectrum supports it - and you should be good. You dont need any other settings configured for the WAN interface other than the default two block statements at the bottom that are checked by default.

What Cable modem are you using by chance? Is it the Arris Surfboard 8200 I think it is? The little white box?

badfrogg

It is an Arris TG1682G