Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 26

Thread: DHCP clients no internet access

  1. #11
    Join Date
    Jan 2009
    Location
    ::1
    Beans
    2,485

    Re: DHCP clients no internet access

    from the client can you 'ping 192.168.33.1'?

  2. #12
    Join Date
    Jun 2009
    Location
    Open Linux Forums
    Beans
    2,710

    Re: DHCP clients no internet access

    Quote Originally Posted by sanderj View Post
    from the client can you 'ping 192.168.33.1'?
    yes, and i can even do a dig <network> axfr or ping other clients on the lan.
    this is however very slow, it takes about 24 seconds to send and receive 4 packets...
    Last edited by Leppie; June 21st, 2010 at 09:49 PM.
    I'm not antisocial. I'm just not user friendly...
    Open Linux Forums

  3. #13
    Join Date
    Jan 2009
    Location
    ::1
    Beans
    2,485

    Re: DHCP clients no internet access

    Well, run all command I gave, and post the output here, including "ip route show"

  4. #14
    Join Date
    Jun 2009
    Location
    Open Linux Forums
    Beans
    2,710

    Re: DHCP clients no internet access

    here we go:
    Code:
    ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:26:2d:1e:21:dc  
              inet addr:192.168.33.71  Bcast:192.168.33.255  Mask:255.255.255.0
              inet6 addr: fe80::226:2dff:fe1e:21dc/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:88 errors:0 dropped:0 overruns:0 frame:0
              TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:17264 (17.2 KB)  TX bytes:11908 (11.9 KB)
              Interrupt:18 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:197 errors:0 dropped:0 overruns:0 frame:0
              TX packets:197 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:21734 (21.7 KB)  TX bytes:21734 (21.7 KB)
    Code:
    ip addr show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
        link/ether 00:26:2d:1e:21:dc brd ff:ff:ff:ff:ff:ff
        inet 192.168.33.71/24 brd 192.168.33.255 scope global eth0
        inet6 fe80::226:2dff:fe1e:21dc/64 scope link 
           valid_lft forever preferred_lft forever
    3: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
        link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
    Code:
    ip route show
    192.168.33.0/24 dev eth0  proto kernel  scope link  src 192.168.33.71 
    169.254.0.0/16 dev eth0  scope link  metric 1000 
    default via 192.168.33.1 dev eth0  metric 100
    I'm not antisocial. I'm just not user friendly...
    Open Linux Forums

  5. #15
    Join Date
    Jan 2009
    Location
    ::1
    Beans
    2,485

    Re: DHCP clients no internet access

    Quote Originally Posted by Leppie View Post
    indeed, the results are the same as before.
    here's my setup:
    internet <-> router 192.168.2.1 <-> 192.168.2.254 :server: 192.168.33.1 <-> lan
    Is your server doing NAT between the LANs?

    If not: does your router know where the network 192.168.33 is? If not, you have a problem ...

  6. #16
    Join Date
    Jun 2009
    Location
    Open Linux Forums
    Beans
    2,710

    Re: DHCP clients no internet access

    Quote Originally Posted by sanderj View Post
    Is your server doing NAT between the LANs?
    most howto's state that only ip4 forwarding needs to be enabled in the sysctl.conf.

    Quote Originally Posted by sanderj View Post
    If not: does your router know where the network 192.168.33 is? If not, you have a problem ...
    fraid not...

    please some advice?
    I'm not antisocial. I'm just not user friendly...
    Open Linux Forums

  7. #17
    Join Date
    Jan 2009
    Location
    ::1
    Beans
    2,485

    Re: DHCP clients no internet access

    Quote Originally Posted by Leppie View Post
    most howto's state that only ip4 forwarding needs to be enabled in the sysctl.conf.


    fraid not...

    please some advice?
    Probably easiest to do NAT on your Ubuntu server. See http://ubuntuforums.org/showthread.php?t=713874

    FYI: I've never done this myself.

  8. #18
    Join Date
    Jun 2009
    Location
    Open Linux Forums
    Beans
    2,710

    Re: DHCP clients no internet access

    many thanks, the clients now have internet access
    the only thing is that now i can no longer ping between the clients.
    I'm not antisocial. I'm just not user friendly...
    Open Linux Forums

  9. #19
    Join Date
    Jan 2009
    Location
    ::1
    Beans
    2,485

    Re: DHCP clients no internet access

    Quote Originally Posted by Leppie View Post
    many thanks, the clients now have internet access
    the only thing is that now i can no longer ping between the clients.
    You now do NAT?

    Which clients can't ping eachother? On the same LAN, you should be able to ping. Between the different LANs not, because the .33. LAN is not known on the main LAN *and* because you do NAT. ;-(

    If you follow my signature, and do 'sudo apt-get install miredo' on the different machines, I expect you can ping6 between the LANs. Can you do that? I'm curious about the result.

  10. #20
    Join Date
    Jun 2009
    Location
    Open Linux Forums
    Beans
    2,710

    Re: DHCP clients no internet access

    Quote Originally Posted by sanderj View Post
    You now do NAT?
    yup, up and running

    Quote Originally Posted by sanderj View Post
    Which clients can't ping eachother?
    the clients on the lan (connected to the .33.0 network)

    Quote Originally Posted by sanderj View Post
    On the same LAN, you should be able to ping. Between the different LANs not, because the .33. LAN is not known on the main LAN *and* because you do NAT. ;-(
    yes, i know. that's what i find so weird...

    Quote Originally Posted by sanderj View Post
    If you follow my signature, and do 'sudo apt-get install miredo' on the different machines, I expect you can ping6 between the LANs. Can you do that? I'm curious about the result.
    since you helped me, i'm going to give it a try and post back
    I'm not antisocial. I'm just not user friendly...
    Open Linux Forums

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •