> They are wrong because there is no way for network traffic from the
> devices on the LAN to make it to the interface enp2s0. Or, if they do
> make it there, then there is something else seriously wrong.
>
tcpdump -i enp2s0 arp
will tell you if the arps are being generated from something on the
> Even after adding the static routes and creating firewall rules to drop
> all traffic from the devices to the internet, their arp entries continue
> to be renewed. How is that possible?
>
>
Your iptables rules are IP based (layer 3), so will not match arp traffic
(layer 2)
On Sat, 26 Dec 2015 14:00:55 Paul Colquhoun wrote:
> On Fri, 25 Dec 2015 12:40:48 walt wrote:
> > On Thu, 24 Dec 2015 10:18:27 -0500
> >
> > Alan Grimes wrote:
> > > Hey, thanks for putting out gcc 5.3...
> > >
> > > Unfortunately, it fails to bootstrap on my machine. I am getting
> > > differen
Adam Carter writes:
>>
>> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
>> enp2s0
>> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
>> enp1s0
>> spa.yagibdah.de (192.168.3.81) auf 88:75:56:07:44:c8 [ether] auf enp2s0
>> spa.yagibdah.de (192.168
Rich Freeman writes:
> On Fri, Dec 25, 2015 at 9:00 PM, Adam Carter wrote:
>>> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
>>> enp2s0
>>> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
>>> enp1s0
>>> spa.yagibdah.de (192.168.3.81) auf 88:75:
On Fri, Dec 25, 2015 at 9:00 PM, Adam Carter wrote:
>> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
>> enp2s0
>> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
>> enp1s0
>> spa.yagibdah.de (192.168.3.81) auf 88:75:56:07:44:c8 [ether] auf enp2s0
On Fri, 25 Dec 2015 12:40:48 walt wrote:
> On Thu, 24 Dec 2015 10:18:27 -0500
>
> Alan Grimes wrote:
> > Hey, thanks for putting out gcc 5.3...
> >
> > Unfortunately, it fails to bootstrap on my machine. I am getting
> > differences between the stage 2 and stage 3 compilers and it's
> > dying...
>
> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
> enp2s0
> grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf
> enp1s0
> spa.yagibdah.de (192.168.3.81) auf 88:75:56:07:44:c8 [ether] auf enp2s0
> spa.yagibdah.de (192.168.3.81) auf 88:75:56:07:44:c8
Hi,
any idea why I have entries in the arp table like this:
grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf enp2s0
grandstream.yagibdah.de (192.168.3.80) auf 00:0b:82:16:ed:9e [ether] auf enp1s0
spa.yagibdah.de (192.168.3.81) auf 88:75:56:07:44:c8 [ether] auf enp2s0
spa.
On Thu, 24 Dec 2015 10:18:27 -0500
Alan Grimes wrote:
> Hey, thanks for putting out gcc 5.3...
>
> Unfortunately, it fails to bootstrap on my machine. I am getting
> differences between the stage 2 and stage 3 compilers and it's
> dying... =(
I'm waiting for 5.3.1 before I even try to install i
David Haller wrote:
> Hello,
>
> On Thu, 24 Dec 2015, Alan Grimes wrote:
>> Hey, thanks for putting out gcc 5.3...
>>
>> Unfortunately, it fails to bootstrap on my machine. I am getting
>> differences between the stage 2 and stage 3 compilers and it's dying... =(
> What compiler and C(XX)FLAGS are
Andreas K. Huettel wrote:
> Am Donnerstag, 24. Dezember 2015, 16:18:27 schrieb Alan Grimes:
> > Hey, thanks for putting out gcc 5.3...
>
> > Unfortunately, it fails to bootstrap on my machine. I am getting
> > differences between the stage 2 and stage 3 compilers and it's
> dying... =(
>
>
> "emerg
On Fri, Dec 25, 2015 at 04:10:40AM +, Ian Bloss wrote
> I was saying the libsdl packages have a USE flag "sound" which builds the
> sound module for sdl. So if qemu makes any calls to the sound module not
> pure alsa calls, that might be causing your issue.
>
> Wabes USE flag output shows he's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Donnerstag, 24. Dezember 2015, 16:18:27 schrieb Alan Grimes:
> Hey, thanks for putting out gcc 5.3...
>
> Unfortunately, it fails to bootstrap on my machine. I am getting
> differences between the stage 2 and stage 3 compilers and it's dying... =
Am Thu, 24 Dec 2015 20:22:45 -0200
schrieb João Matos :
> Dear list,
>
> I was having problem with plasma, so I decided to change it.
>
> I've removed all packages related from world, changed the profile,
> erased use-related files from /etc/portage.
>
> Then I've used "emerge --depclean", that
15 matches
Mail list logo