PfSense install blocks Internet, but computer into modem has Internet?
-
There should be absolutely no reason that ping wouldn't work. It should work will all the settings at their install defaults (including 'block private networks').
So why is the ping not working. Some possibilities:
The pfSense box is sending the ping request out the wrong interface. That should never happen, particularly if you're pinging via the Diagnostic in the webgui where you have to specify which interface to use. I assume you're specifying the correct interface. ;)
The cables are run incorrectly (NICs connected wrongly). That situation is normally pretty obvious because nothing works, however if you have disabled the firewall or have sufficiently open rules you might get some traffic.
The modem is not receiving the ping requests. Hard to see how that might happen.
The modem is not replying. That's distinct possiblity but why is it not replying? Perhaps it only replies to devices in it's DHCP table, have you tried DHCP on the pfSense WAN?The best way to get to the bottom of this is to run a packet capture on the WAN while you try to ping the modem. Then you can see if the packets are leaving and replys coming back.
Steve
-
Ok, so ISP cable person provided a cable modem which has bridge mode.
I changed pfSense from static WAN IP to DHCP.
Connected new modem (in bridge mode) into pfSense and no Internet?I connect bridged modem or non-bridged modem into computer and Internet.
I'm researching now if I'm missing a pfSense setting, as pfSense is a fresh factory reset with default settings for now.
-
Tested pfSense > Diagnostics > Packet Capture > 8.8.8.8 > Start > Stop > no results.
pfSense > WAN > DHCP > green arrow up > IP 0.0.0.0.Rebooted modem several times.
Rebooted pfSense several times.Shouldn't pfSense be receiving an IP from the modem in bridge mode (like the public IP the modem passes through)?
Could there be a MAC address block or something from the ISP. I don't understand the MAC address allocation of IPs yet, so perhaps someone could help me with that angle of troubleshooting? -
Doing a packet capture is meaningless if there isn't any traffic going to that ip at that moment.
As you don't even get an IP on the DHCP set WAN interface I'd check the cable modem/pfS connection/cabling. -
Indeed if you do a packet capture you want to capture everything, don't filter just traffic to/from 8.8.8.8.
At the very least you should see the DHCP requests, and seemingly no replies.
Yes the pfSense box should be getting an IP from the modem. Using modem only device and receiving a public IP is the situation where the modem may only talk to one MAC address though. If you plugged in your client directly you may need to power cycle the modem to get it to talk to the pfSense box.I think we have to get basic here! ;)
Since you have the green up arrow the NIC is clearly seeing the connection, the cable can't be completely broken.
Speculation: the cable has a broken conductor such that not all pairs are working and it's trying to talk at 1Gbps and can't. What does Status: Interfaces: show for the WAN connection? Errors?
What NICs are these? Are they both the same? Is it obvious which one is WAN? We have seen people struggle for a long time with NIC connected incorrectly.Steve
-
First, let me sign in so I can give stephenw10 applause.
This is the reality of troubleshooting…patience, persistence and politeness.So, I should mention I have also tried:
pfSense > Interfaces > WAN > MAC address > WAN NIC MAC address > Save > Apply.
pfSense > Interfaces > WAN > MAC address > LAN NIC MAC address > Save > Apply.
pfSense > Interfaces > WAN > MAC address > Modem Device MAC address > Save > Apply.
pfSense > Status > Dashboard > WAN > IP 0.0.0.0.Cable should be ok, as the modem direct to computer works fine with Internet.
I might trying swapping the cable tomorrow if pfSense still won't allow Internet.What NICs are these? Not sure if you mean the brand? The NICs are 1000baseT full-duplex.
Are they both the same? Same brand?
Is it obvious which one is WAN. Yes, I am clear on the WAN and LAN (yes, it is often confused). This is confirmed by connecting the modem directly to the computer. Computers can still connect to pfSense via the LAN port 192.168.1.155. -
You mean you have tried spoofing the WAN NIC MAC address to those things? You shouldn't have to spoof the MAC. Also I seem to recall that some NICs don't respect the commands behind that tool. Check it with ifconfig.
I meant that if your NICs are, for example, both Intel then they will appear as em0 and em1. If they are both cards then there is no easy way to know which is em0 and which is em1. One good test is to unplug the cable from the WAN NIC and check that the green arrow changes to red or look at the media status in ifconfig.
The only reason I suggested it really is that initially your WAN subnet mask included the LAN such that a machine connecting to the WAN NIC with a LAN address might still be able to access the webgui.Do you know if the modem is gigabit?
Something I've seen before a few times is that a cable with one bad wire can support a 100Mbps no problems but won't run at 1Gbps. Worse though a gigabit connection only uses 2 pairs to negotiate the speed but requires all 4 to actually send traffic so you end up with nothing at all. Hence a machine with a 10/100 card work perfectly and a gigabit card doesn't work at all. I agree it doesn't look like this is your problem but it's an easy test to just swap out the cable.What NICs are they? Did I already ask that? Too many threads! ::)
Steve
-
Ok, so I removed the pfSense > Interfaces > WAN > MAC address, from the WAN NIC.
WAN NIC is clear which it is, yes, due to pulling out and seeing WAN down and red, rather than up and green when I connect the modem back into the pfSense WAN port.
I didn't have an em0 and em1 on pfSense factory reset.
I had re0 and re1.The WAN NIC is a MOBO NIC (motherboard Network Interface Card). Motherboard MSi Z87-G43.
The LAN NIC is a TP-LINK TG-3269 10/100/1000Mbps PCI Adapter.I tried another Ethernet cable and same issue.
I can't really change the WAN NIC without changing the MOBO. I thought this was a good MOBO so I am inclined not to focus on the MOBO.
Perhaps I need to buy an ALIX or something?
Is there a recommended pfSense hardware that uses little power? -
You haven't accidentally set the MAC addresses on WAN or LAN to addresses, that the modem or Clients use in any case? As Steve already mentioned you shouldn't have to override the MAC address on your NICs. Only case I had to do that was when a cable company insisted on binding your static public IPv4 address to a MAC address and we switched the box pfSense was running at. So I had to override the original MAC with the old one so we get our static IP back. But otherwise you shouldn't have to set a value there.
For devices with little power: that depends on the bandwith, packages you wanna run on it and states it needs to handle. For small environments, an ALIX or the bigger APU should be a good match. I also have a few Soekris devices running smoothly or some bigger devices from Lanner Inc (Atom D510 based boxed with 4-6 NICs).
Greets
-
Ok, so you have Realtek NICs, re0 and re1.
Sometimes, with usually no explanation, a particular piece of hardware just won't work with some other piece of hardware. I have run into this only a few times, most recently a Realtek NIC that couldn't talk to my SMC switch no matter what OS/driver I used. Since you're seeing a link negotiated it's probably not that but even so.
Try swapping the NIC assignments such that WAN is using the TP-Link NIC (which is known to be good).I have to say that establishing a link correctly and seeing that correctly in software but not actually being to send any traffic down it is an odd one. :-\
If you run a packet capture on WAN without any filtering, you don't see any traffic at all?
Steve
-
Thanks for the suggestion. I swapped the NIC assignments.
pfSense > Interfaces > (assign) > WAN: re0 to re1.
pfSense > Interfaces > (assign) > WAN: re1 to re0.
Connected modem to pfSense WAN TP-LINK NIC.
Connected router to pfSense LAN MOBO NIC.No Internet.
Unable to ping pfSense LAN 192.168.1.155.
Can't access pfSense any longer on computer to change NIC assignment back.
I guess I'll need to stick a keyboard and monitor into pfSense and hopefully be able to fix swap the NICs back.This seems to indicate the MOBO NIC is faulty. The NIC had one green LED and one orange LED.
The TP-LINK NIC (the usual pfSense LAN) always has 2 green LEDs.Seems I might need a new NIC so I bought:
http://www.mini-box.com/APU-1C-AMD-G-Series-T40E-APU?sc=8&category=1361
http://www.mini-box.com/Enclosure-1d2-Alix-2-redI couldn't find anything with wireless, because at the moment I have an 8 port Switch connected to a 4 port Wi-Fi router connecting to the pfSense LAN.
Perhaps an ALIX with Wi-Fi might be better? -
If it is just a bad NIC then you can always add a second network card. Plenty of spare slots on that mobo.
If you can you should hook up a console and check that the pfSense box is working correctly via the TP-Link NIC.You already bought that APU board?
You can add wifi to the APU board, it has miniPCIe slots and the cases usually have antenna cut-outs. I'm not familiar with the minibox case though if it's different to others.Steve
-
Okay,
so my new ALIX board arrived.
http://www.mini-box.com/APU-1C-AMD-G-Series-T40E-APU?sc=8&category=1361
http://www.mini-box.com/Enclosure-1d2-Alix-2-redI think I need a power supply and SD card or mini SD card? What size SD or mini SD to fit pfSense with the Snort package?
How do I do the Wi-Fi thing stephenw10 mentioned below? This would mean I can remove my old Wi-Fi router currently providing Wi-Fi.
This would remove the 4 ports aswell that I use.Is there a good switch with 12 - 20 ports that anyone recommends with the ALIX board?
This is my first time to install pfSense on the ALIX board. Do I connect a mini SD or SD in, connect an Ethernet to the ALIX, then SSH in to install somehow?
-
@eiger: I'd recommend open another thread as your last post has nothing to do with blocked internet anymore, does it?
As the installation of an APU is a whole different can of worms, I'd say to open a new thread to not confuse people away from helping you with that. BTW: You don't own an ALIX Board. You bought an APU. This is NOT the same board at all. Don't mix and match them, as that will confuse the heck out of people ;) The APU is an amd dualcore chip as the ALIX was a x86 compatible thingy with far less cpu power and RAM. So even if PCengines used the Alix casing (as the boards are the same size and similar layout), you don't have an ALIX :)
I'd recommend trying it with a USB stick and then either buying an SD card with 4GB or 8GB or going with the mSATA module and install it there if you plan to use a few packages.
Greets
-
Thank you for the info.
Yes, I have made a new topic https://forum.pfsense.org/index.php?topic=76541.0
