|
|
| Author |
Message |
| 4 new of 13 responses total. |
maus
|
|
response 10 of 13:
| 
Jan 7 00:47 UTC 2007 |
Sweet. Thanks for posting your solution.
NBSD uses /etc/ifconfig.${ifname}? I thought the BSD standard was
/etc/hostname.${ifname}. One learns something new every day.
|
ball
|
|
response 11 of 13:
|
Jan 7 05:21 UTC 2007 |
I find ifconfig.{if} more intuitive.
,-------------, ,-------------,
|tinman | |almond |
| | | |
|192.168.3.129|---slip---|192.168.3.128| to LAN,
| | |192.168.0.254|---> router etc.
`-------------' `-------------'
As a temporary measure while I'm setting up software on
tinman, I would like almond to forward datagrams from its
SLIP interface out through the 10baseT port onto the LAN and
to accept datagrams for tinman from the LAN and forward them
down the right hole. I understand that I need to use proxy-
arp on almond so that it's MAC address is provided when some
-one tries to look up tinman. What should I use to forward
the datagrams though? NAT need not apply.
|
maus
|
|
response 12 of 13:
|
Jan 7 16:52 UTC 2007 |
You can set up almond to act as a router and advertise a route to
192.168.3.128/30 (you need to give it a /30, not a /31, since you lose
one address to the wire and one to the broadcast for any netblock, even
if a wire and broadcast are silly on a point-to-point link). I believe
all of the versions of BSD come with routed, which you can use to
accomplish this.
|
gull
|
|
response 13 of 13:
|
Jan 9 03:04 UTC 2007 |
Re resp:9: If you're only carrying IP, and only between two hosts, SLIP
is indeed simpler. (In fact, it's about as simple as it could possibly
get.) It gets messy in a hurry if you have to support multiple peers,
though, because it has no support for things like automatically
assigning IP addresses.
|