public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marko Kocić" <marko.kocic@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Net / dhcp (miss)behaviour
Date: Sun, 20 Jan 2008 15:07:41 +0100	[thread overview]
Message-ID: <9238e8de0801200607t68e3a4e8nc695b5cd255678e4@mail.gmail.com> (raw)
In-Reply-To: <200801201351.05575.tony.davison2@ntlworld.com>

It seems like that is the problem. Ipconfig /release or disabling net
conn in win before reboot doesnt help. Rebooting modem smtimes helps
but mostly not. Is it posible to somehow configure dhcp client to use
lease from windows?

On 1/20/08, Tony Davison <tony.davison2@ntlworld.com> wrote:
> On Saturday 19 January 2008 22:09:50 Marko Kocić wrote:
> > > I wonder if my similar problem is related to what you report here:  I am
> > > using dhcpcd and ifplug with my ADSL router, which acts as the dhcp
> > > server on my LAN.  For some reason ifplug does not always manage to get
> > > an IP address from the router and I end up with an APIPA address.
> > > /etc/init.d/net.eth0 stop/start gets it going again.  This problem only
> > > occurs if I disconnect and then reconnect the ethernet cable.  No such
> > > problem exists when I boot the machine with the cable already connected
> > > to the NIC.  I haven't changed timeouts or anything else from the dhcpcd
> > > defaults.  I have always attributed this problem to a somewhat slow dhcp
> > > server on the router.
> >
> > It is similar, with a difference that /etc/init.d/net.eth0 restart
> > doesn't help. I tried
> > enlarging timeout but with no help.
> >
> > > As a note:  WinXP machines do not have any such problem.  Even though
> > > they may end up with a APIPA address, they will in minute or so drop it
> > > and acquire a 10.10.10.XXX domain address from the router.  dhcpcpd does
> > > not seem to have this flexibility.
> >
> > I noticed that in most cases after I boot to windows, when I reboot
> > back to linux I can't connect.
> > When I reboot back to windows, net is up.
> >
> > When it fails I noticed that it send DHCP requests, but doesn't get a
> > response.
> >
> > I tried dhclient, dhcpd and pump, and the results are allways the
> > same. It happens in the evenings, when internet traffic is high.
>
> Windows is not releasing the lease correctly, so the CM ignores request from
> the same MAC address for a new leasr, workround is to reboot the cm whem you
> reboot to gentoo.
>
> This works in the UK YMMV elsewhere.
>
> --
> Tony Davison
> --
> gentoo-user@lists.gentoo.org mailing list
>
>

  reply	other threads:[~2008-01-20 14:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 17:09 [gentoo-user] Net / dhcp (miss)behaviour Marko Kocić
2008-01-18 17:50 ` Alan McKinnon
2008-01-18 18:03   ` Marko Kocić
2008-01-18 18:24     ` Etaoin Shrdlu
2008-01-18 18:17       ` Marko Kocić
2008-01-18 18:27         ` Kevin
2008-01-18 18:48         ` Etaoin Shrdlu
2008-01-18 18:38           ` Marko Kocić
2008-01-18 23:31             ` Mick
2008-01-19 22:09               ` Marko Kocić
2008-01-20  1:37                 ` Roy Wright
2008-01-20 13:51                 ` Tony Davison
2008-01-20 14:07                   ` Marko Kocić [this message]
2008-01-20 15:26                     ` [gentoo-user] " Alan McKinnon
2008-01-22 23:44                       ` Marko Kocić

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9238e8de0801200607t68e3a4e8nc695b5cd255678e4@mail.gmail.com \
    --to=marko.kocic@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox