SUMMARY: Routing problem

Resolved:

Stuart Saxon suggested to check with dladm, which revealed:

bge0            link: up        speed: 1000  Mbps       duplex: full
bge1            link: up        speed: 1000  Mbps       duplex: full
bge2            link: down      speed: 0     Mbps       duplex: unknown
bge3            link: unknown   speed: 0     Mbps       duplex: unknown

The machine was plugged into bge3 not bge2.

Thanks!

S.

ORIGINAL PROBLEM:

I have a log server
(http://www.balabit.com/network-security/syslog-ng/log-server- 
appliance/)
that I want to use on my network.  It is delivered with 192.168.1.1
out of the box.  I want to change its IP to go on the network.  It can
only be configured via a web interface.

I've plugged a crossover cable between it's network connection, and
one of my servers, plumbed bge2, configured bge2 to be 192.168.1.2,
brought it up, and added a host route, but I can't route to it.

Here's the diagnostics:

# ifconfig -a; netstat -rn
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
        inet 127.0.0.1 netmask ff000000
bge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu  
1500 index 2
        inet 172.19.33.250 netmask ffffff00 broadcast 172.19.33.255
        ether 0:14:4f:7b:10:62
bge1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu  
1500 index 3
        inet 172.20.252.173 netmask fffffc00 broadcast 172.20.255.255
        ether 0:14:4f:7b:10:63
bge2: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 4
        inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
        ether 0:14:4f:7b:10:64

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use      
Interface
-------------------- -------------------- ----- ----- ----------  
---------
default              172.20.252.2         UG        1      29975
172.19.33.0          172.19.33.250        U         1        373 bge0
172.20.252.0         172.20.252.173       U         1       9879 bge1
192.168.1.1          192.168.1.2          UGH       1          0
224.0.0.0            172.20.252.173       U         1          0 bge1
127.0.0.1            127.0.0.1            UH       20    6110083 lo0

traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets
1  sta-wf-fr.telewest.co.uk (192.168.1.2)  0.167 ms !H  0.185 ms !H
0.049 ms !H
ICMP Host Unreachable from gateway fms-kn-t1 (172.20.252.173) for icmp
from fms-kn-t1 (172.20.252.173) to 192.168.1.1

Have I missed something obvious?

S.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers