JP Vossen on 30 Aug 2009 17:03:17 -0700


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] network fixer hat


 > On Aug 28, 2009, at 1:22 PM, Eric wrote:

[...]
>> I use an internal 10.10.10.0/24 IP range in my home/office. 
>> Unfortunately, most devices that I'm going to add to the network to
>> configure (wireless routers, NAS, etc) have 192.168.[0|1].0/24
>> addresses.
[...]

> Date: Fri, 28 Aug 2009 16:45:30 -0400
> From: Paul DiSciascio <thenut@bytemonkey.net>

[...]
> However, if the host your traffic is originating from is a linux host,  
> you can get around this by adding an alias to your NIC with an IP on  
> the other subnet.  For example, to add an alias with an IP of  
> 192.168.1.12 to eth0, you would do the following:
> 
> ifconfig eth0:1 192.168.1.12 netmask 255.255.255.0
> 
> and you'll notice the appropriate route is now there and traffic  
> should flow normally.

+1 for this, beat me to it.

Notwithstanding Brent's more detailed and canonical explanation...this 
is a lot easier.  I either do this, or just slap a random laptop onto 
the device, get DHCP from there, log in and change the IPA, then re-wire 
as needed.

Good luck,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP            |:::======|      http://bashcookbook.com/
My Account, My Opinions     |=========|      http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug