[mdlug] Static IP behind NAT with Xfinity

Tue Aug 4 22:39:06 EDT 2020

Okay, there are two (rather) easy ways to take care of this.

One is set the router to use 192.168.1.0/24 instead of
10.0.0.0/23.  This has the advantage of not needing to
do anything to any devices on your network.

The other is to give the server an address in the 10.0.0.0
subnet.  This can be done by enabling DHCP on the
server and jotting down the IP address, network mask,
gateway and nameservers.  You could either keep that
address or select a specific one and hard code it.  The
main advantage here is that if/when the router needs
to be replaced you won't have to make any changes.

Are your MythTV clients all getting IPs from the router?
If so, I'd suggest going with the second approach.

c

On 8/4/20 10:27 PM, R Kannan wrote:
> Thanks for the help.
>
> I believe I had set the static IP because I am using my desktop as a 
> MythTV master backend and I did not want the IP to jump around a few 
> years back.
>
> Now for the life of me I cannot figure out where I had set the static 
> IP to be 192.168.1.90 (which is in the range of my old router). My new 
> router seems to be using 10.0.0.2 through 10.1.1.255. So I believe I 
> have to keep the static IP in this range
>
> ifconfig says...
>
> eth0      Link encap:Ethernet  HWaddr 38:60:77:c7:57:34
>           inet addr:192.168.1.90  Bcast:192.168.1.255 Mask:255.255.255.0
>           inet6 addr: fe80::3a60:77ff:fec7:5734/64 Scope:Link
>           inet6 addr: 2600:1702:28b0:d290:3a60:77ff:fec7:5734/64 
> Scope:Global
>           inet6 addr: 2600:1702:28b0:d290::447/128 Scope:Global
>           inet6 addr: 2600:1702:28b0:d290:d45e:1460:3561:f3df/64 
> Scope:Global
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:458563 errors:0 dropped:54217 overruns:0 frame:0
>           TX packets:247011 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:471035045 (471.0 MB)  TX bytes:50199927 (50.1 MB)
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>           RX packets:163310 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:163310 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:11274718 (11.2 MB)  TX bytes:11274718 (11.2 MB)
>
> These are the contents of the file /etc/network/interfaces (no mention 
> of eth0). Not sure where the static address is set.
>
> eth0      Link encap:Ethernet  HWaddr 38:60:77:c7:57:34
>           inet addr:192.168.1.90  Bcast:192.168.1.255 Mask:255.255.255.0
>           inet6 addr: fe80::3a60:77ff:fec7:5734/64 Scope:Link
>           inet6 addr: 2600:1702:28b0:d290:3a60:77ff:fec7:5734/64 
> Scope:Global
>           inet6 addr: 2600:1702:28b0:d290::447/128 Scope:Global
>           inet6 addr: 2600:1702:28b0:d290:d45e:1460:3561:f3df/64 
> Scope:Global
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:458563 errors:0 dropped:54217 overruns:0 frame:0
>           TX packets:247011 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:471035045 (471.0 MB)  TX bytes:50199927 (50.1 MB)
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>           RX packets:163310 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:163310 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:11274718 (11.2 MB)  TX bytes:11274718 (11.2 MB)
>
>
>
> On 8/4/20 8:29 PM, Carl T. Miller wrote:
>> Did you know you could assign more than one IP address
>> to an interface?  If you can set the Ubuntu desktop to use
>> DHCP, it will get you on your local lan and the internet.
>> Then you can just add a static IP address.
>>
>> If this sounds good, start by getting the desktop to use
>> DHCP and ensure that it's able to connect to your lan
>> and the internet.  We can figure out how to add the
>> static one afterwards.
>>
>> c
>>
>>
>> On 8/4/20 7:49 PM, R Kannan wrote:
>>> Hello,
>>>
>>> I just subscribed to comcast (did not have many choices 
>>> unfortunately) and got their modem/router (Voice and Data Modem
>>> ARRIS Group, Inc. TG1682G). Their dumbed down setup web application 
>>> seemed to work. The wireless is fine and the wired works with 
>>> devices using DHCP.
>>>
>>> But I have a desktop running ubuntu 16.04 using a static IP (for 
>>> various reasons) and when I connected it to the comcast router it 
>>> did not seem to have any connection. Is there something special I 
>>> need to do for devices not requiring IP or the subnet incorrect. I 
>>> cannot find what subnet addresses are being doled out by the router 
>>> as there is no simple web interface like in other modems.
>>>
>>> I thought I will ask here before I go up the chain of Comcast 
>>> unhelpful masses.
>>>
>>> Any help is appreciated.
>>>
>>> Thanks
>>>
>>> _______________________________________________
>>> mdlug mailing list
>>> mdlug at mdlug.org
>>> http://mdlug.org/mailman/listinfo/mdlug
>>
>> _______________________________________________
>> mdlug mailing list
>> mdlug at mdlug.org
>> http://mdlug.org/mailman/listinfo/mdlug
>