Am I in over my head?
-
@johnpoz said in Am I in over my head?:
So your seeing wan connect on pfsense at gig? Your not seeing errors on the interface?
Not sure I understand but. I got 900 Mbps through the box on the bench with iperf. The dashboard interface status shows 0 errors and 0 collisions.
Does that answer? When the box is connected to my modem is when it goes bad.
Oh, and I just tried this. I put the pfsence box behind my old DD-WRT router and it works fine. (at the limit of that old router which is like 80 Mbps)
-
This should work out of the box.... If out of the box you see 900 mbps natting from wan to lan test with iperf... Why would you think it would be any different sending a few packets back and forth to your isp? That screams bad connection to whatever you wan is..
What connection speed is coming on the wan interface when you plug it into your isp? Your getting a public IP? Or do you have a overlap issue with wan and lan networks?
edit: works fine behind the other router would hint at you have an overlap on networks maybe... Like you first had when you tried to test where you thought you could use /16 and then put a /24 on your lan that is inside the /16 network.
Maybe your dd-wrt is using 192.168.2 vs 192.168.1 like your isp device... You can not have overlapping networks on your wan and lan and expect anything to actually work.
-
My ISP is Spectrum on a cable modem with routing turned off. I get a 72.185.x.x IP address. I can plug that modem into my computer directly and get 400+ Mbps (I have a 400 Mbps plan)
-
Well then look to the connection between being your problem.. If your saying it works fine behind your other router... Just use it as a switch then.. I am guessing the ports or 10/100 on your dd-wrt router, or are they gig?
Turn off dhcp on your dd-wrt and use it as just a dumb switch (just use lan ports).. Or use a different switch between your modem and pfsense.
isp device --- switch --- pfsense wan
Also pretty much any cable modem ever worked with requires a reboot when you change the mac of the device connected to it... I swap out different router, or go from router to pc or pc to router, etc.
-
I kinda understood the /16 being on the same sunbnet and overlap thing. That why I was quick to fix that on my own. But I dont see that scenario happening now. everything is DHCP and the addresses are definitely WAN and LAN.
-
if your public on wan, and 192.168.x on your lan your fine... But maybe there is a connection issue between the devices ports.
If your saying works fine with your other router pfsense behind - then just use its lan ports as dumb switch to connect pfsense to your isp modem. Your just goign to want to turn off dhcp server on it so pfsense doesn't get its address from dd-wrt dhcp.
-
The DD-WRT is 10/100, I rebooted the modem after each different try and even call the tech to have them rest my port.
-
Do you not have a gig switch you can use? If your saying there was no overlap in networks, and works fine behind your other router... Then points to connection issue between your modem and pfsense ports. So put a switch only between... Ie you can just use the lan ports of your dd-wrt router as dumb switch - if you get close to 100 that way... Then get switch... You can get a gig 5/8 port switch for like $20...
There are devices that just don't like talking to each other.. Its rare but have seen it over the years.
device A doesn't like talking to B..
So you put device C (switch) in between that A or B have no problem talking too.
-
I have a dumb 1g switch that I can put in between the modem and pfsence. I'll try that.
I do not want the DD-WRT router or switch in the equation. It is slow and old (10 years I think)
I did have two ISPs in the house up until yesterday. This problem persisted on both, two completely different modems. One was the Motorola ONT (FiOS) and the other is a ARRIS TG1682G (The ARRIS is my current one)
-
Even at 100Mbps it would prove the issue is at the link layer.
You could also try fetching a file from pfSense directly to check if it's WAN or LAN side:
[2.4.4-RELEASE][admin@5100.stevew.lan]/root: fetch -o /dev/null http://download.thinkbroadband.com/50MB.zip /dev/null 100% of 50 MB 4470 kBps 00m11sThough it looks like WAN side since it works behind a different router.
Steve
-
@badfrogg have you considered it might be an MTU issue ? have you tried lowering it?
-
I have achieved success. But... I don't know why.
I had an exact duplicate set of the hardware I was using so, I took that hardware and repeated the same process from scratch. I made a fresh USB stick and installed it to the other board.
The same exact version of pfsence, same exact hardware with the same exact processor and bios.Just as before, I installed it with a serial console (the only things I did in console was say no to VLAN and set re0 to WAN and re1 to LAN)
Then in the browser configuration all I did was set the time zone and password.... And it worked! Everything is routing just fine. I get my full service speed with a ping below 10.
I promise that I did these exact steps on the other setup several times.
-
Well maybe something odd with that other hardware nic... I had a nic one time just start spewing out garbage.. A sniff on the wire could of help determine what was the issue - malformed packets maybe? Just a odd problem with that nic talking correctly to your modem, etc.
Glad you got it sorted.
Is it possible the nics on the different hardware are different firmware? You could try redoing the other hardware and see if that still sees the problem.
-
I would not even begin to know how to look at the firmware version let alone updated it on this board. The NIC is on the motherboard.
Yeah. It could be that the NIC chipset may have been zapped. or maybe my initial install from the USB was corrupted. The one thing that was different was that I flashed a new USB installer.
I might one day try the old board but I have spent like 20 hours and just happy to be done with it for now. I will put the "other router" i bought on the shelf and play with it later as well. As long as this box stays stable it will me my new router.
Thanks for everyone who spent their time with me. Sorry that the problem was a wild goose chase.
