ATT Fiber Router not Allowing me to Create a Static Route

P

pmgrape

New member
My ATT fiber optic router won't allow me to set up a static route. It only allows IP passthrough. I have set up a Raspberry pi via FPP with a static IP wifi address for my home network under the same subnet. I also have a LAN static address set up on the raspberry pi under a different subnet to communicate with my Kulp K8 pi and future controllers, receivers, etc. It is my understanding that I need to set up my home router with a static route to make the magic happen but my ATT fiber optic router says hell no we don't do that and only does IP passthrough.
Now I am super confused as to if IP passthrough will work, how to set up IP passthrough, or do i need to add my own router that allows static routing. I was a firefighter/paramedic and know virtually nothing about networking other that what youtube videos have poisoned and overloaded my brain with.
Any help would be greatly appreciated.
Thanks and Merry Christmas you filthy animal!
 
I to used to be a paramedic and a firefighter in Texas, so thank you. I also have an AT&T fiber router, so here is my setup:
Router is set to 192.168.1.1; I have DHCP enabled from 192.168.1.2 - 192.168.1.99. I have my Pi on a separate switch and all of the IPs on that are set to static; 192.168.2.10 (16 controllers). Then I have a USB WiFi dongle (gives a little bit better range than built in) set to 192.168.1.150 (so it's static on my home router. Attached are pictures of my setup.switch
 

Attachments

  • Image1.jpg
    Image1.jpg
    53.2 KB · Views: 8
  • Image2.jpg
    Image2.jpg
    40.3 KB · Views: 8
  • Image3.jpg
    Image3.jpg
    58 KB · Views: 8
I think you'll discover that the best and least painful way to deal with commercial routers, especially those tied to an internet service, is to put your show on a private network. This may involve a separate router and IP setup, but isolating it from the junk the internet providers give you, it becomes the easiest and most efficient way to network a show. Others may argue the point, but probably not much....
 
dirknerkle said:
I think you'll discover that the best and least painful way to deal with commercial routers, especially those tied to an internet service, is to put your show on a private network. This may involve a separate router and IP setup, but isolating it from the junk the internet providers give you, it becomes the easiest and most efficient way to network a show. Others may argue the point, but probably not much....
Click to expand...
I bought a router today but haven't had time to configure it. That will be Mondays project! I'm figuring out really quick exactly what you said and 100% agree.
Thank You
 
joeytx said:
I to used to be a paramedic and a firefighter in Texas, so thank you. I also have an AT&T fiber router, so here is my setup:
Router is set to 192.168.1.1; I have DHCP enabled from 192.168.1.2 - 192.168.1.99. I have my Pi on a separate switch and all of the IPs on that are set to static; 192.168.2.10 (16 controllers). Then I have a USB WiFi dongle (gives a little bit better range than built in) set to 192.168.1.150 (so it's static on my home router. Attached are pictures of my setup.switch
Click to expand...
I bought a router today before I saw your post about the dongle and enabling DHCP. I may pick get one on order from Amazon and try to figure out how to enable DHCP. I have options now! Med math and acid/base balance were easier that this networking stuff.
Thanks Brother
 
pmgrape said:
I bought a router today before I saw your post about the dongle and enabling DHCP. I may pick get one on order from Amazon and try to figure out how to enable DHCP. I have options now! Med math and acid/base balance were easier that this networking stuff.
Thanks Brother
Click to expand...
what exactly do you mean that you have your pi on a separate switch? subnet?
 
Your house network is on a subnet. Typically 192.168.1.x. That means up to 256 devices can talk to each other.

Some of use put the show network on its own switch with its own AP etc. This switch is connected to the house network on a different port on your edge router. Then you set up all of those devices for that router port on a different subnet. For example 192.168.2.x. But now, none of the .1.x device can talk to the .2.x devices. That is a job for a router. A good router can be configured to forward traffic between the two networks (a static route if you will) but it is best if you let the router make such a decision. Unfortunately, routers like the one you get from your ISP have this level of complexity blocked/turned off/ dummied down so that they do not get service calls from users that accidentally try to change settings and then blow everything up.

FYI: I do not let the ISPs router or AP into my house. I would never want someone other than me having the ability to access my network and potentially open it to the internet. I run a full featured router and 16 subnets of which my show is just one. I also run a PFSENSE firewall between the cable modem and the router to provide security. My ISP has no way through that.
 
Just an FYI, if you want to have access to you show network (on one subnet) from a computer which is on another subnet you can create a static route:
Example:
My home network is 192.168.1.x ; My computer has a static IP of 192.168.1.105.
My show Pi has two IPs: Ethernet 192.168.2.10 and WiFi 192.168.1.150

Create route:
route -p ADD 192.168.2.0 MASK 255.255.255.0 192.168.1.150
subnet for SHOW ^ WiFi ^^

This will create a route from the computer which it's run on to allow you to go through the WiFi IP to the show IP.

Delete Route:
route delete 192.168.2.0 mask 255.255.255.0 192.168.1.150

See Routes:
ROUTE PRINT

This is what mine prints out:

Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.2.0 255.255.255.0 192.168.1.150 1
 
You must log in or register to reply here.
Back
Top