SG-2220, GUI, but no internet



  • I have an SG-2220 which lets me access the GUI, but not the internet. I have tried a bunch of different things to fix this, including everything from rebooting and reseting everything in the chain (which is just my computer>SG>modem), shutting down my firewall, ensuring the cables are going in the correct ports, spoofing my old router's MAC, changing my computer's IP then configuring the SG while not connected to the modem, but still no luck.

    I called my ISP to confirm DHCP was the right setting (it is), that they don't need a DHCP Hostname entry, and asking if there's anything else they recommend or any special requirements for setting up routers (there are none).

    I'm really at a loss here after 4 days of wrestling with this. I have even contacted pfsense technical support but am having no luck (so far). It seems like it ought to be something simple that I'll kick myself for later, but I have no idea what it could be (but I'm also a noob to networking. If you have any suggestions at, I would be very happy to hear them.



  • Run Wireshark to get a better idea of what is happening?



  • @Nullity:

    Run Wireshark to get a better idea of what is happening?

    Is that wise given that I already can't handle setting up the SG-2220? :)



  • @pfsensed:

    @Nullity:

    Run Wireshark to get a better idea of what is happening?

    Is that wise given that I already can't handle setting up the SG-2220? :)

    That is precisely why I chose to mention Wireshark rather than tcpdump. :)
    You can't cause many problems by simply monitoring the traffic.

    Anyway, I am a Wireshark noob myself, but the GUI literally displays erroneous packets in red or black. If there is an obvious problem, it should be … well, obvious. Look for things like duplicates, errors, strange IPs. The GUI is reasonably intuitive to newbies.

    Just download it, open it, select your NIC and go.

    Edit: I mean run Wireshark on your PC, not pfSense.



  • @Nullity:

    @pfsensed:

    @Nullity:

    Run Wireshark to get a better idea of what is happening?

    Is that wise given that I already can't handle setting up the SG-2220? :)

    That is precisely why I chose to mention Wireshark rather than tcpdump. :)
    You can't cause many problems by simply monitoring the traffic.

    Anyway, I am a Wireshark noob myself, but the GUI literally displays erroneous packets in red or black. If there is an obvious problem, it should be … well, obvious. Look for things like duplicates, errors, strange IPs. The GUI is reasonably intuitive to newbies.

    Just download it, open it, select your NIC and go.

    Edit: I mean run Wireshark on your PC, not pfSense.

    I solved the problem.

    I disabled several browser add-ons, reset the SG, power cycled my modem and SG, then went through the configuration again, and this time it worked. I believe the culprit was NoScript interfereing with the initial configuration, as some fields which were present before are totally gone now.

    Now I may go install Wireshark anyway :)



  • @pfsensed:

    @Nullity:

    @pfsensed:

    @Nullity:

    Run Wireshark to get a better idea of what is happening?

    Is that wise given that I already can't handle setting up the SG-2220? :)

    That is precisely why I chose to mention Wireshark rather than tcpdump. :)
    You can't cause many problems by simply monitoring the traffic.

    Anyway, I am a Wireshark noob myself, but the GUI literally displays erroneous packets in red or black. If there is an obvious problem, it should be … well, obvious. Look for things like duplicates, errors, strange IPs. The GUI is reasonably intuitive to newbies.

    Just download it, open it, select your NIC and go.

    Edit: I mean run Wireshark on your PC, not pfSense.

    I solved the problem.

    I disabled several browser add-ons, reset the SG, power cycled my modem and SG, then went through the configuration again, and this time it worked. I believe the culprit was NoScript interfereing with the initial configuration, as some fields which were present before are totally gone now.

    Now I may go install Wireshark anyway :)

    Congrats!

    I prefer the CLI of tcpdump myself. GUIs are infinitely confusing.

    Wireshark, or any packet sniffer, is great as a teaching aid to understand computer networking.


Log in to reply