[Sis-SCPS-INTEREST] help with configuring odd hub-and-spoke network

[Dan Miller]

Hmmm... actually, no, if I reduce the data rate to correctly reflect header overhead, I *don't* get channel overrun when I start up the second transfer from the second remote.

So, I guess my only pending question is how do I change BIF_RATE dynamically??
  ----- Original Message ----- 
  From: Dan Miller 
  To: scps mailing list 
  Sent: Monday, January 29, 2007 13:10
  Subject: [Sis-SCPS-INTEREST] help with configuring odd hub-and-spoke network


  I'm porting our satellite-network software to kernel 2.6 (from 2.2.19 which we've used for years).  We'll be using scps for tcp acceleration.  We're working quite well with hub gateway and one remote gateway; ftp transfers between nodes outside the gateway, run at 88.5% of our 3Mbit/second link.

  However, we typically use a hybrid hub-and-spoke configuration; from a network perspective, each remote is on a separate subnet... for example:

  hub eth1   192.168.10.1/30  <-----------> remote eth1  192.168.10.2/30
  hub eth1:1 192.168.10.5/30  <-----------> remote eth1  192.168.10.6/30

  However, a single carrier from the hub is received by all remote units.  So the hub has ONE 3Mbit/sec link available, regardless of how many remote gateways it is communicating with.  The scps gateway doesn't seem to understand this; as long as I only communicate with one remote at a time, it meters data out from the hub at the expected rate.  However, if I start communicating with two remotes simultaneously, it floods the eth1 driver with packets; it appears to believe it has TWO 3Mbit channels available??

  Is there some way for me to communicate my requirements to the machine??

  Second question:
  I need to be able to change the data rates on the fly, hopefully without having to stop/restart scps.
  Can I use gw_route_cmdr for this purpose??  If not, is there any other way to do this??

  Dan Miller

  My rfile from the hub machine (I am using the TUN interface):

  # GW Resource File - comments are allowed, starting with '#'.
  #    Comments can be anywhere EXCEPT between parameter values.

  # interface A info
  AIF_NAME eth0
  AIF_RATE 100000000
  AIF_BUF  32768
  AIF_RBUF 32768
  AIF_CC  1
  AIF_TCPONLY 1
  AIF_MTU  1500
  #AIF_TAP_NAME tap0

  # interface B info
  BIF_NAME  eth1
  BIF_RATE  3072000
  BIF_BUF  300000
  BIF_RBUF  300000
  BIF_CC   0
  BIF_MINRTO  600000
  #BIF_TAP_NAME tap1

  # IPFW info
  C_DIVPORT 52000  
  C_TAP_REMOTE_ACCESS 1










------------------------------------------------------------------------------


  _______________________________________________
  Sis-SCPS-INTEREST mailing list
  Sis-SCPS-INTEREST at mailman.ccsds.org
  http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-scps-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sis-scps-interest/attachments/20070129/ff022a59/attachment.htm