Does pfSense support SNTP
-
Well if you want ipv6 and firmware that is not 5 years old.. You prob want to look for different model ;)
-
I'm not too worried about IPv6 vs IPv4 for SNTP. Even with pfSense, the NTP servers I use support IPv4 only. However, I bought it so that I would have a managed Gb switch and that's what it does. I have the same situation with my TP-Link access point. The management is IPv4 only, but it passes IPv6 as needed, other than the previously mentioned issue that prevents me from running a 2nd SSID.
-
@JKnott said in Does pfSense support SNTP:
he NTP servers I use support IPv4 only.
There are plenty of IPv6 ntp out there you could point too.. Shoot I have my pi stratum 1 ntp server in the pool via ipv6 and ipv4.. It sees plenty of ipv6 clients...
Your the whole IPv6 is the greatest thing since sliced bread guy around here - that you have hardware that doesn't support ipv6 pokes holes in your whole the ipv6 revolution is here, you ipv4 guys are behind the times... Must Use IPv6!!! ;)
-
@johnpoz said in Does pfSense support SNTP:
@JKnott said in Does pfSense support SNTP:
he NTP servers I use support IPv4 only.
There are plenty of IPv6 ntp out there you could point too.. Shoot I have my pi stratum 1 ntp server in the pool via ipv6 and ipv4.. It sees plenty of ipv6 clients...
No doubt there are IPv6 servers. However, I've been using the same ones since long before I started with IPv6.
Your the whole IPv6 is the greatest thing since sliced bread guy around here - that you have hardware that doesn't support ipv6 pokes holes in your whole the ipv6 revolution is here, you ipv4 guys are behind the times... Must Use IPv6!!! ;)
I think you'll find I'm opposed to those who think IPv4 is all that's necessary, even though it hasn't been adequate, due to limited address space, for many years. Even Vint Cerf has said he never intended for 32 bit addresses to be inflicted on the public. It was only to be a concept demo. I am fully in favour of IPv6, as it brings some other advantages, beyond just increased address space. If it had sufficient address space, IPv4 would have been OK. I also not the type to toss functioning equipment, just because something better came along, unless I would get benefit from doing so. Thus my change to a Gb switch, as my Internet connection bandwidth was approaching 100 Mb. My AP is 2.4 GHz 802.11n as going beyond that wouldn't bring me much advantage, since my notebook computer is only 2.4 GHz n. Also, you're talking to a guy that used to use SNA, along with NetBIOS and IP on the same computer. I was also working with networks before Ethernet and IP were available, so I'm not afraid of old stuff.
As for NTP etc., I recently got into a discussion with a co-worker on a project we were working on. This project involved 2 GPS NTP servers (they weren't part of our work), located a few miles apart. He couldn't understand that multiple NTP servers should be peered, rather than main & fallback. There were other servers and the plan was to have the master on our project sync, not peer, with those on another network where there were two more. With 4 GPS NTP servers, they should have all been peered.
-
I must admit that I don't like IPv6 because I don't really understand it and all of its ramifications, and I've been getting by with IPv4 for decades.
-
What's to understand? Fundamentally, it works the same way as IPv4. You have packets, routing works the same and more. The same traffic is supported and from a user perspective it makes no difference whether IPv4 or IPv6 is used. However, in addition to the immense address space, there are a lot of technical improvements that go to performance. For example ARP is gone and replaced with ICMP6 neighbour solicitation. There is also automatic address configuration, without needing DHCP, though it's also available. The fixed length headers improve router performance and more. The designers of IPv6 took the good points of IPv4 and discarded the bad. One example of the bad is broadcasts. They caused disturbance to devices on the network, whether they were interested in the traffic or not. That's been replaced with multicasts. With mulitcasts, the closest to broadcasts is all hosts multicast, which go to all devices. However that would only be done with things, such as router advertisements that must go to all devices. Otherwise targeted multicast groups, such as all routers, etc. would be used. A really big bad that's no longer needed is NAT. There are some things which did not appear in IPv4, such as using SLAAC to assign addresses to devices or DHCPv6-PD, which ISPs use to provide the network prefix to customers. So, do a bit of reading and you can learn about IPv6. One book I recommend is "IPv6 Essentials", from O'Reilly, which covers IPv6 very well, though it doesn't cover DHCPv6-PD.
-
@JKnott said in Does pfSense support SNTP:
JKnott: "What's to understand?"
Lists a dozen things I don't understand.
I get the very basic top-level stuff, but all of those features you mentioned were news to me. I had no idea that IPv6 doesn't use ARP, for example. Plus, I don't use it here at work and likely never will unless our ISP revoked all IPv4 support.
Thanks for the book tip. I'll definitely look into it. I know I need to up my IPv6 game but didn't even know where to start. In past years I had tried reading up on it but I could never find a good resource. IPv6 and VLANs kind of passed me by.
-
I find the best way to learn is to do. I've been using IPv6 for 9 years and knew little about it when I started. Now, I know more about it than the tier two support and senior techs at my ISP (I had to teach them, when I had a problem recently.). One thing that really goes a long way in learning about networks is Wireshark. With it, you can look at the packets to see what's in them. By using Wireshark, I was able to identify the failing system, by name, at my ISP, weeks before they finally figured it out.
VLANs are just logically separate networks that appear as though they're physically different. That's done with a VLAN tag, that contains the VLAN number. Again, reading and Wireshark can help you learn. A good reference is "Ethernet", again from O'Reilly (I have a lot of O'Reilly books
). It covers VLANs and a lot of other things. -
I understand the basic concept of VLANs, just not the specifics and gotchas. Anyway, I didn't mean to hijack this thread into a personal tutorial for me. Thanks for your suggestions.
-
@KOM
Well, it's my thread and I don't mind. Forums like this are a great way to learn, even if things drift off topic. -
@Gertjan said in Does pfSense support SNTP:
@JKnott said in Does pfSense support SNTP:
Wow, I can use XMODEM to upload a file!!! .... TFTP .....
Nice ! You just made me think about a period, some 3 decades ago.
Back then, a Wellar solding station was as important as a keyboard.You still have to XMODEM IOS to a Cisco switch if there's no IOS in flash :)
-
@NogBadTheBad said in Does pfSense support SNTP:
You still have to XMODEM IOS to a Cisco switch if there's no IOS in flash :)
I think I saw that mentioned in my search for firmware updates. However, that would be a bit difficult to do without a serial port on that box. However, what is does to is create a web server, if the firmware can't be found. That web server can then be used to upload the firmware. I wonder if that gets turned on, when http upload is selected. I was using tftp, where I had to specify the IP address and file, but the missing firmware web server was 192.168.1.254, IIRC. I'll have to look into that.
