On Thu, 18 Mar 1999, Juan Carlos Castro y Castro wrote:
> Hi Dale... sorry to hear you're still in this mess.
>
> For some reason I thought the broadcast packets were being sent as
> 10.255.255.255 (according to the netmask) which would be the network's
> proper broadcast address. With 255.255.255.255 as a destination address,
> I can't see how they could travel both ways. Speaking of which, what is
> the philosophycal difference between 255.255.255.255 and, say,
> 192.168.2.255 or 10.255.255.255?
Nope, unfortunately they're sent to 255.255.255.255. There are also
network broadcasts to 10.75.250.255 and 10.42.250.255 ; I think these can
stay on their respective sides of the tunnel. It may not matter; I'll
propagate them if I can.
255.255.255.255 will be heard by *ALL* hosts on a network. It's usually
used for DHCP requests, though I have seen a few software packages that
use it as a broadcast address when sending data to clients on a network.
> Maybe you could research the bridging support in new versions of the
> kernel. I don't know if it's solid enough, though, and I've never tried
> it myself.
I did... it looks to me like it will do Ethernet bridging, but not remote
bridging such as I need.
> Or... what about a little cheating? Since you're hacking the kernel
> routing code anyway, why not masquerade incoming 255.255.255.255
> WAN-bound packets from the LAN as 10.255.255.255, and do the reverse to
> LAN-bound packets from the WAN?
I'm thinking about that, but I can't see where ipfw or ipchains can do it.
I'm not a programmer of sufficient skills that I could write the required
app in C or Perl, though I can see how it could be done. I can make minor
hacks to make someone else's code do what I need it to, but that's not the
same as programming... 8-P
Actually, the broadcast packets that are getting sent now are bouncing
from the wrong side of the remote gateway, so it'd be a little different.
I'm going to have a look at the IP tunnel code tonight... sigh.
Dale
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
