On Wednesday 22 September 2004 23:18, Edwin Groothuis wrote: > I have the same situation here and the solution was to let the ADSL > router forward all unknown traffic to my router. How to do that is > router specific, but it can be done. > > Then, with the tunnels: > > central# ifconfig gif1 inet > gif1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 > tunnel inet 218.185.88.66 --> 203.111.122.8 > inet 10.10.12.1 --> 10.10.12.2 netmask 0xffffffff > > remote# ifconfig gif1 inet > gif1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280 > tunnel inet 192.168.1.1 --> 218.185.88.66 > inet 10.10.12.2 --> 10.10.12.1 netmask 0xffffff00 > > 203.111.122.8 is my ADSL routers address. > 192.168.1.1 is my computers RFC1918 address. > > Two static routes, one on each machine, and it works. >
Thanks for pointer! I will check this with DSL router I have. There, however, might be another problem - my DSL router could be also NAT'ed (and most likely it is), so it draws us the following picture: (LAN) <-NAT-> (FreeBSD) <-NAT-> DSL Router <- ??? -> ISP/Internet Basically I'm unsure whether "???" is a normal, direct connection to internet via ISP, or it is also NAT'ed. I'm most sure that it is NAT, because I've been getting one IP (e.g. my public IP on the net as I appear) for ~1 month (e.g. it never changed, although there is DHCP of course). Well, hell knows how many further NATs I have there - at least I know about two already. I guess time to visit ISP.. > Edwin regards, M. _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
