> Richard Andrews ha scritto:
> > This is a limitation in n2n. It only supports a single /24 network for a
> community. Putting A on 192.168.254.x will cause the problem you see above.
> >
> > I can't recall the reason for this restriction but IIRC it is to reduce the
> amount of traffic associated with broadcasts.
> With this configuration I've got a working routing:
>
> A: 192.168.254.1(virtial tun device on the same machine of B) <-->B:
> 192.168.250.1 (with -r switch on) <->C: 192.168.250.2
>
> in C I routed packet this way:
> "route add -net 192.168.254.0 netmask 255.255.255.0 gw 192.168.250.3"
> So now on C I can reach A with no problems.
Ah. Yes packet forwarding should work when enabled.
I just noticed A and B are on the same host. I didn't notice this last time.
Sorry for misleading you.
Bear in mind the security implications. n2n is a tunnel so the packets
arriving at B edge interface can be addressed any IP or port. Make judicial use
of internal firewalling when -r is turned on.
--
Rich
Make Yahoo!7 your homepage and win a trip to the Quiksilver Pro. Find out
more
_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
