On 2018-12-12 10:30:44 -0500, Dan Ritter wrote:
> Yeah, I think you had a link problem, not a DHCP problem.
I've tried today, and the issue is not always reproducible.
But since there are several access points with the same ESSID,
a reason might be that wicd doesn't always try to connect to
the sa
Vincent Lefevre wrote:
> On 2018-12-11 15:45:19 -0500, Dan Ritter wrote:
> > Check the link status:
> >
> > iw dev wlp61s0 link
> >
> > Look for the hotspot:
> >
> > iw dev wlp61s0 scan
> >
> > Connect to one:
> >
> > iw dev wlp61s0 connect "$ESSID"
> >
> > Run dhclient by hand:
> >
> > dhc
On 2018-12-11 15:45:19 -0500, Dan Ritter wrote:
> Check the link status:
>
> iw dev wlp61s0 link
>
> Look for the hotspot:
>
> iw dev wlp61s0 scan
>
> Connect to one:
>
> iw dev wlp61s0 connect "$ESSID"
>
> Run dhclient by hand:
>
> dhclient wlp61s0
>
> Tell us where it falls down along tha
Vincent Lefevre wrote:
> I get the following error when I try to connect to wifi hotspots with
> no encryption. This is from the wicd log:
>
> [...]
> 2018/12/11 18:44:15 :: Putting interface up...
> 2018/12/11 18:44:15 :: ifconfig wlp61s0 up
> 2018/12/11 18:44:17 :: enctype is None
> 2018/12/11
5.255.255 port 67
interval 10
2018/12/11 18:45:11 :: DHCPDISCOVER on wlp61s0 to 255.255.255.255 port 67
interval 7
2018/12/11 18:45:18 :: No DHCPOFFERS received.
2018/12/11 18:45:18 :: No working leases in persistent database - sleeping.
2018/12/11 18:45:28 :: DHCP connection failed
[...]
jo
On 8/7/2013 4:53 PM, Sean Alexandre wrote:
On Wed, Aug 07, 2013 at 09:29:57PM +0200, Slavko wrote:
is your network like this, please:
-
|ISP|
-
|
|
Sean Alexandre wrote:
> OK, thanks, that's where I was headed, but was hoping it was
> something more obvious. I can get a tcpdump, but don't know DHCP
> very well. I'll take a look, though, and see what I can figure out.
The 'dhcpdump' package is useful for debugging dhcp issues. Easier
than wir
5.255
> port 67 interval 8
> Aug 7 06:29:26 moose dhclient: No DHCPOFFERS received.
> Aug 7 06:29:26 moose dhclient: No working leases in persistent database -
> sleeping.
Because you don't get any response from DHCP server, there are some more
questions...
Are you sure, th
On Wed, Aug 07, 2013 at 09:29:57PM +0200, Slavko wrote:
> is your network like this, please:
>
>-
>|ISP|
>-
> |
> |
>-
>
rval 3
Aug 7 06:28:28 moose dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port
67 interval 6
Aug 7 06:28:28 moose kernel: [ 211.369046] e1000e: eth-wan NIC Link is Up
1000 Mbps Full Duplex, Flow Control: None
Aug 7 06:28:28 moose kernel: [ 211.370437] ADDRCONF(NETDEV_CHANGE): eth-wan:
Dňa 07.08.2013 21:19 Sean Alexandre wrote / napísal(a):
> On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
>> On 07/08/13 18:24, Andy Hawkins wrote:
>>> In article <20130807164822.GA7727@tuzo>,
>>> Sean Alexandre wrote:
No, unfortunately. I know it's not a MAC address issue. Both my TP-
On 07/08/13 20:19, Sean Alexandre wrote:
On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
On 07/08/13 18:24, Andy Hawkins wrote:
In article <20130807164822.GA7727@tuzo>,
Sean Alexandre wrote:
No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
router and the Debi
On Wed, Aug 07, 2013 at 07:16:45PM +0100, Klaus wrote:
> On 07/08/13 18:24, Andy Hawkins wrote:
> >In article <20130807164822.GA7727@tuzo>,
> > Sean Alexandre wrote:
> >>No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
> >>router and the Debian Wheezy machine that works
On Wed, Aug 07, 2013 at 05:24:57PM +, Andy Hawkins wrote:
> In article <20130807164822.GA7727@tuzo>,
> Sean Alexandre wrote:
> > No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
> > router and the Debian Wheezy machine that works get DHCP leases without any
> > probl
On 07/08/13 18:24, Andy Hawkins wrote:
Hi,
In article <20130807164822.GA7727@tuzo>,
Sean Alexandre wrote:
No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
router and the Debian Wheezy machine that works get DHCP leases without any
problems, and have diffe
Hi,
In article <20130807164822.GA7727@tuzo>,
Sean Alexandre wrote:
> No, unfortunately. I know it's not a MAC address issue. Both my TP-LINK home
> router and the Debian Wheezy machine that works get DHCP leases without any
> problems, and have different MAC addresses.
>
> I also asked
On Wed, Aug 07, 2013 at 02:57:58PM +, Andy Hawkins wrote:
> Sean Alexandre wrote:
> > I've got two Debian Wheezy machines. One can connect to my cable modem fine,
> > and gets an IP address. The other can't. They're both configured the same.
> > Any
> > ideas why this might be?
>
> Apologies
Hi,
In article <20130807133856.GA6733@tuzo>,
Sean Alexandre wrote:
> I've got two Debian Wheezy machines. One can connect to my cable modem fine,
> and gets an IP address. The other can't. They're both configured the same. Any
> ideas why this might be?
Apologies for suggesting somethi
I've got two Debian Wheezy machines. One can connect to my cable modem fine,
and gets an IP address. The other can't. They're both configured the same. Any
ideas why this might be?
The log message I get on the machine that doesn't work is:
Aug 7 06:29:26 moose dhclient: No
-- Cuno Sonnemans <[EMAIL PROTECTED]> wrote
(on Tuesday, 15 October 2002, 09:33 AM +0200):
> Alan Chandler heeft geschreven:
> >On Monday 14 October 2002 11:28 pm, Cuno Sonnemans wrote:
> >>Alan Chandler heeft geschreven:
> >>>It may be that you have to register the ethernet card address with the
Alan Chandler heeft geschreven:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On Monday 14 October 2002 11:28 pm, Cuno Sonnemans wrote:
>
>
>>Alan Chandler heeft geschreven:
>>
>>
>
>
>
>> >It may be that you have to register the ethernet card address with the
>> > ISP
>>
>>I don't h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 14 October 2002 11:28 pm, Cuno Sonnemans wrote:
> Alan Chandler heeft geschreven:
> >It may be that you have to register the ethernet card address with the
> > ISP
>
> I don't have a static ip adress but the cable company uses dynamic IP
Alan Chandler heeft geschreven:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>On Monday 14 October 2002 2:52 pm, Mark Janssen wrote:
>
>
>>On Mon, 2002-10-14 at 15:45, Cuno Sonnemans wrote:
>>
>>
>>>Mark Janssen heeft geschreven:
>>>
>>>
Change /etc/network/interfaces, and c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 14 October 2002 2:52 pm, Mark Janssen wrote:
> On Mon, 2002-10-14 at 15:45, Cuno Sonnemans wrote:
> > Mark Janssen heeft geschreven:
> > >Change /etc/network/interfaces, and change the config there (see man
> > >interfaces)
> > >
> > >It sho
On Mon, 2002-10-14 at 15:45, Cuno Sonnemans wrote:
> Mark Janssen heeft geschreven:
> >Change /etc/network/interfaces, and change the config there (see man
> >interfaces)
> >
> >It should look something like this:
> >
> >interface eth0 inet static
> > address x.x.x.x
> > network x.x.x.x
>
Mark Janssen heeft geschreven:
>On Mon, 2002-10-14 at 14:57, Cuno Sonnemans wrote:
>
>
>>But I can't get any connection to the net. I looked in the syslog and
>>there I found this:
>>No DHCPOFFERS received, what does it mean and is this the reason why I
On Mon, 2002-10-14 at 14:57, Cuno Sonnemans wrote:
> But I can't get any connection to the net. I looked in the syslog and
> there I found this:
> No DHCPOFFERS received, what does it mean and is this the reason why I
> can't connect to the internet.
It means your system
I'am trying to setup my internet connection with cabel.
The Nic is setup right IO and irq and is detected on startup and on
startup the network interface is setup.
But I can't get any connection to the net. I looked in the syslog and
there I found this:
No DHCPOFFERS received, what do
28 matches
Mail list logo
