Complete noob here sorry if this is an easy question.
-
-
@steveits @JKnott @Gertjan @Tzvia
As I did before I will atempt to answer all the questions here:
Did I change anything like Static IP or mask or anything?
Not that I can think of other than the IP address to 192.168.1.101 to try to get it to match ( I'm sure this is a rookie mistake).192.168.1.1/24?
No I'm seeing 192.168.1.101/24When I typed in Whoami on CMD:
Server: pfSense.home.arpa
Address: 192.168.1.101DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to pfSense.home.arpa timed-outWhen I typed in
IPconfig /allEthernet adapter Ethernet:
Connection-specific DNS Suffix . : home.arpa
Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection
Physical Address. . . . . . . . . : 70-85-C2-5B-0F-B4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::252b:f3ad:6b0d:e587%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.109(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, April 27, 2021 7:16:58 PM
Lease Expires . . . . . . . . . . : Tuesday, April 27, 2021 9:16:57 PM
Default Gateway . . . . . . . . . : fe80::21b:21ff:fecf:c8f1%14
192.168.1.101
DHCP Server . . . . . . . . . . . : 192.168.1.101
DHCPv6 IAID . . . . . . . . . . . : 342918594
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-50-3E-0F-70-85-C2-5B-0F-B4
DNS Servers . . . . . . . . . . . : 192.168.1.101
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
home.arpaThank you!
-
I keep re-reading your first post, wife gets internet. It states you get IP, you can (sometimes) get into PFSense GUI. So not a speed/duplex. Thought wife's pc was DHCP, yours static, wrong DNS maybe? Wrong gateway? No, you reset your network settings (DHCP). Wife's PC works- maybe set manually with internet DNS so it works, but PFSense not set correctly for DNS or DNS/UNBOUND not working? Goes to neighbor's house, doesn't work (neighbor DHCP, DNS pointing to PFSense and DNS on it still not working?) Would be interesting to see how the wife's computer is set; (static or dhcp with manually set internet DNS servers...?).
Then this thought dawns on me. You are using a four port Intel nic. one is WAN, one is LAN, and the others would be OTHER NETWORKS if configured as such OR more likely non functional (not configured). Four ports does not a switch make. You need to use the same port that worked with your wife's computer; the other ports would only be functional if configured and would be different networks with their own DHCP.
How is the wife's computer configured... -
@tzvia
I will get your her config later.I am using the same port that my wife's computer was plugged into, at this moment I only have one port for wan and one port for lan ( igb0 is wan and igb1 is lan) all others are not setup
-
It appears you're in need of a cheap switch.
-
-
The only reason I suggested a switch was so you could have both computers connected at the same time.
-
@gtimmis07 this probs could be anything,
For your pc, login as admin and try this:
Open command cmd.exe run as admin and type:
ipconfig /release
ipconfig /flushdns
ipconfig /renewnetsh winsock reset
netsh interface ipv4 reset
netsh interface ipv6 reset
netsh interface ip delete destinationcache
netsh winsock reset catalogFor your pfsense, please take your time to watch this video guide fromYoutuber Knowledge Power:
https://www.youtube.com/watch?v=wv1qTYR3faQ -
I did all the cmd commands and restarted my computer. Still no internet on it though. 3 1/2 video is a but much for me right now but I will sit down and watch it later.
-
@gtimmis07 if your pfsense device has more nic and you have only 2 pc, then I suggest don't buy any switcher. But instead use those nic as interfaces Wan, Lan, Opt1, Opt2.
About pfsense video guide, that video has helped more that 8000 pfsense users. Also when you watch that 3.5 hours pfsense guide video, please take a note of timestamp. For example Disabling IPv6 on 41:21 timestamp.
Why you must disable IPv6: https://www.youtube.com/watch?v=Vt4Jl4t43ug
-
@akegec said in Complete noob here sorry if this is an easy question.:
Why you must disable IPv6: https://www.youtube.com/watch?v=Vt4Jl4t43ug
Must ?
What about : make IPv6 work, and most probably better as any available local ISP can offer you : Configuring IPv6 Through A Tunnel Broker Service It's a close to set it and forget it operation."Why to make IPv6 work" isn't really a question. Will it be this year that there will be more IPv6 traffic as IPv4 ? On LAN's, most devices prefer IPv6 over IPv4 (even if the main gateway DNS doesn't support it.
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@akegec said in Complete noob here sorry if this is an easy question.:
Why you must disable IPv6
Nonsense. That is head in the sand stupidity. The world is moving to IPv6. My ISP has provided it for over 5 years and I was running it for 6 more via a tunnel. IPv4 hasn't been adequate since the day it became necessary to use NAT to get around the address shortage. Also, because of that shortage there are many people stuck behind carrier grade NAT, which means they can't access their own networks from elsewhere.
-
@gertjan, @JKnott, the problems with IPv6 , it's not completely implemented while it's been almost 30 years later since the birth of IPv6, but there is no or little improvement. Why? M.A.G.A. don't want to invest in it, just recently they have changed of heart. So you wonder when I will use IPv6 for my clients? When all internet connections use IPv6 only network. By then new technology are equip with IPv6 security futures.
Does anyone know what M.A.G.A. stand for? Microsoft, Amazon, Google and Apple or Make America Great Again?
-
@akegec said in Complete noob here sorry if this is an easy question.:
Why you must disable IPv6: https://www.youtube.com/watch?v=Vt4Jl4t43ug
I just watched the first segment of that video. What a load of nonsense.
PfSense running on Qotom mini PC
i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
UniFi AC-Lite access pointI haven't lost my mind. It's around here...somewhere...
-
I first read about IPv6 in the April 1995 issue of Byte magazine. I have been using it at home for 11 years, next month. These days, many ISPs provide both IPv4 and IPv6, as mine does, though some (including my cell phone company) use 464XLAT to provide IPv4. Sadly, some ISPs are still stuck in the dark ages and provide only IPv4.
As for "MAGA", we'll have to see what happens now that there's a competent president in office.
-
There is really only 1 reason to disable IPv6 - and that is your not up to implementing it. There is a learning curve for sure. There is also some really crappy implementations out there from some ISPs. These can many times be overcome with say a tunnel as mentioned.
As of yet I have not seen any public resource that would require a user to have IPv6.. So unless there is something the user needs that requires it. Love to hear what that is ;) Then sure there is nothing say they have to use it. And it can make their network simpler and easier to manage by just not enabling it.
Saying you "must" disable it is pure and utter BS.. It for sure is the future, but as of yet - unless your on a mobile device.. Many of them use IPv6 only, with gateway on the provider to allow talking to IPv4 addresses.. T-Mobile here in the US is that way, at least in my part of the country. Cell phones going to IPv6 has for sure reduced the strain on the IPv4 space that is for sure.
Or your in part of the world where ISP will not give you an IPv4, or they only give you cgnat IPv4 and if you want to allow for unsolicited inbound traffic and you can do that via IPv6.
But I would say - if the user is having issues with it, and they do not have the desire or skill or time to fix whatever the issue is. Then sure a simple solution is to just not use it at this time. Also if you feel that IPv6 might be part of a problem your trying to troubleshoot - there is nothing wrong with turning it off to test/troubleshoot to validate that yes indeed something is not right with the IPv6 connection, or the configuration or the client use of it, etc. etc.
IPv6 is a bit more than just a longer IP address - there are some fundamental differences for sure. And if the user is not up to speed on understanding these, then turning it off is valid advice.
Users smart enough to disable it, and doing so sure and the hell is not going to slow down the global migration to it ;)
-
@akegec said in Complete noob here sorry if this is an easy question.:
So you wonder when I will use IPv6 for my clients?
Several years ago, your clients would likely be running IPX, yet I bet they've probably moved to IP by now.
-
IPX was not something that could have ever scaled to what is now the internet ;)
So yeah if you wanted to be on the "internet" you had to use tcp/ip.. While not an overall bad example of transition to a new protocol for communication.
It fails in that to use xyz you needed to use IP. With ipv4 vs ipv6 - I can still use xyz, without having to use ipv6.. When I can not get to xyz without ipv6 is when you will see the migration accelerate.
-
At the time, IPX was used in businesses and connected offices within an organization. However, there was initially no concept of an "Internet". Also, when Vint Cerf came up with IPv4, his intent that it was only an experiment to demonstrate the concept and the final version would have a larger address space. Unfortunately, IPv4 "escaped". There were other routeable protocols, such as DECNet, SNA and Appletalk, too.
BTW, the idea of connected networks goes back long before IP. Many years ago, I used to work on a network in the Air Canada reservation system. This network was created by (Rockwell) Collins, for use with their computers. Instead of packets, it used time slots (TDM). The idea was several of these networks could be interconnected, in the way IP did later. I first worked on the network in 1978, but it had been around for a few years before that.
-
