Hello Alexander,
First I'd never done anything with an 'arp request' yet. So have to read to
understand what it does :-/
> No, get rid of the address 192.168.1.104 on desktop, not needed
> Hope this helps.
This DID!
Honestly it seemed backwards to me. I thought you needed to route everything,
so I'd need to route my DESKTOP too. I guess that's all handled then by the
LINUXROUTER.
So with your advice, removing that 192.168. address from DESKTOP,
PUBLIC INTERNET
|
ATT MODEM
| eth0: IP ADDRESS = 192.168.1.254 (Web User Interface)
|
| eth1: IP ADDRESS = 99.X.X.X
| IP ADDRESS = 192.168.1.25
LINUX ROUTER
| eth0: IP ADDRESS = 172.30.8.1
|
ETHERNET SWITCH
|
| eth0: IP ADDRESS = 172.30.8.104
DESKTOP
ON the "DESKTOP", I can
-- ping the "LINUX ROUTER" @ 192.168.1.25
-- ping the "ATT MODEM" @ 192.168.1.254
-- access the 'Web User Interface' on the "ATT MODEM" in a browser
-- access everything on the Public Internet
That's great!
So I took one next step and added a VoIP box attached to the ATTMODEM
PUBLIC INTERNET
|
ATT MODEM
| eth0: IP ADDRESS = 192.168.1.254 (Web User Interface)
| eth1: IP ADDRESS = 192.168.1.64 (VoIP Web UI)
<<<<+++++++++++++++++++
|
| eth1: IP ADDRESS = 99.X.X.X
| IP ADDRESS = 192.168.1.25
LINUX ROUTER
| eth0: IP ADDRESS = 172.30.8.1
|
ETHERNET SWITCH
|
| eth0: IP ADDRESS = 172.30.8.104
DESKTOP
ON the LINUXROUTER, I can
-- ping the 'VoIP Web UI'
-- web access the 'VoIP Web UI'
ON the "DESKTOP", I can NOT
-- ping the 'VoIP Web UI'
-- web access the 'VoIP Web UI'
I guess there's an additional 'hop' that's mucking up the works?
Does access to THAT need to be configured on the LINUXROUTER, or on the
ATTMODEM itself?
Thanks,
Thad
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
