I can't, hence the reason I setup an aliased interface. My LAN is setup for 192.168.1.x and the modem is 192.168.2.1, I can't think of any other way to do it unless I create a static route maybe?
Open to suggestions :) Thanks, Stephen On 12/13/09 8:01 PM, Roberto C. Sanchez wrote: > Stephen Brown wrote: >> I'm running Shorewall 4.4.0 on a two NIC system. eth0 is facing the >> internet on a DSL circuit, and eth1 is facing my local LAN. >> >> I setup a virtual interface on eth0:0 as 192.168.2.2 to be able to >> access the modem configuration, the modem's address is 192.168.2.1 I'm >> able to get to it ok, but I am having some trouble enabling a few >> services, specifically NTP and SNMP (the modem supports both) > > Why on earth would you need to use an aliased interface for that? It > sounds like you are just complicating things unnecessarily. > > What happens if you try accessing the modem without the aliased interface? > > Regards, > > -Roberto > > > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > > > > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
