Re: CPU frequency and custom kernel
On Fri, Nov 22, 2013 at 03:03:33AM -0500, ken wrote: > I've found cpuspeed to be buggy... the speed at which the cpu runs > seems to have little to do with the conditions specified in the > config file. Recent kernel upgrades have improved cpuspeed somewhat > (without any changes to the config file), but it's still nonsensical > at times. I think that was it. I upgraded to most recent stable kernel (3.12.1) [1] and no longer see the problem. I took a look at the 3.2 changelog [2] to see if I could tell what particular change Debian developers made to get this working. There are quite a few cpufreq related changes, but it wasn't clear to me which fixes the problem I was seeing. [1] https://www.kernel.org/ [2] http://ftp-master.metadata.debian.org/changelogs//main/l/linux/linux_3.2.51-1_changelog -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131122115430.GA7395@tuzo
Re: CPU frequency and custom kernel
On Fri, Nov 22, 2013 at 11:06:14AM +0100, Jochen Spieker wrote: > Check the files in this directory: > > /sys/devices/system/cpu/cpu0/cpufreq > > Especially scaling_available_frequencies, scaling_max_freq and > scaling_min_freq. I've been using the cpufreq-info, which I think reports what's in those files. For the Debian kernel I get: cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 800 MHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz, 1.20 GHz, 1000 MHz, 800 MHz available cpufreq governors: conservative, powersave, userspace, ondemand, performance current policy: frequency should be within 800 MHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 800 MHz (asserted by call to hardware). cpufreq stats: 2.30 GHz:5.20%, 2.00 GHz:0.14%, 1.80 GHz:0.16%, 1.60 GHz:0.20%, 1.40 GHz:0.28%, 1.20 GHz:0.44%, 1000 MHz:0.49%, 800 MHz:93.09% (39552) And then for the custom kernel I get: cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 800 MHz - 2.30 GHz available frequency steps: 2.30 GHz, 2.00 GHz, 1.80 GHz, 1.60 GHz, 1.40 GHz, 1.20 GHz, 1000 MHz, 800 MHz available cpufreq governors: conservative, powersave, userspace, ondemand, performance current policy: frequency should be within 800 MHz and 2.30 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.80 GHz (asserted by call to hardware). cpufreq stats: 2.30 GHz:11.32%, 2.00 GHz:1.27%, 1.80 GHz:0.94%, 1.60 GHz:0.59%, 1.40 GHz:1.17%, 1.20 GHz:0.60%, 1000 MHz:1.12%, 800 MHz:82.99% (713) That last line for the custom kernel says the CPU runs at 800 MHz most of the time, but I think that's because the stats don't roll over on reboot. It shows I'm using the Debian kernel most of the time. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131122111329.GA5843@tuzo
CPU frequency and custom kernel
I've built my own kernel, but the CPU runs faster (hotter, more fan noise, etc.) I can't figure out why it's faster. Everything I've checked is the same between the two kernels. If I boot to the Debian provided kernel the CPU runs at 800 MHz, but if I boot to my custom kernel it runs at 1.8 GHz. (These are baseline speeds, after boot without running anything else.) Here's what I've checked so far: * Kernel versions are the same. The Debian version is 3.2.0-4-amd64 and the version I got from kernel.org is 3.2.52. * The boot command line has the same paremeters for both: linux /vmlinuz-3.2.0-4-amd64 root=/dev/mapper/tuzo-root ro quiet * Both boot to the same root file system, and use the same configuration files. * The .config file used to build the custom kernel is the same as the one used to build the Debian kernel. (I'm going to pare it down to just what I need once I figure out this problem.) * Both use the ondemand cpufreq governor. Is there anything else I should check? My next step would be to try and build the kernel source from the Debian package instead of from kernel.org. Maybe this is a code difference? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131122004241.GA13986@tuzo
Re: ssh tunnel delay
On Tue, Sep 10, 2013 at 02:28:37PM +0200, Juan Sierra Pons wrote: > 2013/9/10 Sean Alexandre > > > > On Tue, Sep 10, 2013 at 01:11:17PM +0200, Juan Sierra Pons wrote: > > > Hi, > > > > > > I don't see anything strange in the logs provided. Do you see anything > > > strange in your dmesg, /var/log/daemon.log, etc? > > > > > > Is the DNS on the server's side working properly? Sometimes when the > > > reverse DNS is not properly configure some TCP based services get some > > > delay on first connection: ssh, mysql, etc > > > > > > Can a network issue be discarded. Please check with mtr: mtr remote > > > server > > > > > > Not a solution but a very tiny improvement , launch the tunnel with the -C > > > (compression) parameter. > > > > Thanks for looking at this. The other things you list look fine. I did > > notice > > something else with the log, though. Below I type the line "hello". Then > > there's the 80 second delay. And then there's the log messages after the > > "hello": > > > > debug1: Entering interactive session. > > client> nc localhost 1110 > > hello > > debug1: Connection to port 1110 forwarding to localhost port 1212 requested. > > debug2: fd 6 setting TCP_NODELAY > > debug2: fd 6 setting O_NONBLOCK > > debug3: fd 6 is O_NONBLOCK > > debug1: channel 2: new [direct-tcpip] > > debug2: channel 2: open confirm rwindow 2097152 rmax 32768 > > > > I think the delay no longer happens, with subsequent lines, because > > TCP_NODELAY and O_NONBLOCK get set. I wonder if there's a way to configure > > things to set those from the start? > > > Hi, > > I have found a kind of workaround: > http://www.gossamer-threads.com/lists/openssh/bugs/56042 > If the ssh client is invoked with: > ssh -N host -R port # TCP_NODELAY is not set > ssh -n host -R port sleep 1d # TCP_NODELAY is set - this is a workaround > > Can you try to launch the tunnel without the -N parameter (maybe you > can send later the tunnel to background) I get the same thing, unfortunately, with this: ssh -o IPQoS="lowdelay lowdelay" -o ExitOnForwardFailure=yes -f -L1110:localhost:1212 skoki3 sleep 1d I've also added this line to /etc/ssh/sshd_config on the server, and restarted ssh there: IPQoS lowdelay lowdelay This bug report makes it sound like the bug's been fixed on Debian 7.0, but maybe not: Debian Bug report logs - #643312 openssh-client: IPQoS option ignored for AF_INET since 5.9p1-1 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643312 I've got version 1:6.0p1-4 of openssh-client. The bug report says the problems fixed there, but maybe not. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130910130754.GA14913@tuzo
Re: ssh tunnel delay
On Tue, Sep 10, 2013 at 01:11:17PM +0200, Juan Sierra Pons wrote: > Hi, > > I don't see anything strange in the logs provided. Do you see anything > strange in your dmesg, /var/log/daemon.log, etc? > > Is the DNS on the server's side working properly? Sometimes when the > reverse DNS is not properly configure some TCP based services get some > delay on first connection: ssh, mysql, etc > > Can a network issue be discarded. Please check with mtr: mtr remote server > > Not a solution but a very tiny improvement , launch the tunnel with the -C > (compression) parameter. Thanks for looking at this. The other things you list look fine. I did notice something else with the log, though. Below I type the line "hello". Then there's the 80 second delay. And then there's the log messages after the "hello": debug1: Entering interactive session. client> nc localhost 1110 hello debug1: Connection to port 1110 forwarding to localhost port 1212 requested. debug2: fd 6 setting TCP_NODELAY debug2: fd 6 setting O_NONBLOCK debug3: fd 6 is O_NONBLOCK debug1: channel 2: new [direct-tcpip] debug2: channel 2: open confirm rwindow 2097152 rmax 32768 I think the delay no longer happens, with subsequent lines, because TCP_NODELAY and O_NONBLOCK get set. I wonder if there's a way to configure things to set those from the start? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130910120513.GA14348@tuzo
Re: ssh tunnel delay
On Tue, Sep 10, 2013 at 12:25:59PM +0200, Juan Sierra Pons wrote: > Can you launch the tunnel in verbose (-vvv) mode and send the logs? > ssh -vvv -o ExitOnForwardFailure=yes -fN -L1110:localhost:1212 server Here's what I'm seeing with -vvv: http://paste.debian.net/37873/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130910104403.GA13329@tuzo
ssh tunnel delay
I'm seeing a delay when I attempt a connection through an ssh tunnel. The connection's fast without the tunnel, but has an inital 80 second delay with it. Here's the case that works, without the tunnel. I see lines I type echoed immediately: server> nc -l -p 1212 client> nc server 1212 But if instead I do this, the first line isn't seen for about 80 seconds. After that, everything's fine and lines appear immediately: server> nc -l -p 1212 client> ssh -o ExitOnForwardFailure=yes -fN -L1110:localhost:1212 server client> nc localhost 1110 I can ssh to the server fine, with no delay. Any ideas why the tunnel has the delay? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130910101005.GA13051@tuzo
Re: dhcpdump not seeing dhclient messages
On Mon, Aug 26, 2013 at 01:28:44PM -0300, Luther Blissett wrote: > I do not know if this is the case, but ISP's usually record its > customers MAC address which is universally unique. Maybe, just maybe, > when you switched from your tp-link router to direct wan link, the ISP > machine noticed that there was an unknown MAC attempting to connect and > refused connection. Then your dhcp discover packets would reach ISP > hardware, but would not receive any responses. I've checked with my ISP and they say to just power down the cable modem for 30 seconds before attaching a machine with a new MAC. And, I've been able to switch between two other machines, both with different MAC addresses. It's just this third machine that's given me problems. What I'm really stuck on right now is why does the dhclient log show that it's sending DHCPDISCOVER messages, but dhcpdump isn't seeing them? It's like something is sitting between dhclient and my NIC. I've disabled all firewall rules, though, so know it's not that. (All tables and chains have a default policy of ACCEPT, and no rules.) > BTW, you should notice that dchp communications are not held with the > same machines when you have a direct link as opposed to routed link. > When routed through some gateway, you have two sets of dhcp ISP <--> > router <--> pc. Thanks. All my connections right now are direct, like this: [ISP]---[cable modem]---[my machine] The cable modem is just a modem, and not a router. But I know what you mean. My final configuration will be: [ISP]---[cable modem]---[my machine, a router]---[LAN machines] -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130826170716.GA7349@tuzo
Re: dhcpdump not seeing dhclient messages
On Mon, Aug 26, 2013 at 02:54:27PM +0530, Arun Khan wrote: > On Mon, Aug 26, 2013 at 2:01 PM, Sean Alexandre wrote: > > I have a machine that's not acquiring a DHCP lease from my ISP. I can see > > that > > dhclient is sending DHCPDISCOVER messages. My system log has: > > > > Aug 25 17:36:41 athabasca dhclient: DHCPDISCOVER on eth-wan to > > 255.255.255.255 port 67 interval 7 > > -8<-8<-8<-8<-8<-8<-8<- > > > The odd thing is if I do the exact same thing with this machine connected to > > a local TP-LINK router instead of my ISP cable modem, dhcpdump sees the > > DHCPDISCOVER, and the machine acquires a DHCP lease. > > Is your cable modem setup in bridge mode? (bridge between it's > ethernet (RJ45) and the 'wan' ports with cable coming in from ISP. Yes, bridge mode. (It's just a cable modem, and not a router. Bridge mode is the only way it works.) > > > Any ideas why would dhclient be sending a DHCPDISCOVER, but dhcpdump not > > see it? > > Try tcpdump with dest port 67 OK, thanks. I just tried that now, and it got a DHCP lease this time, for some reason. So it's working again. I'll do a tcpdump next time, if I see the problem again, and hopefully that will tell me what's going on. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130826104607.GA5205@tuzo
dhcpdump not seeing dhclient messages
I have a machine that's not acquiring a DHCP lease from my ISP. I can see that dhclient is sending DHCPDISCOVER messages. My system log has: Aug 25 17:36:41 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 7 Aug 25 17:36:48 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 13 Aug 25 17:37:01 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 12 Aug 25 17:37:13 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 12 Aug 25 17:37:25 athabasca dhclient: DHCPDISCOVER on eth-wan to 255.255.255.255 port 67 interval 5 Aug 25 17:37:30 athabasca dhclient: No DHCPOFFERS received. Aug 25 17:37:30 athabasca dhclient: No working leases in persistent database - sleeping. But for some reason the DHCPDISCOVER messages aren't making it out over the NIC. I'm running dhcpdump and see no traffic. This is with no firewall rules. All tables and chains are set to ACCEPT. The odd thing is if I do the exact same thing with this machine connected to a local TP-LINK router instead of my ISP cable modem, dhcpdump sees the DHCPDISCOVER, and the machine acquires a DHCP lease. Any ideas why would dhclient be sending a DHCPDISCOVER, but dhcpdump not see it? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130826083131.GA6922@tuzo
Re: owncloud no longer in wheezy
On Fri, Aug 09, 2013 at 06:07:04AM -0400, Sean Alexandre wrote: > I see owncloud is no longer in wheezy, and I'm trying to understand why. Where > can I find information on why a package was pulled from a release? > > I see this, but it only seems to say when it was pulled: > http://packages.qa.debian.org/o/owncloud.html > > It was pulled from testing to unstable on 2013-05-14. I'd like to understand > why, > (and how this works in general.) > > Is there somewhere else I can check? > > I'm trying to understand the Debian development process as much as anything. > > (I had installed owncloud on a wheezy box when wheezy was testing. I want to > install it again, but this time on wheezy stable.) I think I just found the answer to my question, here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=owncloud#_4_2_5 owncloud 4.0 (the version that was in wheezy testing) had a serious bug. It's been fixed, but in the next release: owncloud 5.0. But, wheezy had already been frozen by that time and so owncloud got pulled. So next time I'll check the "Bugs in source package" link to understand why a package got pulled from a release: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=owncloud -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130809103357.GA28387@tuzo
owncloud no longer in wheezy
I see owncloud is no longer in wheezy, and I'm trying to understand why. Where can I find information on why a package was pulled from a release? I see this, but it only seems to say when it was pulled: http://packages.qa.debian.org/o/owncloud.html It was pulled from testing to unstable on 2013-05-14. I'd like to understand why, (and how this works in general.) Is there somewhere else I can check? I'm trying to understand the Debian development process as much as anything. (I had installed owncloud on a wheezy box when wheezy was testing. I want to install it again, but this time on wheezy stable.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130809100704.GA28285@tuzo
Re: dhclient "No DHCPOFFERS received"
On Wed, Aug 07, 2013 at 09:29:57PM +0200, Slavko wrote: > is your network like this, please: > >- >|ISP| >- > | > | >- >| modem | >- > | >-- >| | | > - - - > | Debian I | | Debian II | | TP-Link | > - - - > > > or like this? > >- >|ISP| >- > | > | >- >| modem | >- > | > | >- >| TP-Link | >- > | > -- > || > - - > | Debian I | | Debian II | > - - My network is like your first diagram, but with only one machine connected to the modem at a time. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130807205320.GB9875@tuzo
Re: dhclient "No DHCPOFFERS received"
On Wed, Aug 07, 2013 at 08:29:53PM +0100, Klaus wrote: > 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 Debian Wheezy machine that works get DHCP leases without > >>>>any > >>>>problems, and have different MAC addresses. > >>>> > >>>>I also asked my ISP about this, when I had them on the line to bring up my > >>>>new cable modem. They said any MAC address is fine. Just power the cable > >>>>modem down for 30 seconds first. > >>> > >>>Ok, I did say I was kind of stating the obvious! > >>> > >>>Next thing I'd be doing is using tshark or similar to sniff the traffic > >>>being seen on the Debian box. > >>> > >>>Andy > >>> > >>> > >>Just more of the obvious stuff: > >>You say it's a new cable modem, there is a home router, and there is > >>at least one other Debian Wheezy box. > >>Does your ISP provide you with one, or more than one IP address? If > >>one, the router probably translates this "public" IP address to your > >>"private" LAN. Does the router function as a DHCP server, or do you > >>have a dedicated box on your LAN? Can you check the logs of your LAN > >>DHCP server for entries matching the non-functioning box? > > > >There's no NAT in what I'm doing, no. The boxes in each case get a public > >IP address from my ISP (or try to.) The different cases are: > > > >CASE 1, works: > >[cable modem]---[TP-LINK router] > > > >CASE 2, works: > >[cable modem]---[wheezy box that works] > > > >CASE 3, doesn't work: > >[cable modem]---[wheezy box that doesn't work] > > > >I attach a laptop to the TP-LINK router to see that it got an IP address, so > >there's NAT there. But, NAT doens't come into play for the larger problem, if > >that's what you're asking. > > > > > Have you checked for DHCP client entries in /var/log/daemon.log ? > I'm running the standard dhclient, from the isc-dhcp-client package > (though my box is running SID), and there are log messages like > > /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient: > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 > /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient: DHCPREQUEST > on eth0 to 255.255.255.255 port 67 > /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient: DHCPOFFER > from 192.168.0.1 > /var/log/daemon.log:Aug 5 08:48:29 myhostname dhclient: DHCPACK > from 192.168.0.1 > On the wheezy box that works I get: Aug 6 17:46:13 tuzo dhclient: Internet Systems Consortium DHCP Client 4.2.2 Aug 6 17:46:13 tuzo dhclient: Copyright 2004-2011 Internet Systems Consortium. Aug 6 17:46:13 tuzo dhclient: All rights reserved. Aug 6 17:46:13 tuzo dhclient: For info, please visit https://www.isc.org/software/dhcp/ Aug 6 17:46:13 tuzo dhclient: Aug 6 17:46:13 tuzo dhclient: Listening on LPF/eth0/10:0b:a9:8b:33:f8 Aug 6 17:46:13 tuzo dhclient: Sending on LPF/eth0/10:0b:a9:8b:33:f8 Aug 6 17:46:13 tuzo dhclient: Sending on Socket/fallback Aug 6 17:46:13 tuzo dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Aug 6 17:46:20 tuzo dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Aug 6 17:46:20 tuzo dhclient: DHCPNAK from 10.132.192.1 Aug 6 17:46:20 tuzo dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 Aug 6 17:46:20 tuzo dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Aug 6 17:46:20 tuzo dhclient: DHCPOFFER from 10.132.192.1 Aug 6 17:46:20 tuzo dhclient: DHCPACK from 10.132.192.1 Aug 6 17:46:21 tuzo dhclient: bound to 66.26.64.22 -- renewal in 1705 seconds. On the wheezy box that doesn't work I get: Aug 7 06:28:25 moose dhclient: Internet Systems Consortium DHCP Client 4.2.2 Aug 7 06:28:25 moose dhclient: Copyright 2004-2011 Internet Systems Consortium. Aug 7 06:28:25 moose dhclient: All rights reserved. Aug 7 06:28:25 moose dhclient: For info, please visit https://www.isc.org/software/dhcp/ Aug 7 06:28:25 moose dhclient: Aug 7 06:28:25 moose kernel: [ 208.409987] ADDRCONF(NETDEV_UP): eth-wan: link is not ready Aug 7 06:28:25 moose dhclient: Listening on LPF/eth-wan/00:25:90:39:de:08 Aug 7 06:28:25 moose dhclient: Sending on LPF/eth-wan/00:25:90:39:de:08 Aug 7 06:28:25 moose dhclient: Sending on Sock
Re: dhclient "No DHCPOFFERS received"
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 get DHCP leases without any > >>problems, and have different MAC addresses. > >> > >>I also asked my ISP about this, when I had them on the line to bring up my > >>new cable modem. They said any MAC address is fine. Just power the cable > >>modem down for 30 seconds first. > > > >Ok, I did say I was kind of stating the obvious! > > > >Next thing I'd be doing is using tshark or similar to sniff the traffic > >being seen on the Debian box. > > > >Andy > > > > > Just more of the obvious stuff: > You say it's a new cable modem, there is a home router, and there is > at least one other Debian Wheezy box. > Does your ISP provide you with one, or more than one IP address? If > one, the router probably translates this "public" IP address to your > "private" LAN. Does the router function as a DHCP server, or do you > have a dedicated box on your LAN? Can you check the logs of your LAN > DHCP server for entries matching the non-functioning box? There's no NAT in what I'm doing, no. The boxes in each case get a public IP address from my ISP (or try to.) The different cases are: CASE 1, works: [cable modem]---[TP-LINK router] CASE 2, works: [cable modem]---[wheezy box that works] CASE 3, doesn't work: [cable modem]---[wheezy box that doesn't work] I attach a laptop to the TP-LINK router to see that it got an IP address, so there's NAT there. But, NAT doens't come into play for the larger problem, if that's what you're asking. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130807191905.GB8969@tuzo
Re: dhclient "No DHCPOFFERS received"
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 > > problems, and have different MAC addresses. > > > > I also asked my ISP about this, when I had them on the line to bring up my > > new cable modem. They said any MAC address is fine. Just power the cable > > modem down for 30 seconds first. > > Ok, I did say I was kind of stating the obvious! > > Next thing I'd be doing is using tshark or similar to sniff the traffic > being seen on the Debian box. 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. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130807191154.GA8969@tuzo
Re: dhclient "No DHCPOFFERS received"
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 for suggesting something obvious you might already have thought > of, but I seem to recall my Cable provider's modem will only provide DHCP > addresses to a single MAC unless it's been correctly release (or perhaps the > Cable Modem re-powered). > > Could it be as simple as that? 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 my ISP about this, when I had them on the line to bring up my new cable modem. They said any MAC address is fine. Just power the cable modem down for 30 seconds first. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130807164822.GA7727@tuzo
dhclient "No DHCPOFFERS received"
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 DHCPOFFERS received. The configuration on both machines looks the same. I've checked: * /etc/dhcp/dhclient.conf * /etc/sysctl.conf * iptables What's mysterious about this is that both machines can connect fine to my TP-LINK home router, and get DHCP leases and IP addresses. It's only when I try to connect the problem machine to my cable modem that it gets the "No DHCPOFFERS received." 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. Any ideas? Thanks! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130807133856.GA6733@tuzo
Re: SSHD Keys
On Sat, Aug 03, 2013 at 10:16:08PM -0400, Jerry Stuckle wrote: > I was just renewing my SSHD keys (dpkg-reconfigure openssh-server) > and noticed it is generating 512 bit RSA keys. This isn't all that > secure. > > How can I get it to generate better keys? As root: rm /etc/ssh/ssh_host* ssh-keygen -N '' -b 4096 -t rsa -f /etc/ssh/ssh_host_rsa_key -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130804081950.GA23754@tuzo
Re: server log centalized
On Mon, Jul 15, 2013 at 03:18:52PM +0200, Pol Hallen wrote: > I need setting up a server log centralized over internet (using rsyslog). > What is better? Using a vpn or crypt log files? stunnel is good for this. It creates encrypted SSL tunnels between machines, for network daemons. Here are some links: stunnel package in wheezy http://packages.debian.org/wheezy/stunnel4 Article about using stunnel with rsyslog http://freecode.com/articles/ssl-encrypting-syslog-with-stunnel Wikipedia article on stunnel https://en.wikipedia.org/wiki/Stunnel Official site https://www.stunnel.org/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130715144828.GA19958@tuzo
Deterministic Builds (was [Re: wacky question])
On Wed, Jun 19, 2013 at 10:44:12PM -0400, Greg wrote: > Does anyone think that debian could participate in any programs like > PRISM? Or could a lone (or group of) sympathetic DD or DM slip a > backdoor or something that could collect private info in the binary > packages distributed by debian? There was an interesting post on this the other day on the liberationtech mailing list by Mike Perry from the Tor Project: Deterministic builds and software trust https://mailman.stanford.edu/pipermail/liberationtech/2013-June/009257.html To quote: > For the past several years, we've been seeing a steady increase in the > weaponization, stockpiling, and the use of exploits by multiple > governments, and by multiple *areas* of multiple governments. This > includes weaponized exploits specifically designed to "bridge the air > gap", by attacking software/hardware USB stacks, disconnected Bluetooth > interfaces, disconnected Wifi interfaces, etc. Even if these exploits > themselves don't leak (ha!), the fact that they are known to exist means > that other parties can begin looking for them. > In this brave new world, without the benefit of anonymity to protect > oneself from such targeted attacks, I don't believe it is possible to > keep a software-based GPG key secure anymore, nor do I believe it is > possible to keep even an offline build machine secure from malware > injection anymore, especially against the types of adversaries that Tor > has to contend with. > This means that software development has to evolve beyond the simple > models of "Trust my gpg-signed apt archive from my trusted build > machine", or even projects like Debian going to end up distributing > state-sponsored malware in short order. > This is where deterministic builds come in... He goes on to explain what "deterministc builds" are, how Tor has started using them, and how hopefully Linux distros will as well. Also related, Bruce Scheier just wrote an interesting piece on weaponized exploits, on how the NSA is planting logic bombs and backdoors in machines and routers around the world: Has U.S. started an Internet war? www.cnn.com/2013/06/18/opinion/schneier-cyberwar-policy -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130620073240.GA29135@tuzo
Re: Openvpn, network manager and resolv.conf
On Mon, Jun 17, 2013 at 08:31:41PM -0700, Erwan David wrote: > Le 17/06/2013 19:40, Sean Alexandre a écrit : > >Your openvpn config file may be missing these two lines: > > > >up /etc/openvpn/update-resolv-conf > >down /etc/openvpn/update-resolv-conf > > > >You should be seeing a log file entry like this, that shows resolv.conf has > >been updated: > > > >Sun June 16 08:18:10 2013 us=8295 /etc/openvpn/update-resolv-conf tun0 1500 > >1562 10.0.122.114 10.0.122.113 init > > > > > That would mazke the config file on client not only linux but even > debian specific. And good security dictates that such decision > should be forced by server. > I remember it once worked this way... I see your point. I don't know if there's a way to do that -- to configure the OpenVPN server to update resolv.conf for all clients without the clients needing to configure anything. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130618034814.GA11868@tuzo
Re: Openvpn, network manager and resolv.conf
On Mon, Jun 17, 2013 at 05:42:19PM -0700, Erwan David wrote: > Le 17/06/2013 09:25, Sean Alexandre a écrit : > >It sounds like you may not have the resolvconf package installed. > > I have... > > And I see in my resolv.conf > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > nameserver 8.8.8.8 > search key.chillispot.info > > And in /var/log/daemon.log > > Jun 17 17:35:27 bibi ovpn-dedibox[4076]: PUSH: Received control > message: 'PUSH_REPLY,ifconfig-ipv6 2a01:e0b:2070:1::1001/64 > 2a01:e0b:2070:1::1,tun-ipv6,route-ipv6 2000::/3 > 2a01:0e0b:2070:1::1,redirect-gateway def1 bypass-dhcp,dhcp-option > DNS 10.8.0.1,dhcp-option DOMAIN rail.eu.org,tun-ipv6,route > 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.10 > 10.8.0.9' > > which shows that the openvpn server pushed the DNS Your openvpn config file may be missing these two lines: up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf You should be seeing a log file entry like this, that shows resolv.conf has been updated: Sun June 16 08:18:10 2013 us=8295 /etc/openvpn/update-resolv-conf tun0 1500 1562 10.0.122.114 10.0.122.113 init -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130618024004.GA10498@tuzo
Re: Openvpn, network manager and resolv.conf
On Mon, Jun 17, 2013 at 08:58:51AM -0700, Erwan David wrote: > I am in holidays going from hotel to hotel and I see that > resolv.conf stays the same, i.e. the one networkmanager writes from > the hotel DHCP. It sounds like you may not have the resolvconf package installed. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130617162546.GA5716@tuzo
Re: Debian/Linux tutorials.
On Thu, Jun 06, 2013 at 02:11:21PM +0300, atar wrote: > I wanted to know please where can I enrich my knowledge about Linux > at general and especially about Debian Linode's got some great tutorials: https://library.linode.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130606144811.GA24390@tuzo
Re: avahi-daemon: Is it *really* needed?
On Thu, May 23, 2013 at 12:39:16PM -0700, David Guntner wrote: > I'm still running Squeeze for a while longer before I finally upgrade to > Wheezy - want to let it shake out a bit before taking the plunge. :-) > > A question that I've been pondering for a while now: Is the > avahi-daemon *really* needed? I've disabled it, and haven't needed it. Here's more on what it's for: http://packages.debian.org/wheezy/avahi-daemon So it seems you'd only need it if you want auto-discovery for printers and other devices on your network. You should be able to disable it with: update-rc.d avahi-daemon disable This leaves it installed, to satisfy the dependencies you're seeing, but causes it not to start when you reboot. To stop it before rebooting: service avahi-daemon stop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130523204656.GA29320@tuzo
Re: Debugging a Wheezy Hang
On Mon, May 20, 2013 at 03:47:13PM -0400, staticsafe wrote: > Didn't you post this earlier this week? > I will repost my answer and CC you as well: I just joined the list, but apparently not in time to get your earlier response. I'm seeing responses now. Thanks for resending. I'll take a look at those logs, and the other things people are suggesting. Would there any way to trigger a core dump, of the entire system, and would that be in any way useful? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130520212738.GA18144@tuzo
Debugging a Wheezy Hang
I've installed Wheezy on a laptop. Every few days it hangs. (I can't even ctl+alt+f2 to get a console.) I'd like to report this. How do I capture debug info that would be useful in a bug report? (And, where do I file a bug report?) Thanks! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130520194008.GA16983@tuzo
Reporting Wheezy Freeze
I've installed Wheezy on my laptop and it's freezing every so often. (I can't even to get a console.) I'd like to report a bug, but don't know where to start. What can I run to capture info on the bug the next time it happens? Where/how do I report it? Thanks for any pointers! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130519221724.GA6955@tuzo
