No Internet With WAN connection

[Metu69salemi]

Sometimes you just have to reboot your modem to get it work, have you done that?

[IVIilkman]

Yeah Tried that a Few Times And no Luck.

If I bypass Pfsense and go right to the Hub All the Computers Can connect perfectly.

[wallabybob]

Your default route goes through your cable modem? (What is the output from the pfSense shell command # netstat -n -r ?)

[Metu69salemi]

Maybe it has something todo with wan-rule "Block private networks"
But smarter ones has to answer

[IVIilkman]

I'm very Stupid when it Come to this. I'm not even entirely sure the proper way execute the Shell command # netstat -n -r

[wallabybob]

@Metu69salemi:

Maybe it has something todo with wan-rule "Block private networks"

That's a good thought. The interface counters show no blacked packets and no pass packets so things haven't got far enough along for this particular wan rule to become an issue.

For clarity, in this configuration Block private networks should be DISABLED (not ticked) on all interfaces.

[wallabybob]

@IVIilkman:

I'm not even entirely sure the proper way execute the Shell command # netstat -n -r

Some options:

• On pfSense console menu select option 8 (Shell) and type netstat -n -r at the shell prompt (#)

• On another system ssh with login as admin to the pfSense LAN interface address, at the menu select option 8 (Shell) and type netstat -n -r at the shell prompt (#)

• From the pfSense web GUI select Diagnostics -> Command prompt and type netstat -n -r in the Command box and click the Execute button.

  With the last option it is pretty easy to copy and paste the command output into a reply to this thread.

[IVIilkman]

ok results of the netstat -n -r

The Top on is the one that Work. The lower Photo Does not Work.


[wallabybob]

Sorry I didn't spot this earlier. You have an invalid configuration: em1 and re0 belong to the same subnet. You should change em1 IP address to be (say) 192.168.99.1/24 to be distinct from em0 and re0.

If you have DHCP enabled on em1 you will also need to change the range of DHCP addresses.

If you have a fair bit of stuff configured around a LAN subnet of 192.168.0.0/24 then it may be easier to change the cable modem's configured DHCP subnet to (say) 192.168.99.0/24

[XIII]

Might have to clone the mac of the computer that can connect without issue.

[IVIilkman]

Thank you wallabybob Changed the Cable modems DHCP subnet and it all works like a Champ.

Thanks