New comcast gateway wired connection not working

[walterbyrd]

Comcast "upgraded" me to new XB10 gateway. Wireless works just fine. Wired connections not so much.
I can ping internet IP addresses. But I cannot go to a named website, like "google.com"
Comcast will not support FreeBSD.
I cannot login to the gateway. I have to do everything with their xfinity app.
I tried setting my name servers to 1.1.1.1 and 8.8.8.8 in rc.conf, but I got the message that those servers could not be found. I think the nameservers are set in the gateway, and I am not sure if I can change them.
I have my freebsd configured as a webserver, I can reach my local website.
I cannot bring up websites that are not local. For example, I can ping 96.47.72.84 but if I enter that address in my browser, the connection times out.
I have my freebsd configured to use static IP address: 10.0.0.9.
My local Jellyfin server also works.

 

[Espionage724]

I cannot login to the gateway. I have to do everything with their xfinity app.

Are you sure you can't access an administration page? Iirc Xfinity stuff had something odd like 10.10.10.1

I don't think it'd fix connectivity (missed where wifi works; looks like just FreeBSD-side conf needed), but putting it in bridge mode and having another device handle router stuff might be an option too (if a FreeBSD PC's the only device hard-wired to the modem, I'd have FreeBSD DHCP IPv4 + IPv6 SLAAC, bridge the modem, then try accessing the modem admin page and/or seeing if WAN works); this post says XB10 can do bridge mode

 

[walterbyrd]

When I try to go to 10.0.0.1 I just get a message that my network are to managed with xfinity app. I they give me a link to xfinity.com.

I edited my original post to include this:
I have my freebsd configured as a webserver, I can reach my local website.
I cannot bring up websites that are not local. For example, I can ping 96.47.72.84 but if I enter that address in my browser, the connection times out.
I have my freebsd configured to use static IP address: 10.0.0.9.
My local Jellyfin server also works.

 

[SirDice]

Comcast will not support FreeBSD.

Irrelevant, it's TCP/IP.

I tried setting my name servers to 1.1.1.1 and 8.8.8.8 in rc.conf

Wrong place. Nameservers go in /etc/resolv.conf.

I think the nameservers are set in the gateway

You typically get an IP address, subnet mask, default gateway and one or more DNS servers with DHCP.

I have my freebsd configured to use static IP address: 10.0.0.9.

It's probably not the correct subnet. Just set the host to DHCP and let it automatically figure it out.

 

[walterbyrd]

Sorry for being away from this thread for so long. I have had a lot going on.

I started a chat with Comcast, it went on for hours. They keep insisting I do tests to see if the gateway connects to the internet. I have no way to tell them that is not the problem.

I did not tell the person I chatted with that I was using freebsd. If I had told them that, it would have been the end of the chat right away. I have a Mac that can use wifi or wired. I tried setting the Mac to a static address and connecting that by wire, but had the same issues.

I am not sure if I told him that I had a static address. I want to use a static address for a few reasons. I think it make Jellyfin easier. But, I suppose I could have using DHCP and then found out what the masking was and so on.

The Comcast guy told me to hook up the old gateway, and he would send me a new gateway. But I never got the new gateway. I may just stick with the old gateway. At least the old gateway works. I did not notice any dramatic increase in speed with the new gateway.

Thanks for telling me that /etc/rc.conf is not the place for nameservers. I should have known that.

This is my /etc/resolv.conf file. I am not sure where it got those nameservers. I don't think I put them there.

# Generated by resolvconf
nameserver 2001:558:feed::1
nameserver 2001:558:feed::2