NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Using a Static IP Address on a Raspberry Pi Connected to my Nighthawk Router
Hi, I have a couple of Raspberry Pis connected to my Home Network which is provided by my Netgear Router. Ideally I want to set up a static IP Address for each of these Pis, but I cannot make th...
schumaku wrote:So t the end of the day, what went wrong and broke the Pi <-> D7800 connection and the Internet connection finally?
The router was unaware of the presence of the Webserver, so didn't route Google traffic when I was trying to use the Static IP.
I think that I should clear up a few things. The WiFi generated by the Netgear Router doesn't come into this and neither does the WiFi on the Pi, because it has been disabled. The only WiFI that is relevant to this discussion (and then only peripherally) is that provided by two Outdoor WiFi Antennas which allow the Visitors (or staff if they so wish) to open the splash page of the Captive Portal and thence open the content hosted on the Model Town's private Website which provides Audio Guides, etc. These Outdoor Antennas are connected to the 192.168.0.* subnet and are primarly provided for Visitors. Staff and volunteers can plug into a switch on the 192.168.0.* subnet or log into the network on the Outdoor WiFI Antennas and then SSH into the Pis.
All this is not particularly useful (other than for interest :-) ). The IP Addresses that I want to be static are on the Main Office Router side (the Netgear for my Test Rig). Since my posting earlier this morning, I have kind of accepted that the main Router doesn't show the devices added with a static IP. It isn't really a problem, I now feel that as long as I understand why this is occuring I can live with it. My initial problem was caused by the lack of visibility of what was connected to the Router; I had got used to seeing this.
As far as pinging the Netgear Router from the 192.168.0.* subnet is concerned; no that doesn't work. I never expected it to (it didn't stop me trying :-) ). Both of these devices purposely prevent it. The Webserver (which includes the Captive Portal software) uses iptables to turn the Webserver Pi into router and block practically everything going out on that Ethernet port; that's what it's for. Similarly the VPN Server also uses iptables to create a router that uses MASQUERADE (eg NAT) to prevent traffic going out, except in response to valid packets from an external device using the VPN service.
Anyway. Thanks for the insights that everyone has provided in this thread. Even the ones that were off beam have helped me work though this problem and come to an understanding of what is going on.
Ok, so you have a wired connection on one of the Ethernet ports for the link to the router - not much of a difference: A static config on that interface should to the job with a few potential deal breakers like WiFI isolation. The ping and traffic capturing was clearly intended for testing the link from the Pi to the router of course. Anything beyond is your Pi project business 8-). Everything I wrote above does still apply - as all that has to work and that's the only part where the router is affected.
So t the end of the day, what went wrong and broke the Pi <-> D7800 connection and the Internet connection finally?
schumaku wrote:So t the end of the day, what went wrong and broke the Pi <-> D7800 connection and the Internet connection finally?
The router was unaware of the presence of the Webserver, so didn't route Google traffic when I was trying to use the Static IP.