On Di, 2016-09-27 at 05:42 +0200, Armin Tüting wrote:
...
I've made the suggested changes, but still no joy!
I'm seeing the traffic arriving with tcpdump, but the chain
'EXT_INPUT_CHAIN' doesn't show the packet.
Regards,
Armin.
--
On Mo, 2016-09-26 at 22:15 -0500, Lonnie Abelbeck wrote:
> On Sep 26, 2016, at 8:42 PM, Armin Tüting ne.com> wrote:
>
> >
> > On Mo, 2016-09-26 at 14:31 -0500, Lonnie Abelbeck wrote:
> > >
> > > On Sep 26, 2016, at 1:16 PM, Armin Tüting > > onli
> > > ne.com> wrote:
> > >
> > > >
> > > >
>
On Sep 26, 2016, at 8:42 PM, Armin Tüting
wrote:
> On Mo, 2016-09-26 at 14:31 -0500, Lonnie Abelbeck wrote:
>> On Sep 26, 2016, at 1:16 PM, Armin Tüting > ne.com> wrote:
>>
>>>
>
> ip route
> default via 192.168.60.1 dev eth0 metric 2
> 192.168.10.0/24 via 192.168.40.
On Mo, 2016-09-26 at 14:31 -0500, Lonnie Abelbeck wrote:
> On Sep 26, 2016, at 1:16 PM, Armin Tüting ne.com> wrote:
>
> >
> > >
> > > >
> > > > ip route
> > > > default via 192.168.60.1 dev eth0 metric 2
> > > > 192.168.10.0/24 via 192.168.40.1 dev eth1 metric 1
> > > > 192.168.40.0/24 dev
On Sep 26, 2016, at 1:16 PM, Armin Tüting
wrote:
>>> ip route
>>> default via 192.168.60.1 dev eth0 metric 2
>>> 192.168.10.0/24 via 192.168.40.1 dev eth1 metric 1
>>> 192.168.40.0/24 dev eth1 proto kernel scope link src
>>> 192.168.40.6
>>> 192.168.50.0/24 via 192.168.40.1 dev eth1 me
On Mo, 2016-09-26 at 11:52 -0500, Lonnie Abelbeck wrote:
> On Sep 26, 2016, at 11:13 AM, Armin Tüting ine.com> wrote:
>
> >
> > >
> > > Also try:
> > > --
> > > arp-scan -lI eth0
> > > --
> > > and make sure you don't colliding IP's.
> > No double ip addresses! But, where is my AstLinux
> > ar
Hello all
I work for Northumberland National Park Authority in the UK, and we've been
using AstLinux for many years. I built our system, and maintained it.
However, three things mean I would like to get some external help in:
1. We are out of date - I was away for 18 months during which our boxes
On Sep 26, 2016, at 11:13 AM, Armin Tüting
wrote:
>> Also try:
>> --
>> arp-scan -lI eth0
>> --
>> and make sure you don't colliding IP's.
> No double ip addresses! But, where is my AstLinux
> arp-scan -lI eth0
> Interface: eth0, datalink type: EN10MB (Ethernet)
> Starting arp-scan 1.9 with 25
On Mo, 2016-09-26 at 11:03 -0500, Lonnie Abelbeck wrote:
> On Sep 26, 2016, at 10:49 AM, Armin Tüting ine.com> wrote:
>
> >
> >
> > BTW - I've assigned a static RFC 1918 address (192.168.0.0/16) to
> > EXTIF
> > and INTIF. Could this be the root cause of my issue?
>
> As long as both EXTIF an
On Mo, 2016-09-26 at 10:58 -0500, Lonnie Abelbeck wrote:
> On Sep 26, 2016, at 10:39 AM, Armin Tüting ine.com> wrote:
>
> >
> > On Mo, 2016-09-26 at 09:12 -0500, Lonnie Abelbeck wrote:
> > >
> > > 1) When I spoke of "user.conf" I meant the file
> > > /mnt/kd/rc.conf.d/user.conf which does not h
On Sep 26, 2016, at 10:49 AM, Armin Tüting
wrote:
>
> BTW - I've assigned a static RFC 1918 address (192.168.0.0/16) to EXTIF
> and INTIF. Could this be the root cause of my issue?
As long as both EXTIF and INTIF networks are non-overlapping, that is fine.
But if *any* of your network inter
On Sep 26, 2016, at 10:39 AM, Armin Tüting
wrote:
> On Mo, 2016-09-26 at 09:12 -0500, Lonnie Abelbeck wrote:
>> 1) When I spoke of "user.conf" I meant the file
>> /mnt/kd/rc.conf.d/user.conf which does not have anything enabled by
>> default.
> SYSLOGHOST, DIALING_PREFIX_NUMBERS, SENSEMODS, ALE
On Mo, 2016-09-26 at 09:12 -0500, Lonnie Abelbeck wrote:
> On Sep 26, 2016, at 8:27 AM, Armin Tüting ne.com> wrote:
>
> >
> > On Mo, 2016-09-26 at 07:56 -0500, Lonnie Abelbeck wrote:
> > >
> > > Armin,
> > Lonnie,
> >
> > thanks for your quick turnaround!
> >
> > >
> > > The only thing I can
On Mo, 2016-09-26 at 09:12 -0500, Lonnie Abelbeck wrote:
> 1) When I spoke of "user.conf" I meant the file
> /mnt/kd/rc.conf.d/user.conf which does not have anything enabled by
> default.
SYSLOGHOST, DIALING_PREFIX_NUMBERS, SENSEMODS, ALERT_SOUNDS, VAR_SIZE,
TMP_SIZE and VI_EDITOR_OPTIONS.
> 2) If
On Sep 26, 2016, at 8:27 AM, Armin Tüting
wrote:
> On Mo, 2016-09-26 at 07:56 -0500, Lonnie Abelbeck wrote:
>> Armin,
> Lonnie,
>
> thanks for your quick turnaround!
>
>> The only thing I can think of that would effect external interface
>> routing is if the Network tab -> Failover Interface:
On Mo, 2016-09-26 at 07:56 -0500, Lonnie Abelbeck wrote:
> Armin,
Lonnie,
thanks for your quick turnaround!
> The only thing I can think of that would effect external interface
> routing is if the Network tab -> Failover Interface: was enabled. I
> presume yours is [ none ] ?
Yes, it is!
> Do y
On Sep 26, 2016, at 3:52 AM, Armin Tüting
wrote:
> On Fr, 2016-09-23 at 09:30 -0500, Lonnie Abelbeck wrote:
>> On Sep 23, 2016, at 9:02 AM, Armin Tüting > ne.com> wrote:
>>
>>>
>>> Hi Group,
I'm having the latest AstLinux 1.2.7 running. So far I'm
experiencing
no i
On Fr, 2016-09-23 at 09:30 -0500, Lonnie Abelbeck wrote:
> On Sep 23, 2016, at 9:02 AM, Armin Tüting ne.com> wrote:
>
> >
> > Hi Group,
> > >
> > >
> > > I'm having the latest AstLinux 1.2.7 running. So far I'm
> > > experiencing
> > > no issue while connecting the phone via internal interfac
18 matches
Mail list logo
