New SG-1100 no Internet

larryjb

I'm quite new at this, and I may have posted this in the wrong section, so forgive me if this is in the wrong place.

I just received my new SG-1100. I successfully logged into the firewall and ran the wizard. However, once I completed the process, I still did not have access to the Internet.

I attached the WAN cable to the WAN port.
I connected the computer directly to the LAN port.

I ran the wizard using the recommended settings from the manual:
I left DNS Servers blank as I'm using the supplied DNS servers.
Using DHCP for WAN type

I am coming from a Netgear router/firewall and am able to connect to the Internet from there. The IP and DNS servers are all obtained from the ISP.

I'm sure I must have done something wrong in the configuration, but the initial configuration looks so simple that I cannot figure out what I may have done wrong.

SteveITS

Does the dashboard show a WAN IP address?

You could try powering off your ISP router/modem. Sometimes that is necessary.

larryjb

@teamits

Thanks, I've tried power cycling the modem, firewall, and computer. That made no difference.

Last time I went back to the Netgear, it took quite a long time for it to get the Internet though.

I recall seeing something earlier but I didn't record it at the time. I'll look for and record the WAN IP address.

larryjb

The WAN IP address shows up as 0.0.0.0

DNS servers: 127.0.0.1
208.67.222.222
208.67.220.220

The current date and time seem off. Perhaps that might be the problem, that the date and time don't match the DNS server? It's Jan 29, but the current date in the dashboard is showing up as Sept 16.

larryjb

I got it. I'm not sure exactly what I did, but I think my modem was on the same ip as the firewall. I had wondered, but didn't know how to check it, but I tried changing the ip to 192.168.2.1 and it's working.

The final clue I got was I finally saw on the dashboard the ip of the gateway went from 0.0.0.0 to 192.168.1.1. Then I knew I had to change it.

larryjb

All is working well now.

However, a curious thing happened to me earlier today. I had set my Netgate to 192.168.1.2 to avoid conflict with the gateway which was at 192.168.1.1. (I had tried setting the Netgate to 192.168.2.1, but then I couldn't access anything else on the network, so I switched it to the 192.168.1.1.) All was working well and I started setting static DHCP leases. Once I tried logging into the Netgate IP (192.168.1.2), my Epson printer came up! I didn't think this could happen because the Netgate was already set at 192.168.1.2. I had to turn off my printer then reenter the Netgate IP before I could gain access to it again. I'm curious why this could happen.

chpalmer

@larryjb sounds like a you have the same subnet on WAN and LAN. That won't work.

larryjb

@chpalmer Pardon my ignorance, I'm used to essentially plug and play wireless routers. When you say the same subnet for WAN and LAN, do you mean that the Gateway should NOT be configured for any 192.168.1.x? That is should be a 192.168.0.x? On all my previous routers, I assume there was never any conflict with the gateway and router

Now that it is connected and running, I get the providers IP for the ISP of my DNS server.

SteveITS

Which gateway are you talking about? The gateway on the WAN is assigned by your ISP, since you said WAN was using DHCP.

The subnet of the WAN needs to be different than the subnet for the LAN or else the router won't know where to send traffic.

re: the Epson, it sounds like that already had an IP address...some devices won't get a new address until the address lease time expires. It's safer to at least ping an IP before to manually assign it to something.

larryjb

@teamits

Okay, I'm must be mixing up and confusing terms. By the gateway, I was trying to refer to the modem. I thought some referred to the modem as the gateway, like some refer to the router as the firewall. It doesn't help that these terms seem to be poorly defined elsewhere on the Internet.

SteveITS

Different people do use the term differently. For any network, the "gateway" is where a device sends packets that are for another network. To your PC your pfSense is its gateway. To pfSense, the ISP modem/router is its gateway, and so on.

As long as all networks have their own subnet, and all devices have a unique IP address, things are fine. :)

larryjb

Just today the printer dropped out again, but I cannot find a reason for it.

I assigned the printer to 192.168.1.120 in pfsense. When I type the ip address I get a printer settings page in the browser so I know I am communicating with the printer. However, when I try to print I get a network error in the print queue.

I'm still using the Netgear R6700v3, but as a wireless access point only. I'll try turning it off and using only the Unifi Lite AP instead.

EDIT:
I since pulled my R6700v3 even as an access point, connected the printer to the Unifi Lite, then removed and reinstalled the printer drivers. Printing is back. I'm pretty sure all my printer issues originated from the R6700v3.