Change ip address -

[Robert Nichols]

On 10/06/2015 03:19 AM, Bob Goodwin wrote:
> On 10/05/15 21:18, Robert Nichols wrote:
>>
>> All you needed to do was add a routing table entry to direct packets for
>> 1.1.1.1 out the appropriate interface. No need to mess up the rest of
>> your networking.
> .
>
> I was able to accomplish what I needed to do and the system was returned
> to normal without much difficulty but I am interested in your suggestion
> since this is something that comes up at times however I could use a
> some clarification of:
>
> "add a routing table entry to direct packets for
> 1.1.1.1 out the appropriate interface."
>
> After a bit of Googling I see the following which seems like it might
> apply to my need to access the Buffalo ethernet bridge device I needed
> to access after  doing a default "reset" to 1.1.1.1.
>
> "Directly Attached Network    The local network entry corresponds to the
> directly attached network. IP packets destined for the directly attached
> network are not forwarded to a router but sent directly to the
> destination. Note that the Gateway and Interface columns match the IP
> address of the node. This indicates that the packet is sent from the
> network adapter corresponding to the node's IP address."
>
> I don't know exactly how to do that, an example perhaps ...

       ip route add to 1.1.1.1 dev enp0s25

That's all there is to it. Your system now knows that address 1.1.1.1
can be reached directly (no gateway) on that interface. At some point
you'll probably want to run "ip route delete 1.1.1.1", but there's no
rush unless you want to connect to a 1.1.1.1 address out there on the
internet.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.