Installed openWRT to my Raspberry PI 5. I think I am on my fourth attempt. This time I put it back on the keyboard, mouse and monitor.
Several issues:
1). The keyboard works but does not echo to the monitor.
2). The system auto does an auto login, is this correct?
Several Questions. I have 2 windows PC's and a Raspberry PI4 that I want to install behind the firewall for now.
Network is 192.168.1.x
ISP connection is 192.168.1.254
Last attempt yestderday ended in disaster and I have no idea why.
1st windows PC that I use as a configuration point works great setting up with luci and ssh into openWRT. No outside internet.
Changing the default gateway to 192.168.1.1 fixed the no internet. Of course I could no longer get to the other PC, or PI4.
Changing the second PC to the 192.168.1.1 gateway, I could now talk to the second PC and it saw the internet. All seemed to be going well.
Changing the gateway on the PI4 to 191.168.1.1 and everything turned to junk. I could not talk to anyone from anywhere and none of the computers was seeing the internet.
Anythoughts?
Do you have a 2nd USB based Ethernet port ?
If you do, wan and lan can't use the same subnets.
No I am using a waveshare hat with dedicated eth port.
Ok, so there's a 2nd port, is it detected by OpenWRT?
Yes, etho is 192.168.1.1, eth1 is dynamic from isp modem. 192.168.1.x. depending on what the dhcp server configures.
Then my 1st reply is valid, change upstream device's subnet or RPIs LAN subnet.
eth0 (192.168.1.1) is configured as br-lan
What part of "can't be the same as wan" is tricky ?
So you are saying eth1 needs to be a subnet from the isp modem, 192.168.1.x.
and eth0 (br-lan) needs to be 192.168.x.1.
Where x <> 1 in 192.168.x, if RPi is supposed to be used as router.
Ok thanks, don't think I have seen that written anywhere. Since openWRT comes up as 192.168.1.1. I ASSUME I was ok. Going to be a good bit of work, my entire lan is configured as 192.168.1.x. lots of stuff will need to be changed, before I embark on my next attemp.
You could try to change the upstream subnet on ISP's device, if doable.
That would be the easy way, but my isp gets touchy about making config changes to the modem. If they have an issue first thing they point to is you changed the config on the modem.
Seems strange to me that they can't be on the same subnet as they should really not be connected at no point does eth0 and eth1 traffic end up connecting except at opposite ends of the firewall.
Same subnet on both sides confuse the routing, that's why.
This is common in all routers. There cannot be 2 interfaces with identical addressing. As already mentioned, IP forwarding (otherwise called "routing") won't work with the IPs are identical.