|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] network fixer hat
|
Paul DiSciascio wrote:
> You're correct, it's being passed to the default gateway. You won't
> be able to talk to anything in the 192.168.0.0/24 subnet without a NIC
> on that subnet or a router that knows about it. Even if you were to
> add a route for that subnet to your routing table, the return traffic
> won't know how to get back to the 10.10.10.0/24 subnet.
This makes sense. Oddly, I can get return traffic from the ftp daemon
Unfortunately, I cannot log in so maybe it's not working as it appears.
> However, if the host your traffic is originating from is a linux host,
Yes.
> 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.
Great! Although that did not solve the ftp login problem I'll leave it while I
work on accessing the target itself.
Thanks,
Eric
>
> ~Paul
>
> On Aug 28, 2009, at 1:22 PM, Eric wrote:
>
>> Once again I'm called on to wear my "network fixer" hat... but this
>> time it's in
>> my own office!
>>
>> 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. When I plug in the new
>> device and
>> try to access it via http or tftp from my Linux workstation - I get
>> nothing. Is
>> that because any request outside the 10.10.10.0/24 range falls
>> through the
>> routing table to "default" and then gets sent to the gateway - which
>> drops it as
>> non-routable?
>>
>> How can I "tweak" my routing on the Ubuntu (8.10) workstation to see
>> these types
>> of devices without messing up anything else?
>>
>> Here is the output of the route command:
>>
>> ~$ route
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric Ref
>> Use Iface
>> 10.10.10.0 * 255.255.255.0 U 1
>> 0 0 eth1
>> link-local * 255.255.0.0 U 1000
>> 0 0 eth1
>> default polaris 0.0.0.0 UG 0
>> 0 0 eth1
>>
>> I'm thinking this might work:
>>
>> route -v add -net 192.168.0.0 netmask 255.255.0.0 -dev eth1
>>
>> Would I add this permanently or just when I needed it?
>>
>> Thanks,
>> Eric
>> --
>> # Eric Lucas
>> #
>> # "Oh, I have slipped the surly bond of earth
>> # And danced the skies on laughter-silvered wings...
>> # -- John Gillespie Magee Jr
>> ___________________________________________________________________________
>> 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
>
> ___________________________________________________________________________
> 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
>
--
# Eric Lucas
#
# "Oh, I have slipped the surly bond of earth
# And danced the skies on laughter-silvered wings...
# -- John Gillespie Magee Jr
___________________________________________________________________________
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
|
|