[Going nuts] Can't share the connection to the Internet

From: The Yeti (goatravellers_at_yahoo.com)
Date: 07/30/04


Date: 30 Jul 2004 12:03:34 -0700

It's been since monday that I'm trying to share the connection to the
Internet.

I have this FreeBSD computer connected to the Internet (PPPoE), with
NAT, and I have other computers connected to it through a hub.

Each computer pings well the FreeBSD machine. But it can't ping
google. I tryed all configuration that I thought about, and read
enough man pages and forum threads. Here are some infos:

/etc/rc.conf
ppp_enable="YES"
ppp_mode="ddial"
ppp_profile="internet"
ppp_nat="YES"
gateway_enable="YES"
#firewall_script="/etc/rc.firewall"
#firewall_enable="YES"
#firewall_type="OPEN"
natd_enable="YES"
natd_interface="tun0"
natd_flags=""
hostname="branquinho.network"
ifconfig_rl0="192.168.0.1/24"
ifconfig_sk0="192.168.1.1/24"
inetd_enable="YES"
keymap="br275.iso.acc"
linux_enable="YES"
moused_enable="YES"
sshd_enable="YES"
usbd_enable="YES"

/etc/ppp/ppp.conf
default:
        enable dns
        set ifaddr 0 0

internet:
        allow users charles
        set device PPPoE:rl0
        set authname whatever
        set authkey whatever
        add default HISADDR

/etc/hosts
:1 localhost.network localhost
127.0.0.1 localhost.network localhost
192.168.0.1 branquinho.network branquinho
192.168.1.1 branquinho.network branquinho
192.168.0.3 cinza.network cinza

branquinho# ifconfig
fwe0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 02:e0:18:26:ba:11
        ch 1 dma -1
sk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::20c:6eff:fe74:3371%sk0 prefixlen 64 scopeid 0x2
        ether 00:0c:6e:74:33:71
        media: Ethernet autoselect (100baseTX
<full-duplex,flag0,flag1>)
        status: active
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=8<VLAN_MTU>
        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
        inet6 fe80::208:54ff:fe10:80b2%rl0 prefixlen 64 scopeid 0x3
        ether 00:08:54:10:80:b2
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
        inet 200.193.168.220 --> 200.103.132.254 netmask 0xffffffff
        Opened by PID 217

I can ping Google from this FreeBSD machine, but not from other
machines of the LAN. From other PCs, I can only ping local machines.
Thanks,

Charles.



Relevant Pages

  • FreeBSD 5.1 <-> WinXP Networking Problem UPDATE
    ... am able to ping back and forth ... ... I tried pinging from Freebsd to 192.168.0.4 the ... WinXP #2 machine. ... flags=8843mtu ...
    (freebsd-questions)
  • cant route.
    ... I just setup some configuration for routing from the Freebsd to the ... Test result is the WinXP is only able to ping 192.168.1.1, ... fxp0: flags=8843mtu 1500 ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Home Network, step by step?
    ... which one is my incoming internet connection? ... bfe0: flags=8843mtu 1500 ... >>recognise the information in the FreeBSD handbook. ... > to use one of the computers you already have and NAT. ...
    (freebsd-newbies)
  • Re: freebsd-net Digest, Vol 181, Issue 9
    ... FreeBSD 6.1 + ath0 + NAT ... connection to the Internet, and a Netgear WG311T wireless Ethernet card ... ath0: flags=8843 mtu 1500 ...
    (freebsd-net)
  • Re: POP3 Connector Issue
    ... the DF number will always be 28 bytes less than the MTU ... using this ping test. ... your server is not connected to the Internet." ... the router should return the message "packet needs to ...
    (microsoft.public.windows.server.sbs)