On Thu 31 Oct 2024 at 10:06:42 (+0100), to...@tuxteam.de wrote:
> On Thu, Oct 31, 2024 at 10:48:52AM +0200, Anssi Saari wrote:
> > Timothy M Butterworth writes:
> >
> > > As you can see here pinging google from eth0 fails. If masquerading was
> > > working then ping would be successful.
>
> I'm
On Thu, Oct 31, 2024 at 10:48:52AM +0200, Anssi Saari wrote:
> Timothy M Butterworth writes:
>
> > As you can see here pinging google from eth0 fails. If masquerading was
> > working then ping would be successful.
I'm late to the party, but did you take into account that masquerading
ICMP (ping
Timothy M Butterworth writes:
> As you can see here pinging google from eth0 fails. If masquerading was
> working then ping would be successful.
Well, if it helps, I don't have external accress on my router via the
inside interface either. Works from the LAN hosts though.
> Can ip masquerading
On 10/31/24 07:17, Timothy M Butterworth wrote:
3: virbr0: mtu 1500 qdisc noqueue
state DOWN
mode DEFAULT group default qlen 1000
link/ether 52:54:00:78:fb:ce brd ff:ff:ff:ff:ff:ff
4: eth0: mtu 1500 qdisc fq_codel state DOWN
mode DEFAULT group default qlen 1000
link/ether 00:00:00:00:11
On 24/01/2024 04:18, Geert Stappers wrote:
|root@nero:~# nmcli device | grep -e wifi -e gsm
|ttyACM1 gsm unavailable --
|wlp2s0wifi unavailable --
If the devices are hard-blocked then you may need to enable them in
firmware (BIOS) setup. Old lap
On Mon, Jan 22, 2024 at 06:36:57AM +0200, Anssi Saari wrote:
> Geert Stappers writes:
> >
> > Here on a laptop does `ip link` see a WIFI device,
> > but `nmcli device` does not.
>
> And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
> sometimes comes up with a wwx ID like that, some
David Wright writes:
> On Mon 22 Jan 2024 at 06:36:57 (+0200), Anssi Saari wrote:
>> And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
>> sometimes comes up with a wwx ID like that, sometimes wwan0. I even
>> explicitly rename it to wwan0 if that happens to make life easier.
>
> I
On Mon 22 Jan 2024 at 06:36:57 (+0200), Anssi Saari wrote:
> Geert Stappers writes:
> >
> > Here on a laptop does `ip link` see a WIFI device,
> > but `nmcli device` does not.
>
> And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
> sometimes comes up with a wwx ID like that, someti
Geert Stappers writes:
> Hello,
>
>
>
> Here on a laptop does `ip link` see a WIFI device,
> but `nmcli device` does not.
And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
sometimes comes up with a wwx ID like that, sometimes wwan0. I even
explicitly rename it to wwan0 if that hap
On Mon 22 Jan 2024 at 00:05:08 (+0700), Max Nikulin wrote:
> On 21/01/2024 23:33, Geert Stappers wrote:
> > The repair:
> >
> > wget
> > http://deb.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210315-3_all.deb
> >
> > sudo dpkg -i firmware-iwlwifi_20210315-3_all.deb
>
>
On 21/01/2024 23:33, Geert Stappers wrote:
The repair:
wget
http://deb.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210315-3_all.deb
sudo dpkg -i firmware-iwlwifi_20210315-3_all.deb
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#n
On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> [7.854942] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
> [7.860452] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
> [8.356275] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
Run rfkill and, if i
On Sun, Jan 21, 2024 at 03:58:18PM +0100, Geert Stappers wrote:
>
> Hello,
>
>
>
> Here on a laptop does `ip link` see a WIFI device,
> but `nmcli device` does not.
>
> How to make NetworkManager aware of a WIFI device?
>
Have the firmware for WIFI card installed.
What follows are the "bef
Am 21.01.2024 um 16:36:09 Uhr schrieb Geert Stappers:
> Even better :-)
>
> It doesn't exist in /etc/network
Is system-networkd being used?
How did you configure it in the past?
On Sun, Jan 21, 2024 at 04:26:46PM +0100, Marco Moock wrote:
> Am 21.01.2024 um 15:58:18 Uhr schrieb Geert Stappers:
>
> > How to make NetworkManager aware of a WIFI device?
>
> Is the device commented out in /etc/network?
>
Even better :-)
It doesn't exist in /etc/network
|root@nero:/etc/n
Am 21.01.2024 um 15:58:18 Uhr schrieb Geert Stappers:
> How to make NetworkManager aware of a WIFI device?
Is the device commented out in /etc/network?
On 2021-02-07 9:40 p.m., Elias Pereira wrote:
> hello,
>
> I have debian 10 in a xenserver 7.0 vm with static ip and keeps trying
> dhcp. Already removed some packages that could be interfering, but must
> still have something installed.
>
> the post messages
> https://i.stack.imgur.com/9ylgS.p
On Tue, Jul 21, 2020 at 12:39:23PM +0200, basti wrote:
> On 21.07.20 11:34, Reco wrote:
> > Hi.
> >
> > On Tue, Jul 21, 2020 at 11:09:04AM +0200, basti wrote:
> >> Hello, I need some kind of software for ip accounting and record my
> >> traffic rx and tx. I need to know how much Gigabyte I use
>> I need to Monitor my monthly traffic, send and receive from my ISP.
>> In the datacenter we used nfdump. but this is a bit over killed i
>> think. I will try to use vnstat.
>> It's just to make a rough estimate how much traffic is used all over a
>> month.
>>
>
> Can you not just look at your r
On Tue, 21 Jul 2020 12:39:23 +0200
basti wrote:
> On 21.07.20 11:34, Reco wrote:
> > Hi.
> >
> > On Tue, Jul 21, 2020 at 11:09:04AM +0200, basti wrote:
> >> Hello, I need some kind of software for ip accounting and record my
> >> traffic rx and tx. I need to know how much Gigabyte I used o
On 21.07.20 11:34, Reco wrote:
> Hi.
>
> On Tue, Jul 21, 2020 at 11:09:04AM +0200, basti wrote:
>> Hello, I need some kind of software for ip accounting and record my
>> traffic rx and tx. I need to know how much Gigabyte I used over a month.
>
> nfacct, ulogd2, possibly iptables-netflow, "
Hi.
On Tue, Jul 21, 2020 at 11:09:04AM +0200, basti wrote:
> Hello, I need some kind of software for ip accounting and record my
> traffic rx and tx. I need to know how much Gigabyte I used over a month.
nfacct, ulogd2, possibly iptables-netflow, "ip -s a l" if you need it
quick. Good old
basti wrote:
> Hello, I need some kind of software for ip accounting and record my
> traffic rx and tx. I need to know how much Gigabyte I used over a
> month.
vnstat
S!
--
Sigmentation fault. Core dumped.
On Saturday 18 July 2015 17:39:48 David Wright wrote:
> And ip's -o switch makes it even easier
> because each item is all on one line.
For some, possibly idiosyncratic, meanings of the word "easier". ;-)
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
On Sat, 18 Jul 2015, Dan Ritter wrote:
I find that a bizarre attitude.
I'm so sorry. I hope the experience was not too
uncomfortable for you. Please forgive me. I have many
personal shortcomings, and frequent descents into
bizarro-world figures prominently in any comprehensive
list of them
Quoting bri...@aracnet.com (bri...@aracnet.com):
> On Fri, 17 Jul 2015 19:25:45 -0500
> David Wright wrote:
>
> > Quoting John J. Boyer (john.bo...@abilitiessoft.org):
> > > Thanks for all of your answers. The problem was that ifconfig is in sbin
> > > not bin.
> >
> > I think you're better off
Patrick Wiseman writes:
> On Fri, Jul 17, 2015 at 2:25 PM, John J. Boyer
> wrote:
>> I have net-tools. ifconfig works only for root. WHY? On other distros
>> ordinary users can use it.
>
> You haven't been listening to what others have been telling you.
> ifconfig resides in sbin, which is in ro
"John J. Boyer" writes:
> Why isn't ifconfig available on Jessie? There id no package. The
> command produces an error message that it has not been found.
>
> John
>
> On Fri, Jul 17, 2015 at 01:44:35PM -0400, Miles Fidelman wrote:
>> John J. Boyer wrote:
>> >I have Jessie set up for CLI only. T
"John J. Boyer" writes:
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
>
> John
>
> On Fri, Jul 17, 2015 at 05:41:27PM +0200, Elimar Riesebieter wrote:
>> * John J. Boyer [2015-0
bri...@aracnet.com a écrit :
>
> the output of ip is a bit of a mess.
>
> valid_lft forever preferred_lft forever
>
> what the hell ? i have no idea what tha means.
It is specific to IPv6 addresses. When an interface gets IPv6 addresses
assigned by stateless address autoconfiguration (SLAAC)
On 18/07/15 15:25, bri...@aracnet.com wrote:
the output of ip is a bit of a mess.
valid_lft forever preferred_lft forever
what the hell ? i have no idea what tha means. i know i'll do man ip, it's
probably
got an explanation. no. it doesn't.
It's saying that the valid and preferred remai
On Fri, 17 Jul 2015 19:25:45 -0500
David Wright wrote:
> Quoting John J. Boyer (john.bo...@abilitiessoft.org):
> > Thanks for all of your answers. The problem was that ifconfig is in sbin
> > not bin.
>
> I think you're better off forgetting about ifconfig and using ip in
> its place; that's th
On Fri, Jul 17, 2015 at 09:27:04PM -0400, Bob Bernstein wrote:
> On Fri, 17 Jul 2015, Martin G. McCormick wrote:
>
> >Yes but depending on how your path is set it may not simply work.
>
> NO.
>
> There ought to be no monkeying EVA with the default PATHs (for root
> and other users) created by th
Quoting Bob Bernstein (poo...@ruptured-duck.com):
> On Fri, 17 Jul 2015, David Wright wrote:
>
> >I think you're better off forgetting about ifconfig and using ip
> >in its place;
>
> Ach du Lieber Himmel! You will have to pry ifconfig out of my cold
> dead fingers!
>
> >that's the direction thi
On Fri, 17 Jul 2015, Martin G. McCormick wrote:
Yes but depending on how your path is set it may not
simply work.
NO.
There ought to be no monkeying EVA with the default
PATHs (for root and other users) created by the
authors of Linux and Unix. Period. (Which is why the
wheel group ought t
On Fri, 17 Jul 2015, Hans wrote:
If you know a little bit about the range of the
network (i.e. if you know at least , it is
192.168.), then you might try to scan the IP with a
direct connection to the network card.
Try nmap (either from a separate computer with a
crossover cable) on the c
On Fri, 17 Jul 2015, David Wright wrote:
I think you're better off forgetting about ifconfig
and using ip in its place;
Ach du Lieber Himmel! You will have to pry ifconfig
out of my cold dead fingers!
that's the direction things are heading.
Of course David I am no one to gainsay your ty
Quoting John J. Boyer (john.bo...@abilitiessoft.org):
> Thanks for all of your answers. The problem was that ifconfig is in sbin
> not bin.
I think you're better off forgetting about ifconfig and using ip in
its place; that's the direction things are heading. From Packages:
Package: iproute2
...
Miles Fidelman writes:
> ifconfig -a
> is always a good one
Yes but depending on how your path is set it may not simply work.
Martin McCormick
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive
On Friday 17 July 2015 18:49:59 John J. Boyer wrote:
> ip
> seems to be inapropriate.
Why is
$ip addr
inappropriate for finding out the IP address of an interface?
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
On Fri 17 Jul 2015 at 14:47:09 -0400, Cindy-Sue Causey wrote:
> On 7/17/15, Jape Person wrote:
> >
> > I think ifconfig isn't a package.
> >
> > By default on my Jessie systems it's under /sbin.
> >
> > If
> >
> > $ ifconfig -a
> >
> > doesn't work, then
> >
> > $ /sbin/ifconfig -a
> >
> > probab
On 7/17/15, Jape Person wrote:
>
> I think ifconfig isn't a package.
>
> By default on my Jessie systems it's under /sbin.
>
> If
>
> $ ifconfig -a
>
> doesn't work, then
>
> $ /sbin/ifconfig -a
>
> probably will.
Ah-HA! I usually remember to try going that route if something
suggested here does
On Fri 17 Jul 2015 at 13:25:35 -0500, John J. Boyer wrote:
> I have net-tools. ifconfig works only for root. WHY? On other distros
> ordinary users can use it.
That's a change of tack! It started with "I cannot find a file but on
other distros users are more capable" and has now become "ifconfig
On Fri, Jul 17, 2015 at 2:25 PM, John J. Boyer
wrote:
> I have net-tools. ifconfig works only for root. WHY? On other distros
> ordinary users can use it.
You haven't been listening to what others have been telling you.
ifconfig resides in sbin, which is in root's but not the ordinary
user's path
> I have Jessie set up for CLI only. […]
> What command will tell me what ip address it is using?
ip address works fine:
ip address show scope global | sed -r -n 's|^ *inet6? ([^ /]*).*$|\1|p'
--
Gabriel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
I have net-tools. ifconfig works only for root. WHY? On other distros
ordinary users can use it.
John
On Fri, Jul 17, 2015 at 08:01:29PM +0200, Simon Brandmair wrote:
> Hi,
>
> On 07/17/2015 07:50 PM, John J. Boyer wrote:
> > None of these solutions work. ifconfig is not available on Jessie. ip
> Am 17.07.2015 um 19:57 schrieb "John J. Boyer" :
>
> Why isn't ifconfig available on Jessie? There id no package. The
> command produces an error message that it has not been found.
>
> John
>
>> On Fri, Jul 17, 2015 at 01:44:35PM -0400, Miles Fidelman wrote:
>> John J. Boyer wrote:
>>> I ha
On Fri 17 Jul 2015 at 12:57:37 -0500, John J. Boyer wrote:
> Why isn't ifconfig available on Jessie? There id no package. The
> command produces an error message that it has not been found.
brian@desktop:~$ dpkg -S ifconfig
net-tools: /usr/share/man/pt_BR/man8/ifconfig.8.gz
net-tools: /usr/share
On 07/17/2015 01:49 PM, John J. Boyer wrote:
None of these solutions work. ifconfig is not available on Jessie. ip
seems to be inapropriate. dig produces nothing. I have used ifconfig on
other distros.
John
I think ifconfig isn't a package.
By default on my Jessie systems it's under /sbin.
I
Hi,
On 07/17/2015 07:50 PM, John J. Boyer wrote:
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
ifconfig is available if you install net-tools.
And what do you mean with "ip seems
On 17/07/15 18:49, John J. Boyer wrote:
None of these solutions work. ifconfig is not available on Jessie. ip
seems to be inapropriate. dig produces nothing. I have used ifconfig on
other distros.
I'm using DHCP at home, and it appears to me that the answer Lisi Reisz
kindly provided you with
Am Freitag, 17. Juli 2015, 12:49:59 schrieb John J. Boyer:
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
>
> John
Hi John,
just an idea.
If you know a little bit about the range
Why isn't ifconfig available on Jessie? There id no package. The
command produces an error message that it has not been found.
John
On Fri, Jul 17, 2015 at 01:44:35PM -0400, Miles Fidelman wrote:
> John J. Boyer wrote:
> >I have Jessie set up for CLI only. The machine is on a local network
> >us
Le 17/07/2015 19:49, John J. Boyer a écrit :
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
>
> John
>
> On Fri, Jul 17, 2015 at 05:41:27PM +0200, Elimar Riesebieter wrote:
>> * Joh
None of these solutions work. ifconfig is not available on Jessie. ip
seems to be inapropriate. dig produces nothing. I have used ifconfig on
other distros.
John
On Fri, Jul 17, 2015 at 05:41:27PM +0200, Elimar Riesebieter wrote:
> * John J. Boyer [2015-07-17 08:32 -0500]:
>
> > I have Jessie
John J. Boyer wrote:
I have Jessie set up for CLI only. The machine is on a local network
using dhcp. What command will tell me what ip address it is using?
Thanks,
John
ifconfig -a
is always a good one
--
In theory, there is no difference between theory and practice.
In practice, there is.
On Jul 17, 2015 11:53 AM, "Elimar Riesebieter" wrote:
>
> * John J. Boyer [2015-07-17 08:32 -0500]:
>
> > I have Jessie set up for CLI only. The machine is on a local network
> > using dhcp. What command will tell me what ip address it is using?
>
> $ dig +short `hostname -f`
>
Won't always wor
* John J. Boyer [2015-07-17 08:32 -0500]:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
$ dig +short `hostname -f`
Elimar
--
The path to source is always uphill!
-un
John J. Boyer writes:
I have Jessie set up for CLI only. The machine is on a local
network using dhcp. What command will tell me what ip address
it is using?
$ ip addr
Alexis.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Fri 17 Jul 2015 at 08:32:59 -0500, John J. Boyer wrote:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
ifconfig -a
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject o
On Friday 17 July 2015 14:32:59 John J. Boyer wrote:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
$ ip addr
HTH
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject o
Hi,
On 07/17/2015 03:32 PM, John J. Boyer wrote:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
ifconfig ?
Kind regards,
--
“One original thought is worth a thousand mindless quotings.”
“Le vrai n'est
Petter Adsen wrote:
> Reco wrote:
> > May I suggest using etckeeper for this? The tool is invaluable if one
> > needs to answer a question such as "what exactly did I changed a
> > couple of days ago?". The usual caveat is that using etckeeper
> > requires at least casual knowledge of any RCS that'
On Tue, 26 May 2015 18:18:15 +0300
Reco wrote:
> On Tue, May 26, 2015 at 12:42:50PM +0200, Petter Adsen wrote:
> > And even worse, after starting to mess with this, browsing is
> > _abysmal_. After taking a few speed tests online (speed.io etc),
> > upload/download and ping times seem good, but t
On Tue, May 26, 2015 at 12:57:52PM +0200, Petter Adsen wrote:
>
> > > > > > > I've been trying to improve NFS performance at home, and in
> > > > > > > that process i ran iperf to get an overview of general
> > > > > > > network performance. I have two Jessie hosts connected to a
> > > > > > > dumb
On Tue, May 26, 2015 at 12:42:50PM +0200, Petter Adsen wrote:
> On Sun, 24 May 2015 16:01:41 +0300
> Reco wrote:
>
> > Hi.
> >
> > On Sun, 24 May 2015 13:47:48 +0200
> > Petter Adsen wrote:
> >
> > > On Sun, 24 May 2015 13:26:52 +0200
> > > Petter Adsen wrote:
> > > > Thanks to you, I now ge
On Sun, 24 May 2015 15:53:17 +0300
Reco wrote:
> Hi.
>
> On Sun, 24 May 2015 13:26:52 +0200
> Petter Adsen wrote:
>
> > > On Sun, 24 May 2015 11:28:36 +0200
> > > Petter Adsen wrote:
> > >
> > > > > On Sun, 24 May 2015 10:36:39 +0200
> > > > > Petter Adsen wrote:
> > > > >
> > > > > > I'v
On Sun, 24 May 2015 16:01:41 +0300
Reco wrote:
> Hi.
>
> On Sun, 24 May 2015 13:47:48 +0200
> Petter Adsen wrote:
>
> > On Sun, 24 May 2015 13:26:52 +0200
> > Petter Adsen wrote:
> > > Thanks to you, I now get ~880Mbps, which is a lot better. It seems
> > > increasing the MTU was what had th
Hi.
On Sun, 24 May 2015 13:47:48 +0200
Petter Adsen wrote:
> On Sun, 24 May 2015 13:26:52 +0200
> Petter Adsen wrote:
> > Thanks to you, I now get ~880Mbps, which is a lot better. It seems
> > increasing the MTU was what had the most effect, so I won't bother
> > with TCP window size.
>
> Now
Hi.
On Sun, 24 May 2015 13:26:52 +0200
Petter Adsen wrote:
> > On Sun, 24 May 2015 11:28:36 +0200
> > Petter Adsen wrote:
> >
> > > > On Sun, 24 May 2015 10:36:39 +0200
> > > > Petter Adsen wrote:
> > > >
> > > > > I've been trying to improve NFS performance at home, and in that
> > > > > p
On Sun, 24 May 2015 13:26:52 +0200
Petter Adsen wrote:
> Thanks to you, I now get ~880Mbps, which is a lot better. It seems
> increasing the MTU was what had the most effect, so I won't bother
> with TCP window size.
Now, this is a little odd:
petter@monster:/etc$ iperf -i 1 -c fenris -r
--
On Sun, 24 May 2015 13:20:04 +0300
Reco wrote:
> Hi.
>
> On Sun, 24 May 2015 11:28:36 +0200
> Petter Adsen wrote:
>
> > > On Sun, 24 May 2015 10:36:39 +0200
> > > Petter Adsen wrote:
> > >
> > > > I've been trying to improve NFS performance at home, and in that
> > > > process i ran iperf t
Hi.
On Sun, 24 May 2015 11:28:36 +0200
Petter Adsen wrote:
> > On Sun, 24 May 2015 10:36:39 +0200
> > Petter Adsen wrote:
> >
> > > I've been trying to improve NFS performance at home, and in that
> > > process i ran iperf to get an overview of general network
> > > performance. I have two Je
On Sun, 24 May 2015 12:02:32 +0300
Reco wrote:
> Hi.
>
> On Sun, 24 May 2015 10:36:39 +0200
> Petter Adsen wrote:
>
> > I've been trying to improve NFS performance at home, and in that
> > process i ran iperf to get an overview of general network
> > performance. I have two Jessie hosts conne
Hi.
On Sun, 24 May 2015 10:36:39 +0200
Petter Adsen wrote:
> I've been trying to improve NFS performance at home, and in that
> process i ran iperf to get an overview of general network performance.
> I have two Jessie hosts connected to a dumb switch with Cat-5e. One
> host uses a Realtek RTL8
Nemeth Gyorgy a écrit :
>>
> Yes, it can work as a short go-nogo test. But the suggestion was not
> mentioned it, that it is only for that. And it is very likely that when
> the OP tries this and it 'works' (I mean the Windows machine behind the
> Linux works well), then the rules will remain.
I w
I adopted Mr. Gyorgy's suggested iptables rules with only a
couple of additions based on nmap's report that port 411 was open
because it passed with flying colors nmaps tcp and udp scan of the
first 1056 ports, grc.com tests and pcflank.com tests.
For a single user system running no service
2014-08-10 22:30 keltezéssel, Joe írta:
> Why is it unresolvable? A DROP/REJECT policy is fail-safe, ACCEPT
> isn't. If the rest of the rules are correct, (and more importantly,
> guaranteed always to stay that way in the face of editing, sometimes
> rushed) an ACCEPT policy is redundant, and if th
On Tue, Aug 12, 2014 at 5:19 AM, Joe wrote:
> On Tue, 12 Aug 2014 04:53:51 -0400
> Tom H wrote:
>>
>> And you've proven my point...
>
> Agreed, I just can't see why there is any controversy.
You misunderstand. The fact that you can't accept that there may be
others who have good reason (whatever
On Tue, 12 Aug 2014 04:53:51 -0400
Tom H wrote:
>
> And you've proven my point...
>
>
Agreed, I just can't see why there is any controversy.
--
Joe
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian
On Sun, Aug 10, 2014 at 4:30 PM, Joe wrote:
> On Sun, 10 Aug 2014 16:07:01 -0400
> Tom H wrote:
>> On Sun, Aug 10, 2014 at 2:24 PM, Nemeth Gyorgy
>> wrote:
>>> 2014-08-10 11:33 keltezéssel, Pascal Hambourg írta:
sysctl -w net.ipv4.ip_forward=1
iptables -t nat -P ACCEPT
iptabl
On Mon, Aug 11, 2014 at 02:06:28PM +0200, Pascal Hambourg wrote:
> Mike McClain a ?crit :
> >
> > Clearly DNS lookup is working and I have a problem with the
> > configuration of IE.
>
> Check in its network settings whether a proxy is defined, and remove it.
Hi Pascal,
Nope, no proxy.
Mike McClain a écrit :
>
> Clearly DNS lookup is working and I have a problem with the
> configuration of IE.
Check in its network settings whether a proxy is defined, and remove it.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Mon, 11 Aug 2014 17:44:52 +1000
Andrew McGlashan wrote:
>
> I give another vote for IPCop btw that or pfsense, but IPCop is
> simpler.
>
Yes, but it's a distribution in itself, which means you need to
dedicate an entire computer to it. (No, I don't think there is any point
in running
On 10/08/2014 10:06 AM, Mike McClain wrote:
>> Please describe your network topology. Where's the Win2k box ?
> __
> | Debian| LAN| Windows 2000 |
> Inet|Linux|-
On Sun, 10 Aug 2014 16:07:01 -0400
Tom H wrote:
> On Sun, Aug 10, 2014 at 2:24 PM, Nemeth Gyorgy
> wrote:
> > 2014-08-10 11:33 keltezéssel, Pascal Hambourg írta:
> >>
> >> Nemeth Gyorgy's ruleset is too complicated. Use the bare minimum :
> >>
> >> sysctl -w net.ipv4.ip_forward=1
> >> iptables -
On Sun, Aug 10, 2014 at 2:24 PM, Nemeth Gyorgy wrote:
> 2014-08-10 11:33 keltezéssel, Pascal Hambourg írta:
>>
>> Nemeth Gyorgy's ruleset is too complicated. Use the bare minimum :
>>
>> sysctl -w net.ipv4.ip_forward=1
>> iptables -t nat -P ACCEPT
>> iptables -t filter -P ACCEPT
>
> This is really
2014-08-10 11:33 keltezéssel, Pascal Hambourg írta:
> Nemeth Gyorgy's ruleset is too complicated. Use the bare minimum :
>
> sysctl -w net.ipv4.ip_forward=1
> iptables -t nat -P ACCEPT
> iptables -t filter -P ACCEPT
This is really a big sechole.
> iptables -t mangle -P ACCEPT
> iptables -t nat -
2014-08-10 01:49 keltezéssel, Mike McClain írta:
>> It's a rather complicated, sometimes overcomplicated script. But some
>> rules are missing and/or not in the correct order.
>
> I've little doubt you are correct, admittedly I'm flailing a bit.
> Trying this and that with little luck.
> I'd appre
On Sun, Aug 10, 2014 at 11:33:27AM +0200, Pascal Hambourg wrote:
>
> Nemeth Gyorgy's ruleset is too complicated. Use the bare minimum :
>
> sysctl -w net.ipv4.ip_forward=1
> iptables -t nat -P ACCEPT
> iptables -t filter -P ACCEPT
> iptables -t mangle -P ACCEPT
> iptables -t nat -F
> iptables -t fi
On Sat, Aug 09, 2014 at 10:30:53PM -0600, Bob Proulx wrote:
> Mike McClain wrote:
> > Pascal Hambourg wrote:
> > > Please describe your network topology. Where's the Win2k box ?
> >
> > __
> > | Debian|
Mike McClain a écrit :
>
> from a zsh prompt:
> Mike zsh:~> nslookup
> Default Server: resolver1.opendns.com
> Address: 208.67.222.222
>
> Didn't return.
Of course not. If you don't provide a domain name to query in the
command line, nslookup just sits there and waits for a command or a name
to
Mike McClain a écrit :
> On Fri, Aug 08, 2014 at 09:13:23PM +0200, Pascal Hambourg wrote:
>>
>> Same as Nemeth Gyorgy : restart without any filtering, just the IP
>> forwarding and masquerading. If it does not work, it's not due to
>> filtering. Then when everything works add the filtering.
>
> Al
Bob Proulx a écrit :
> Mike McClain wrote:
>> __
>> | Debian| LAN| Windows 2000 |
>> Inet|Linux|-| S40 |
>> (ppp) | 192.168.1.2 |
Mike McClain wrote:
> Pascal Hambourg wrote:
> > Please describe your network topology. Where's the Win2k box ?
>
> __
> | Debian| LAN| Windows 2000 |
> Inet|Linux|
On Fri, Aug 08, 2014 at 09:13:23PM +0200, Pascal Hambourg wrote:
> Hello,
>
> Mike McClain a ?crit :
> > I've been trying to get my hand rolled iptables firewall to
> > masquerade traffic on the LAN to/from a Win2K box.
>
> Please describe your network topology. Where's the Win2k box ?
On Fri, Aug 08, 2014 at 08:24:11PM +0200, Nemeth Gyorgy wrote:
> 2014-08-08 09:04 keltez?ssel, Mike McClain ?rta:
> > I've been trying to get my hand rolled iptables firewall to
> > masquerade traffic on the LAN to/from a Win2K box. I've gotten it to
> > the point that I can ping from the boxes
On Fri, Aug 08, 2014 at 09:16:05PM -0700, Matt Ventura wrote:
> On 8/8/2014 12:04 AM, Mike McClain wrote:
> > I've been trying to get my hand rolled iptables firewall to
> >masquerade traffic on the LAN to/from a Win2K box. I've gotten it to
> >the point that I can ping from the boxes both ways
On Fri, Aug 08, 2014 at 07:05:28PM -0700, David Christensen wrote:
> On 08/08/2014 12:04 AM, Mike McClain wrote:
> > I've been trying to get my hand rolled iptables firewall to
> >masquerade traffic on the LAN to/from a Win2K box.
>
> I used to write my own firewall/ router rules, but then disc
On 8/8/2014 12:04 AM, Mike McClain wrote:
I've been trying to get my hand rolled iptables firewall to
masquerade traffic on the LAN to/from a Win2K box. I've gotten it to
the point that I can ping from the boxes both ways, smbclient can move
files both ways and the Win2K box can ping Google'
1 - 100 of 723 matches
Mail list logo
