08-12-2016, 05:23 PM
(This post was last modified: 08-12-2016, 05:24 PM by MarkHaysHarris777.)
hi Tom,
This is kinda typical for Comcast; they often use the 10.0.0.1 address for the gateway address; however, I thought that the 10.0.0.1 was a class A network , so would need a netmask of 255.0.0.0 (yours shows the netmask set to 255.255.255.0 which is a class C netmask.
So, things may not be working because of the netmask being incorrect ; possibly, please don't hold my feet to the fire. Comcast is a strange animal.
(anyone else is free to chime in here too)
You might want to take a look at other machines on your network, and compare their gateway addresses, netmask, and nameserver information. How do they compare?
This is kinda typical for Comcast; they often use the 10.0.0.1 address for the gateway address; however, I thought that the 10.0.0.1 was a class A network , so would need a netmask of 255.0.0.0 (yours shows the netmask set to 255.255.255.0 which is a class C netmask.
So, things may not be working because of the netmask being incorrect ; possibly, please don't hold my feet to the fire. Comcast is a strange animal.
(anyone else is free to chime in here too)
You might want to take a look at other machines on your network, and compare their gateway addresses, netmask, and nameserver information. How do they compare?
marcushh777 
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )