Re: Routing confusion

2008-02-29 Thread Eric Anderson


I forgot to send the ifconfig for the load balancer as well.

$ ifconfig -a
fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet x.y.187.253 netmask 0xff00 broadcast x.y.187.255
inet6 fe80::240:d9ff:fe02:48fe%fxp0 prefixlen 64 scopeid 0x1
inet x.y.187.8 netmask 0x broadcast x.y.187.255
inet x.y.187.10 netmask 0x broadcast x.y.187.255
ether 00:40:d9:02:48:fe
media: Ethernet autoselect (100baseTX full-duplex)
status: active
fxp1: flags=c843UP,BROADCAST,RUNNING,SIMPLEX,LINK2,MULTICAST mtu 1500
inet 192.168.254.1 netmask 0xff00 broadcast 192.168.254.255
inet6 fe80::240:d9ff:fe02:48ff%fxp1 prefixlen 64 scopeid 0x2
ether 00:40:d9:02:48:ff
media: Ethernet autoselect (100baseTX full-duplex)
status: active
faith0: flags=8002BROADCAST,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500
sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552

I guess my biggest question is, why do the IPs .128, .129, .130, .131 
appear in the routing tables where they're NOT defined?  I don't get it?


Ok, as a Solaris (and Linux) guy, I'm thoroughly confused by some routing 
issues going on in this FreeBSD-based load balancer that I'm working on.


This box has one upstream NIC (fxp0) and a 4-port (hub?) as fxp1.

Currently, it has two cables plugged into it (server1 and server2), and two 
domains being load balanced:


192.168.254.128, 192.168.254.130 server1
192.168.254.129, 192.168.254.131 server2

I guess my first question is, why are these IP addresses even registered on 
the load balancer?  These IPs are plumbed and active on server1 and server2 
respectively.  I'm assuming the below is some kind of routing deal, but why 
is a route defined on the routing server?


I'm trying to add another server (192.168.254.254) that can be accessed from 
the load balancer, server1 and server2.


Seems simple enough:

route add -host 192.168.254.254 192.168.254.1

but that didn't work.

I guess I need to figure out how to define 192.168.254.254 the same as 
.128, .129, .130, .131 but I just can't figure it out because FreeBSD's 
netstat output is so different from Solaris (or Linux).


Can anyone else?  Let me know if you need more clarification..

192.168.254.1:# netstat -nr

DestinationGatewayFlagsRefs  Use  Netif Expire
defaultx.y.187.1   UGSc   54607523 55161243   fxp0
x.y.187/24  link#1 UC  60   fxp0
x.y.187.1   00:07:b4:00:bb:01  UHLW70   fxp0918
x.y.187.2   00:11:5d:9c:d0:00  UHLW00   fxp0120
x.y.187.3   00:0f:f8:de:f4:00  UHLW00   fxp01187
x.y.187.4   00:14:22:73:0a:20  UHLW0 9254   fxp01196
x.y.187.8/32link#1 UC  00   fxp0
x.y.187.10/32   link#1 UC  00   fxp0
x.y.187.243 link#1 UHLW77   fxp0
x.y.187.246 00:17:31:ef:5f:f9  UHLW 7528 7528   fxp0   807
127.0.0.1  127.0.0.1  UH  08lo0
192.168.254link#2 UC  60   fxp1
192.168.254.1  00:40:d9:02:48:ff  UHLW07lo0
192.168.254.12800:14:22:72:87:67  UHLW7 13663296   fxp1   857
192.168.254.12900:14:22:72:91:48  UHLW7 12663561   fxp1   1138
192.168.254.13000:14:22:72:87:67  UHLW7   685454   fxp1   918
192.168.254.13100:14:22:72:91:48  UHLW8   560930   fxp1   918
192.168.254.255ff:ff:ff:ff:ff:ff  UHLWb   04   fxp1


___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Routing confusion

2008-02-29 Thread Bruce M. Simpson

Eric Anderson wrote:
I guess my biggest question is, why do the IPs .128, .129, .130, .131 
appear in the routing tables where they're NOT defined?  I don't get it?


You are not seeing forwarding table entries. You are seeing ARP entries 
- the LLINFO flag is set (L). This is a legacy behaviour we haven't done 
away with just yet.


BMS

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to [EMAIL PROTECTED]