On 02/01/15 10:37, Otto Moerbeek wrote:
On Sun, Feb 01, 2015 at 10:26:35AM -0600, Edgar Pettijohn wrote:

On 02/01/15 10:13, Rosen Iliev wrote:
Hi Edgar,

Ignore my previous email.

You don't need the route
it should bu just:
inet 104.238.145.48 255.255.254.0 NONE

Rosen
I thought it should be that easy, but I get the same results. No ping :(
I'm wondering if its a virtual machine issue.
Are you sure you need a second interface? It might very well be your
vm hoss has the second address set up on the the same interface as the
first.

        -Otto

Possibly. I could have sworn I got it working last night by adding an alias for the new ip to the vio0 interface, but then it wasn't working this morning. Maybe I'll revisit that tactic.

# ifconfig

vio1: flags=28843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6> mtu 1500
         lladdr 52:54:00:86:36:94
         priority: 0
         media: Ethernet autoselect
         status: active
         inet 104.238.145.48 netmask 0xfffffe00 broadcast 104.238.145.255

# route show

Routing tables

Internet:
Destination        Gateway            Flags   Refs      Use   Mtu Prio Iface
default            108.61.222.1       UGS        3      310 -     8 vio0
104.238.144/23     link#2             UC         0        0 -     4 vio1
vpn.pettijohn-web. 52:54:00:86:36:94  UHLl       0        0 -     1 lo0
108.61.222/24      link#1             UC         2        0 -     4 vio0
108.61.222.1       74:8e:f8:48:67:80  UHLc       1        0 -     4 vio0
pettijohn-web.com  56:00:00:03:ef:10  UHLl       0        0 -     1 lo0
108.61.222.170.vul 52:54:00:cb:e8:f1  UHLc       0        0 -     4 vio0
loopback           localhost          UGRS       0        0 32768     8 lo0
localhost          localhost          UH         5      120 32768     4 lo0
BASE-ADDRESS.MCAST localhost          URS        0        0 32768     8 lo0
I appreciate the assistance thus far. Should have mentioned I disabled pf during my testing. Have to take the kids to the park. I'll keep trying later.

Reply via email to