Menu
▾
▴
astlinux-users — AstLinux Users Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
| 2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
| 2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
| 2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
| 2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
| 2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
| 2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
| 2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
| 2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
| 2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
| 2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
| 2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
| 2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
| 2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
| 2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
| 2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
| 2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
| 2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
| 2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
(1) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Lonnie A. <li...@lo...> - 2020-11-28 13:56:51
|
Announcing AstLinux Pre-Release: astlinux-1.4-4914-e9aab1
** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.
-- Linux Kernel 4.19.160 (version bump), security and bug fixes
-- WireGuard VPN, module 1.0.20201112 (version bump), tools 1.0.20200827 (no change)
-- libcurl (curl) version bump to 7.73.0
-- chrony, version bump to 4.0
-- miniupnpd, version 2.1, add Debian security fixes: CVE-2019-12107, CVE-2019-12108
CVE-2019-12109, CVE-2019-12110, CVE-2019-12111
-- sngrep, version bump to 1.4.8
-- Monit, version bump to 5.27.1
-- zabbix, version bump to 4.0.26
-- Asterisk 13.29.2 ('13se' no change)
Older than latest Asterisk 13.x version but more tested, built --without-pjproject
-- Asterisk 13.38.0 (version bump) and 16.15.0 (version bump)
-- DAHDI, dahdi-linux 3.1.0 (no change) and dahdi-tools 3.1.0 (no change)
-- pjsip 2.10 (no change)
-- Add support for directory /var/spool/asterisk/outgoing_tmp for call file staging.
-- Add support for persistent /mnt/kd/call-file/ directory for certain tmpfs spool directories.
If the directory /mnt/kd/call-file/ exists, the following symlinks will automatically occur:
== /var/spool/asterisk/outgoing -> /mnt/kd/call-file/outgoing
== /var/spool/asterisk/outgoing_tmp -> /mnt/kd/call-file/outgoing_tmp
== /var/spool/asterisk/outgoing_done -> /mnt/kd/call-file/outgoing_done
-- Complete Pre-Release ChangeLog:
https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt
The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...
AstLinux Project -> Development
https://www.astlinux-project.org/dev.html
AstLinux Team
|
|
From: Michael K. <mic...@ip...> - 2020-11-24 18:32:52
|
Yep thanks Lonnie. Already know about that one from experience ☹
Regards
Michael Knill
On 25/11/20, 1:03 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Yes, as long as you don't require PPPoE on the 2nd WAN (Failover) interface.
Lonnie
> On Nov 24, 2020, at 3:55 AM, Michael Knill <mic...@ip...> wrote:
>
> Yep I thought that may be the case. Thanks Michael.
>
> Regards
> Michael Knill
>
> On 24/11/20, 8:46 pm, "Michael Keuter" <li...@mk...> wrote:
>
>
>> Am 24.11.2020 um 06:34 schrieb Michael Knill <mic...@ip...>:
>>
>> Hi Group
>>
>> I'm wanting two external interfaces for my softswitch gateway with one connecting to the internet and the other connecting to a direct Megaport connection to my SIP provider.
>> I'm assuming that I can set up the following in user.conf:
>> EXT2IF="eth2"
>> EXT2IP="10.1.1.2"
>> EXT2NM="255.255.255.0"
>> EXT2GW="10.1.1.1"
>> EXT2ROUTES="<Provider routes here>"
>
> You can do this in the WebGUI:
> Failover Interface eth2
> The rest in the Failover tab, but disable failover.
>
>>
>> I also will have Failover disabled on the Failover tab.
>>
>> Is this workable? I'm assuming I will need common firewall entries for both interfaces?
>
> Yes.
>
>> I have always only done this in a failover scenario with both interfaces connected to the internet!
>>
>> Thanks all.
>>
>> Regards
>> Michael Knill
>
> Michael
>
> http://www.mksolutions.info
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2020-11-24 14:02:39
|
Yes, as long as you don't require PPPoE on the 2nd WAN (Failover) interface. Lonnie > On Nov 24, 2020, at 3:55 AM, Michael Knill <mic...@ip...> wrote: > > Yep I thought that may be the case. Thanks Michael. > > Regards > Michael Knill > > On 24/11/20, 8:46 pm, "Michael Keuter" <li...@mk...> wrote: > > >> Am 24.11.2020 um 06:34 schrieb Michael Knill <mic...@ip...>: >> >> Hi Group >> >> I'm wanting two external interfaces for my softswitch gateway with one connecting to the internet and the other connecting to a direct Megaport connection to my SIP provider. >> I'm assuming that I can set up the following in user.conf: >> EXT2IF="eth2" >> EXT2IP="10.1.1.2" >> EXT2NM="255.255.255.0" >> EXT2GW="10.1.1.1" >> EXT2ROUTES="<Provider routes here>" > > You can do this in the WebGUI: > Failover Interface eth2 > The rest in the Failover tab, but disable failover. > >> >> I also will have Failover disabled on the Failover tab. >> >> Is this workable? I'm assuming I will need common firewall entries for both interfaces? > > Yes. > >> I have always only done this in a failover scenario with both interfaces connected to the internet! >> >> Thanks all. >> >> Regards >> Michael Knill > > Michael > > http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2020-11-24 09:55:22
|
Yep I thought that may be the case. Thanks Michael.
Regards
Michael Knill
On 24/11/20, 8:46 pm, "Michael Keuter" <li...@mk...> wrote:
> Am 24.11.2020 um 06:34 schrieb Michael Knill <mic...@ip...>:
>
> Hi Group
>
> I'm wanting two external interfaces for my softswitch gateway with one connecting to the internet and the other connecting to a direct Megaport connection to my SIP provider.
> I'm assuming that I can set up the following in user.conf:
> EXT2IF="eth2"
> EXT2IP="10.1.1.2"
> EXT2NM="255.255.255.0"
> EXT2GW="10.1.1.1"
> EXT2ROUTES="<Provider routes here>"
You can do this in the WebGUI:
Failover Interface eth2
The rest in the Failover tab, but disable failover.
>
> I also will have Failover disabled on the Failover tab.
>
> Is this workable? I'm assuming I will need common firewall entries for both interfaces?
Yes.
> I have always only done this in a failover scenario with both interfaces connected to the internet!
>
> Thanks all.
>
> Regards
> Michael Knill
Michael
http://www.mksolutions.info
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Michael K. <li...@mk...> - 2020-11-24 09:46:02
|
> Am 24.11.2020 um 06:34 schrieb Michael Knill <mic...@ip...>: > > Hi Group > > I'm wanting two external interfaces for my softswitch gateway with one connecting to the internet and the other connecting to a direct Megaport connection to my SIP provider. > I'm assuming that I can set up the following in user.conf: > EXT2IF="eth2" > EXT2IP="10.1.1.2" > EXT2NM="255.255.255.0" > EXT2GW="10.1.1.1" > EXT2ROUTES="<Provider routes here>" You can do this in the WebGUI: Failover Interface eth2 The rest in the Failover tab, but disable failover. > > I also will have Failover disabled on the Failover tab. > > Is this workable? I'm assuming I will need common firewall entries for both interfaces? Yes. > I have always only done this in a failover scenario with both interfaces connected to the internet! > > Thanks all. > > Regards > Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2020-11-24 05:50:51
|
Hi Group I'm wanting two external interfaces for my softswitch gateway with one connecting to the internet and the other connecting to a direct Megaport connection to my SIP provider. I'm assuming that I can set up the following in user.conf: EXT2IF="eth2" EXT2IP="10.1.1.2" EXT2NM="255.255.255.0" EXT2GW="10.1.1.1" EXT2ROUTES="<Provider routes here>" I also will have Failover disabled on the Failover tab. Is this workable? I'm assuming I will need common firewall entries for both interfaces? I have always only done this in a failover scenario with both interfaces connected to the internet! Thanks all. Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2020-11-20 02:06:41
|
Hi Group Sorry guys I think this was a config error. I had the same address in the primary test and secondary route which I suspect broke things. Regards Michael Knill Sent from my iPhone so please excuse my brevity. > On 13 Nov 2020, at 9:07 am, Michael Knill <mic...@ip...> wrote: > > Hi Lonnie > > Yes a weird one. It is a static IP Address on eth0.100 and the cable was out for a while yet it did not fail over until I manually shut the interface. This was even after I reset the box. > I looked at the routing table and the default route remained pointing to the Default Gateway. > I will do some more testing and let you know. > > Regards > Michael Knill > > On 13/11/20, 2:45 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > If I understand correctly, your upstream internet worked for some destinations, but had an outage for others, so one of your WAN Failover -> "Target IPv4 Hosts" still worked, so it did not automatically failover. > > Unless this was a one-off fluke, you may want to consider "Target IPv4 Hosts" closer to your critical infrastructure. > > The fact that the WAN is a tagged VLAN should not make any difference. > > Back to your question, what happens when the WAN (External Interface) link goes down while failover is running. In general it should force a failover. > > But keep in mind, in order for the failover script to work properly, static /32 routes are defined for each "Target IPv4 Hosts" over the *primary* interface (or ppp0 for PPPoE). Without these static routes as soon as the secondary link became active the "Target IPv4 Hosts" would be reachable and failover would return back to primary ... maintaining the "Target IPv4 Hosts" static /32 routes over the primary interface (or ppp0 for PPPoE) is very important internally to the failover script. > > If something would happen to remove the primary interface and any routes associated with it, behind the back of the failover script, things would not work as expected temporarily, but the failover script will automatically refresh these routes if it detects they are missing. > > So "pulling the cable" may have forced failover if you waited long enough. > > Anyway, defining "Target IPv4 Hosts" closer to your critical infrastructure may be a solution. > > Lonnie > > > > >> On Nov 12, 2020, at 5:00 AM, Michael Knill <mic...@ip...> wrote: >> >> Hi Group >> >> I got caught this evening. >> One of our providers requires a tagged sub interface to be used for their WAN connection e.g. eth0.100. >> The WAN connection was broken but you could still ping at least one of the test IP Address. Ok that's fine I will just disconnect eth0 and it will fail over. Wrong it didn't! >> I had to shut down the sub interface with ‘ifconfig eth0.100 down’ to make it actually be down so it failed over. >> Is there a better way to do this? Can I actually bring this interface down externally any way? >> >> Thanks guys. >> >> Regards >> Michael Knill >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > |
|
From: Michael K. <mic...@ip...> - 2020-11-12 22:07:33
|
Hi Lonnie
Yes a weird one. It is a static IP Address on eth0.100 and the cable was out for a while yet it did not fail over until I manually shut the interface. This was even after I reset the box.
I looked at the routing table and the default route remained pointing to the Default Gateway.
I will do some more testing and let you know.
Regards
Michael Knill
On 13/11/20, 2:45 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
If I understand correctly, your upstream internet worked for some destinations, but had an outage for others, so one of your WAN Failover -> "Target IPv4 Hosts" still worked, so it did not automatically failover.
Unless this was a one-off fluke, you may want to consider "Target IPv4 Hosts" closer to your critical infrastructure.
The fact that the WAN is a tagged VLAN should not make any difference.
Back to your question, what happens when the WAN (External Interface) link goes down while failover is running. In general it should force a failover.
But keep in mind, in order for the failover script to work properly, static /32 routes are defined for each "Target IPv4 Hosts" over the *primary* interface (or ppp0 for PPPoE). Without these static routes as soon as the secondary link became active the "Target IPv4 Hosts" would be reachable and failover would return back to primary ... maintaining the "Target IPv4 Hosts" static /32 routes over the primary interface (or ppp0 for PPPoE) is very important internally to the failover script.
If something would happen to remove the primary interface and any routes associated with it, behind the back of the failover script, things would not work as expected temporarily, but the failover script will automatically refresh these routes if it detects they are missing.
So "pulling the cable" may have forced failover if you waited long enough.
Anyway, defining "Target IPv4 Hosts" closer to your critical infrastructure may be a solution.
Lonnie
> On Nov 12, 2020, at 5:00 AM, Michael Knill <mic...@ip...> wrote:
>
> Hi Group
>
> I got caught this evening.
> One of our providers requires a tagged sub interface to be used for their WAN connection e.g. eth0.100.
> The WAN connection was broken but you could still ping at least one of the test IP Address. Ok that's fine I will just disconnect eth0 and it will fail over. Wrong it didn't!
> I had to shut down the sub interface with ‘ifconfig eth0.100 down’ to make it actually be down so it failed over.
> Is there a better way to do this? Can I actually bring this interface down externally any way?
>
> Thanks guys.
>
> Regards
> Michael Knill
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2020-11-12 15:44:39
|
Hi Michael, If I understand correctly, your upstream internet worked for some destinations, but had an outage for others, so one of your WAN Failover -> "Target IPv4 Hosts" still worked, so it did not automatically failover. Unless this was a one-off fluke, you may want to consider "Target IPv4 Hosts" closer to your critical infrastructure. The fact that the WAN is a tagged VLAN should not make any difference. Back to your question, what happens when the WAN (External Interface) link goes down while failover is running. In general it should force a failover. But keep in mind, in order for the failover script to work properly, static /32 routes are defined for each "Target IPv4 Hosts" over the *primary* interface (or ppp0 for PPPoE). Without these static routes as soon as the secondary link became active the "Target IPv4 Hosts" would be reachable and failover would return back to primary ... maintaining the "Target IPv4 Hosts" static /32 routes over the primary interface (or ppp0 for PPPoE) is very important internally to the failover script. If something would happen to remove the primary interface and any routes associated with it, behind the back of the failover script, things would not work as expected temporarily, but the failover script will automatically refresh these routes if it detects they are missing. So "pulling the cable" may have forced failover if you waited long enough. Anyway, defining "Target IPv4 Hosts" closer to your critical infrastructure may be a solution. Lonnie > On Nov 12, 2020, at 5:00 AM, Michael Knill <mic...@ip...> wrote: > > Hi Group > > I got caught this evening. > One of our providers requires a tagged sub interface to be used for their WAN connection e.g. eth0.100. > The WAN connection was broken but you could still ping at least one of the test IP Address. Ok that's fine I will just disconnect eth0 and it will fail over. Wrong it didn't! > I had to shut down the sub interface with ‘ifconfig eth0.100 down’ to make it actually be down so it failed over. > Is there a better way to do this? Can I actually bring this interface down externally any way? > > Thanks guys. > > Regards > Michael Knill > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2020-11-12 11:16:50
|
Hi Group I got caught this evening. One of our providers requires a tagged sub interface to be used for their WAN connection e.g. eth0.100. The WAN connection was broken but you could still ping at least one of the test IP Address. Ok that's fine I will just disconnect eth0 and it will fail over. Wrong it didn't! I had to shut down the sub interface with ‘ifconfig eth0.100 down’ to make it actually be down so it failed over. Is there a better way to do this? Can I actually bring this interface down externally any way? Thanks guys. Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2020-10-15 00:21:52
|
Ignore my last email sorry. It worked fine when the driver was configured correctly.
Regards
Michael Knill
From: Michael Knill <mic...@ip...>
Reply to: AstLinux List <ast...@li...>
Date: Thursday, 15 October 2020 at 11:04 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Secondary IP Address
Hi All
It certainly works using Bonjour however their windows machines still cannot discover the printer on the other network.
I suspect its using WSD which uses IP Multicast to perform the discovery.
Any way I can implement this?
Regards
Michael Knill
From: Michael Knill <mic...@ip...>
Reply to: AstLinux List <ast...@li...>
Date: Thursday, 15 October 2020 at 8:50 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Secondary IP Address
Yes they are (well VLAN interfaces on the same Physical interface anyway).
Thanks David/Lonnie for the info here. It seems to be exactly what I am looking for.
I will let you know how I go.
Regards
Michael Knill
From: David Kerr <da...@ke...>
Reply to: AstLinux List <ast...@li...>
Date: Thursday, 15 October 2020 at 8:45 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Secondary IP Address
Are the two subnets connected to two different LAN interfaces on Astlinux? If so look at the avahi service and in avahi-daemon.conf add this...
[reflector]
enable-reflector=yes
reflect-ipv=no
#reflect-filters=_printer._tcp.local,_ipp._tcp.local,_pdl-datastream._tcp.local,_airplay._tcp.local,_raop._tcp.local,_googlecast._tcp.local,_googlerpc._tcp.local,_googlezone._tcp.local,_hap._tcp.local,_appletv-v2._tcp.local,_homekit._tcp.local
I have commented out the reflect-filter line above which means "reflect" all bonjour traffic across interfaces, if you uncomment then only those listed services will be reflected between LANs... above I have a typical set.
You can view what services are broadcast on your LANs with the "Discovery" app available in both the iOS and MacOS app stores (I don't know about Android but presume there is a version for that too). Beware that clients cache what they find so enabling/disabling or changing the reflect-filter in avahi does not necessarily get immediately picked up by the clients.
And... if you want a client on one LAN to talk to a printer on another LAN then firewall rules need to permit the traffic.
David
On Wed, Oct 14, 2020 at 5:11 PM Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
Would it be worth turning on UPnP do you think?
Regards
Michael Knill
On 15/10/20, 8:08 am, "Michael Knill" <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Guys
It seems that this was working fine when the Cisco router was in place and only stopped when the Astlinux box was put in place.
Looking at the Cisco router I do see 'ip forward-protocol nd' with nd being the Neighbor Discovery Protocol which may have been the reason it worked.
Is it possible to set this up on Astlinux?
Regards
Michael Knill
On 14/10/20, 7:34 am, "Michael Knill" <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Lonnie. Good question.
I have a site with two customers sharing the same network and telephony infrastructure.
The data network is segregated for the two customers but there is a single shared printer on one of the networks.
The customer on the other network is having problems with the printer and their current IT provider has said that because the driver is so crap, the printer needs to be on the same network (Sigh!)
Also this network has a number of statically assigned devices.
I must admit that as I write this, I'm not sure this is going to solve the problem. So ridiculous!
Thanks guys though for the info.
Regards
Michael Knill
On 14/10/20, 12:22 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote:
A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ?
A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox).
So, if for some reason you want to add 192.168.99.1/32<http://192.168.99.1/32> to eth1, simply:
--
ip addr add 192.168.99.1/32<http://192.168.99.1/32> dev eth1
--
If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label:
--
ip addr add 192.168.99.1/32<http://192.168.99.1/32> dev eth1 label eth1:1
--
Lonnie
> On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...<mailto:li...@mk...>> wrote:
>
>
>
>> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...<mailto:mic...@ip...>>:
>>
>> Hi Group
>>
>> Is there a way to add a secondary LAN IP Address with Astlinux?
>> I cant see an INTIP_ALIAS variable!
>>
>> Regards
>> Michael Knill
>
> https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/
>
> You have to add this to rc.elocal to make it persistent.
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...<mailto:Ast...@li...>
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
>
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
|
|
From: Michael K. <mic...@ip...> - 2020-10-15 00:04:05
|
Hi All
It certainly works using Bonjour however their windows machines still cannot discover the printer on the other network.
I suspect its using WSD which uses IP Multicast to perform the discovery.
Any way I can implement this?
Regards
Michael Knill
From: Michael Knill <mic...@ip...>
Reply to: AstLinux List <ast...@li...>
Date: Thursday, 15 October 2020 at 8:50 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Secondary IP Address
Yes they are (well VLAN interfaces on the same Physical interface anyway).
Thanks David/Lonnie for the info here. It seems to be exactly what I am looking for.
I will let you know how I go.
Regards
Michael Knill
From: David Kerr <da...@ke...>
Reply to: AstLinux List <ast...@li...>
Date: Thursday, 15 October 2020 at 8:45 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Secondary IP Address
Are the two subnets connected to two different LAN interfaces on Astlinux? If so look at the avahi service and in avahi-daemon.conf add this...
[reflector]
enable-reflector=yes
reflect-ipv=no
#reflect-filters=_printer._tcp.local,_ipp._tcp.local,_pdl-datastream._tcp.local,_airplay._tcp.local,_raop._tcp.local,_googlecast._tcp.local,_googlerpc._tcp.local,_googlezone._tcp.local,_hap._tcp.local,_appletv-v2._tcp.local,_homekit._tcp.local
I have commented out the reflect-filter line above which means "reflect" all bonjour traffic across interfaces, if you uncomment then only those listed services will be reflected between LANs... above I have a typical set.
You can view what services are broadcast on your LANs with the "Discovery" app available in both the iOS and MacOS app stores (I don't know about Android but presume there is a version for that too). Beware that clients cache what they find so enabling/disabling or changing the reflect-filter in avahi does not necessarily get immediately picked up by the clients.
And... if you want a client on one LAN to talk to a printer on another LAN then firewall rules need to permit the traffic.
David
On Wed, Oct 14, 2020 at 5:11 PM Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
Would it be worth turning on UPnP do you think?
Regards
Michael Knill
On 15/10/20, 8:08 am, "Michael Knill" <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Guys
It seems that this was working fine when the Cisco router was in place and only stopped when the Astlinux box was put in place.
Looking at the Cisco router I do see 'ip forward-protocol nd' with nd being the Neighbor Discovery Protocol which may have been the reason it worked.
Is it possible to set this up on Astlinux?
Regards
Michael Knill
On 14/10/20, 7:34 am, "Michael Knill" <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Lonnie. Good question.
I have a site with two customers sharing the same network and telephony infrastructure.
The data network is segregated for the two customers but there is a single shared printer on one of the networks.
The customer on the other network is having problems with the printer and their current IT provider has said that because the driver is so crap, the printer needs to be on the same network (Sigh!)
Also this network has a number of statically assigned devices.
I must admit that as I write this, I'm not sure this is going to solve the problem. So ridiculous!
Thanks guys though for the info.
Regards
Michael Knill
On 14/10/20, 12:22 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote:
A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ?
A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox).
So, if for some reason you want to add 192.168.99.1/32<http://192.168.99.1/32> to eth1, simply:
--
ip addr add 192.168.99.1/32<http://192.168.99.1/32> dev eth1
--
If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label:
--
ip addr add 192.168.99.1/32<http://192.168.99.1/32> dev eth1 label eth1:1
--
Lonnie
> On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...<mailto:li...@mk...>> wrote:
>
>
>
>> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...<mailto:mic...@ip...>>:
>>
>> Hi Group
>>
>> Is there a way to add a secondary LAN IP Address with Astlinux?
>> I cant see an INTIP_ALIAS variable!
>>
>> Regards
>> Michael Knill
>
> https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/
>
> You have to add this to rc.elocal to make it persistent.
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...<mailto:Ast...@li...>
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
>
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
|
|
From: Michael K. <mic...@ip...> - 2020-10-14 21:49:43
|
Yes they are (well VLAN interfaces on the same Physical interface anyway).
Thanks David/Lonnie for the info here. It seems to be exactly what I am looking for.
I will let you know how I go.
Regards
Michael Knill
From: David Kerr <da...@ke...>
Reply to: AstLinux List <ast...@li...>
Date: Thursday, 15 October 2020 at 8:45 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Secondary IP Address
Are the two subnets connected to two different LAN interfaces on Astlinux? If so look at the avahi service and in avahi-daemon.conf add this...
[reflector]
enable-reflector=yes
reflect-ipv=no
#reflect-filters=_printer._tcp.local,_ipp._tcp.local,_pdl-datastream._tcp.local,_airplay._tcp.local,_raop._tcp.local,_googlecast._tcp.local,_googlerpc._tcp.local,_googlezone._tcp.local,_hap._tcp.local,_appletv-v2._tcp.local,_homekit._tcp.local
I have commented out the reflect-filter line above which means "reflect" all bonjour traffic across interfaces, if you uncomment then only those listed services will be reflected between LANs... above I have a typical set.
You can view what services are broadcast on your LANs with the "Discovery" app available in both the iOS and MacOS app stores (I don't know about Android but presume there is a version for that too). Beware that clients cache what they find so enabling/disabling or changing the reflect-filter in avahi does not necessarily get immediately picked up by the clients.
And... if you want a client on one LAN to talk to a printer on another LAN then firewall rules need to permit the traffic.
David
On Wed, Oct 14, 2020 at 5:11 PM Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
Would it be worth turning on UPnP do you think?
Regards
Michael Knill
On 15/10/20, 8:08 am, "Michael Knill" <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Guys
It seems that this was working fine when the Cisco router was in place and only stopped when the Astlinux box was put in place.
Looking at the Cisco router I do see 'ip forward-protocol nd' with nd being the Neighbor Discovery Protocol which may have been the reason it worked.
Is it possible to set this up on Astlinux?
Regards
Michael Knill
On 14/10/20, 7:34 am, "Michael Knill" <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Lonnie. Good question.
I have a site with two customers sharing the same network and telephony infrastructure.
The data network is segregated for the two customers but there is a single shared printer on one of the networks.
The customer on the other network is having problems with the printer and their current IT provider has said that because the driver is so crap, the printer needs to be on the same network (Sigh!)
Also this network has a number of statically assigned devices.
I must admit that as I write this, I'm not sure this is going to solve the problem. So ridiculous!
Thanks guys though for the info.
Regards
Michael Knill
On 14/10/20, 12:22 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote:
A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ?
A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox).
So, if for some reason you want to add 192.168.99.1/32<http://192.168.99.1/32> to eth1, simply:
--
ip addr add 192.168.99.1/32<http://192.168.99.1/32> dev eth1
--
If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label:
--
ip addr add 192.168.99.1/32<http://192.168.99.1/32> dev eth1 label eth1:1
--
Lonnie
> On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...<mailto:li...@mk...>> wrote:
>
>
>
>> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...<mailto:mic...@ip...>>:
>>
>> Hi Group
>>
>> Is there a way to add a secondary LAN IP Address with Astlinux?
>> I cant see an INTIP_ALIAS variable!
>>
>> Regards
>> Michael Knill
>
> https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/
>
> You have to add this to rc.elocal to make it persistent.
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...<mailto:Ast...@li...>
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
>
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
_______________________________________________
Astlinux-users mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>.
|
|
From: David K. <da...@ke...> - 2020-10-14 21:45:02
|
Are the two subnets connected to two different LAN interfaces on Astlinux? If so look at the avahi service and in avahi-daemon.conf add this... [reflector] enable-reflector=yes reflect-ipv=no #reflect-filters=_printer._tcp.local,_ipp._tcp.local,_pdl-datastream._tcp.local,_airplay._tcp.local,_raop._tcp.local,_googlecast._tcp.local,_googlerpc._tcp.local,_googlezone._tcp.local,_hap._tcp.local,_appletv-v2._tcp.local,_homekit._tcp.local I have commented out the reflect-filter line above which means "reflect" all bonjour traffic across interfaces, if you uncomment then only those listed services will be reflected between LANs... above I have a typical set. You can view what services are broadcast on your LANs with the "Discovery" app available in both the iOS and MacOS app stores (I don't know about Android but presume there is a version for that too). Beware that clients cache what they find so enabling/disabling or changing the reflect-filter in avahi does not necessarily get immediately picked up by the clients. And... if you want a client on one LAN to talk to a printer on another LAN then firewall rules need to permit the traffic. David On Wed, Oct 14, 2020 at 5:11 PM Michael Knill < mic...@ip...> wrote: > Would it be worth turning on UPnP do you think? > > Regards > Michael Knill > > On 15/10/20, 8:08 am, "Michael Knill" <mic...@ip...> > wrote: > > Hi Guys > > It seems that this was working fine when the Cisco router was in place > and only stopped when the Astlinux box was put in place. > Looking at the Cisco router I do see 'ip forward-protocol nd' with nd > being the Neighbor Discovery Protocol which may have been the reason it > worked. > Is it possible to set this up on Astlinux? > > Regards > Michael Knill > > On 14/10/20, 7:34 am, "Michael Knill" < > mic...@ip...> wrote: > > Hi Lonnie. Good question. > > I have a site with two customers sharing the same network and > telephony infrastructure. > The data network is segregated for the two customers but there is > a single shared printer on one of the networks. > The customer on the other network is having problems with the > printer and their current IT provider has said that because the driver is > so crap, the printer needs to be on the same network (Sigh!) > Also this network has a number of statically assigned devices. > > I must admit that as I write this, I'm not sure this is going to > solve the problem. So ridiculous! > > Thanks guys though for the info. > > Regards > Michael Knill > > On 14/10/20, 12:22 am, "Lonnie Abelbeck" < > li...@lo...> wrote: > > A question to Michael Knill, can you help us understand why > you want to add an additional IP to a LAN ? > > A comment, when adding network commands to rc.elocal, it is > best to use 'ip' (iproute2) instead of 'ifconfig' (busybox). > > So, if for some reason you want to add 192.168.99.1/32 to > eth1, simply: > -- > ip addr add 192.168.99.1/32 dev eth1 > -- > > If for some reason you want it to look like an old-style > ifconfig 'alias' with label 'eth1:1', add the label: > -- > ip addr add 192.168.99.1/32 dev eth1 label eth1:1 > -- > > Lonnie > > > > > > On Oct 13, 2020, at 3:03 AM, Michael Keuter < > li...@mk...> wrote: > > > > > > > >> Am 13.10.2020 um 06:16 schrieb Michael Knill < > mic...@ip...>: > >> > >> Hi Group > >> > >> Is there a way to add a secondary LAN IP Address with > Astlinux? > >> I cant see an INTIP_ALIAS variable! > >> > >> Regards > >> Michael Knill > > > > > https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/ > > > > You have to add this to rc.elocal to make it persistent. > > > > Michael > > > > http://www.mksolutions.info > > > > > > > > > > > > _______________________________________________ > > Astlinux-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via > PayPal to pa...@kr.... > > > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via > PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal > to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2020-10-14 21:42:20
|
> On Oct 14, 2020, at 4:10 PM, Michael Knill <mic...@ip...> wrote: > > Would it be worth turning on UPnP do you think? No, no, no. As for the Cisco command, I did a quick search and 'ip forward-protocol nd' was old in 2010 -- Forwards Network Disk (ND) packets. This protocol is used by older diskless Sun workstations. -- seems unrelated to a printer issue. It may be possible that mDNS (avahi) might solve this printer issue, together with firewall rules: mDNS/DNS-SD Service Discovery (Bonjour) https://doc.astlinux-project.org/userdoc:tt_avahi_mdns As the docs show, David Kerr has used this. It may be possible that just firewall rules might be enough if the printer is referenced via a static IP address. Lonnie > > Regards > Michael Knill > > On 15/10/20, 8:08 am, "Michael Knill" <mic...@ip...> wrote: > > Hi Guys > > It seems that this was working fine when the Cisco router was in place and only stopped when the Astlinux box was put in place. > Looking at the Cisco router I do see 'ip forward-protocol nd' with nd being the Neighbor Discovery Protocol which may have been the reason it worked. > Is it possible to set this up on Astlinux? > > Regards > Michael Knill > > On 14/10/20, 7:34 am, "Michael Knill" <mic...@ip...> wrote: > > Hi Lonnie. Good question. > > I have a site with two customers sharing the same network and telephony infrastructure. > The data network is segregated for the two customers but there is a single shared printer on one of the networks. > The customer on the other network is having problems with the printer and their current IT provider has said that because the driver is so crap, the printer needs to be on the same network (Sigh!) > Also this network has a number of statically assigned devices. > > I must admit that as I write this, I'm not sure this is going to solve the problem. So ridiculous! > > Thanks guys though for the info. > > Regards > Michael Knill > > On 14/10/20, 12:22 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ? > > A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox). > > So, if for some reason you want to add 192.168.99.1/32 to eth1, simply: > -- > ip addr add 192.168.99.1/32 dev eth1 > -- > > If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label: > -- > ip addr add 192.168.99.1/32 dev eth1 label eth1:1 > -- > > Lonnie > > > > >> On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...> wrote: >> >> >> >>> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...>: >>> >>> Hi Group >>> >>> Is there a way to add a secondary LAN IP Address with Astlinux? >>> I cant see an INTIP_ALIAS variable! >>> >>> Regards >>> Michael Knill >> >> https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/ >> >> You have to add this to rc.elocal to make it persistent. >> >> Michael >> >> http://www.mksolutions.info >> >> >> >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >> >> > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2020-10-14 21:10:56
|
Would it be worth turning on UPnP do you think?
Regards
Michael Knill
On 15/10/20, 8:08 am, "Michael Knill" <mic...@ip...> wrote:
Hi Guys
It seems that this was working fine when the Cisco router was in place and only stopped when the Astlinux box was put in place.
Looking at the Cisco router I do see 'ip forward-protocol nd' with nd being the Neighbor Discovery Protocol which may have been the reason it worked.
Is it possible to set this up on Astlinux?
Regards
Michael Knill
On 14/10/20, 7:34 am, "Michael Knill" <mic...@ip...> wrote:
Hi Lonnie. Good question.
I have a site with two customers sharing the same network and telephony infrastructure.
The data network is segregated for the two customers but there is a single shared printer on one of the networks.
The customer on the other network is having problems with the printer and their current IT provider has said that because the driver is so crap, the printer needs to be on the same network (Sigh!)
Also this network has a number of statically assigned devices.
I must admit that as I write this, I'm not sure this is going to solve the problem. So ridiculous!
Thanks guys though for the info.
Regards
Michael Knill
On 14/10/20, 12:22 am, "Lonnie Abelbeck" <li...@lo...> wrote:
A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ?
A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox).
So, if for some reason you want to add 192.168.99.1/32 to eth1, simply:
--
ip addr add 192.168.99.1/32 dev eth1
--
If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label:
--
ip addr add 192.168.99.1/32 dev eth1 label eth1:1
--
Lonnie
> On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...> wrote:
>
>
>
>> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...>:
>>
>> Hi Group
>>
>> Is there a way to add a secondary LAN IP Address with Astlinux?
>> I cant see an INTIP_ALIAS variable!
>>
>> Regards
>> Michael Knill
>
> https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/
>
> You have to add this to rc.elocal to make it persistent.
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Michael K. <mic...@ip...> - 2020-10-14 21:07:25
|
Hi Guys
It seems that this was working fine when the Cisco router was in place and only stopped when the Astlinux box was put in place.
Looking at the Cisco router I do see 'ip forward-protocol nd' with nd being the Neighbor Discovery Protocol which may have been the reason it worked.
Is it possible to set this up on Astlinux?
Regards
Michael Knill
On 14/10/20, 7:34 am, "Michael Knill" <mic...@ip...> wrote:
Hi Lonnie. Good question.
I have a site with two customers sharing the same network and telephony infrastructure.
The data network is segregated for the two customers but there is a single shared printer on one of the networks.
The customer on the other network is having problems with the printer and their current IT provider has said that because the driver is so crap, the printer needs to be on the same network (Sigh!)
Also this network has a number of statically assigned devices.
I must admit that as I write this, I'm not sure this is going to solve the problem. So ridiculous!
Thanks guys though for the info.
Regards
Michael Knill
On 14/10/20, 12:22 am, "Lonnie Abelbeck" <li...@lo...> wrote:
A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ?
A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox).
So, if for some reason you want to add 192.168.99.1/32 to eth1, simply:
--
ip addr add 192.168.99.1/32 dev eth1
--
If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label:
--
ip addr add 192.168.99.1/32 dev eth1 label eth1:1
--
Lonnie
> On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...> wrote:
>
>
>
>> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...>:
>>
>> Hi Group
>>
>> Is there a way to add a secondary LAN IP Address with Astlinux?
>> I cant see an INTIP_ALIAS variable!
>>
>> Regards
>> Michael Knill
>
> https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/
>
> You have to add this to rc.elocal to make it persistent.
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2020-10-14 16:44:08
|
Hi David, Since you build your own images, look at the first 'for' line in /etc/profile, add your /mnt/kd/bin path to: https://github.com/astlinux-project/astlinux/blob/master/project/astlinux/target_skeleton/etc/profile For those who don't build their own images, or just want to keep things 'clean', look at the end of the same /etc/profile where ~/.bashrc gets sourced if it exists. For a 'root' user you need a persistent /mnt/kd/root directory or use rc.local to populate /root/.bashrc with -- export PATH="/mnt/kd/bin:$PATH" -- Lonnie > On Oct 14, 2020, at 8:31 AM, David Kerr <da...@ke...> wrote: > > Can anyone tell me how I can set the PATH environment variable to include an additional directory? I tried adding... > export PATH="/mnt/kd/bin:$PATH" > to rc.local but it is not working. > > Thanks > David > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: David K. <da...@ke...> - 2020-10-14 16:22:44
|
Can anyone tell me how I can set the PATH environment variable to include an additional directory? I tried adding... export PATH="/mnt/kd/bin:$PATH" to rc.local but it is not working. Thanks David |
|
From: Michael K. <mic...@ip...> - 2020-10-13 20:33:51
|
Hi Lonnie. Good question.
I have a site with two customers sharing the same network and telephony infrastructure.
The data network is segregated for the two customers but there is a single shared printer on one of the networks.
The customer on the other network is having problems with the printer and their current IT provider has said that because the driver is so crap, the printer needs to be on the same network (Sigh!)
Also this network has a number of statically assigned devices.
I must admit that as I write this, I'm not sure this is going to solve the problem. So ridiculous!
Thanks guys though for the info.
Regards
Michael Knill
On 14/10/20, 12:22 am, "Lonnie Abelbeck" <li...@lo...> wrote:
A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ?
A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox).
So, if for some reason you want to add 192.168.99.1/32 to eth1, simply:
--
ip addr add 192.168.99.1/32 dev eth1
--
If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label:
--
ip addr add 192.168.99.1/32 dev eth1 label eth1:1
--
Lonnie
> On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...> wrote:
>
>
>
>> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...>:
>>
>> Hi Group
>>
>> Is there a way to add a secondary LAN IP Address with Astlinux?
>> I cant see an INTIP_ALIAS variable!
>>
>> Regards
>> Michael Knill
>
> https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/
>
> You have to add this to rc.elocal to make it persistent.
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2020-10-13 13:21:31
|
A question to Michael Knill, can you help us understand why you want to add an additional IP to a LAN ? A comment, when adding network commands to rc.elocal, it is best to use 'ip' (iproute2) instead of 'ifconfig' (busybox). So, if for some reason you want to add 192.168.99.1/32 to eth1, simply: -- ip addr add 192.168.99.1/32 dev eth1 -- If for some reason you want it to look like an old-style ifconfig 'alias' with label 'eth1:1', add the label: -- ip addr add 192.168.99.1/32 dev eth1 label eth1:1 -- Lonnie > On Oct 13, 2020, at 3:03 AM, Michael Keuter <li...@mk...> wrote: > > > >> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...>: >> >> Hi Group >> >> Is there a way to add a secondary LAN IP Address with Astlinux? >> I cant see an INTIP_ALIAS variable! >> >> Regards >> Michael Knill > > https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/ > > You have to add this to rc.elocal to make it persistent. > > Michael > > http://www.mksolutions.info > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > |
|
From: Michael K. <li...@mk...> - 2020-10-13 08:04:10
|
> Am 13.10.2020 um 06:16 schrieb Michael Knill <mic...@ip...>: > > Hi Group > > Is there a way to add a secondary LAN IP Address with Astlinux? > I cant see an INTIP_ALIAS variable! > > Regards > Michael Knill https://www.cyberciti.biz/faq/linux-creating-or-adding-new-network-alias-to-a-network-card-nic/ You have to add this to rc.elocal to make it persistent. Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2020-10-13 04:17:03
|
Hi Group Is there a way to add a secondary LAN IP Address with Astlinux? I cant see an INTIP_ALIAS variable! Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2020-10-11 21:05:45
|
Thanks Michael for closing the loop on this issue. Additionally, AstLinux 1.4.0 should solve this issue without needing the workaround. Lonnie > On Oct 11, 2020, at 2:34 PM, Michael Knill <mic...@ip...> wrote: > > PS just letting the group know that I haven’t had any lockups since adding this workaround which is certainly a relief. > Thanks all for your help. > > Regards > Michael Knill > > On 21/9/20, 8:34 am, "Michael Knill" <mic...@ip...> wrote: > > Thanks Lonnie for all your help. > > Regards > Michael Knill > > On 21/9/20, 7:37 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > Considering this is a very obscure kernel bug that has been around for a long time, and AstLinux 1.4.x will have it fixed ... I personally would not get carried away implementing the workaround. > > BTW, the PHYETH_DISABLE_OFFLOAD workaround only applies to physical ethernet NICs. > > You understand the situation, so do what you think is best. > > Lonnie > > > > >> On Sep 20, 2020, at 3:45 PM, Michael Knill <mic...@ip...> wrote: >> >> Thanks Lonnie >> >> One last question; could I just blanket add this to all my systems or are there any that will certainly not be affected by this bug e.g. VM or virtual NIC? >> The plan is to have this command active by default and commented out if desired. >> >> Regards >> Michael Knill >> >> On 20/9/20, 9:58 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >> >>> Do you think I should remove PHYETH_DISABLE_OFFLOAD and try a BIOS upgrade to see if it fixes the problem? >> >> No ... first make sure setting PHYETH_DISABLE_OFFLOAD solves the issue with your DLS provider and your APU2s. >> >> After that, AstLinux 1.4.0 will be the solution without setting PHYETH_DISABLE_OFFLOAD . >> >> Ideally, you could test a 1.4-pre-release on an APU2 with the new DLS provider to make certain we have identified the issue. >> https://www.astlinux-project.org/dev.html >> >> Lonnie >> >> >>> On Sep 20, 2020, at 5:24 AM, Michael Knill <mic...@ip...> wrote: >>> >>> Yes my BIOS is quite old: >>> 3999-IPCBuild-CM1 kd # dmesg | grep DMI >>> [ 0.000000] DMI: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 >>> >>> Funny as it's a pretty new box. >>> >>> Do you think I should remove PHYETH_DISABLE_OFFLOAD and try a BIOS upgrade to see if it fixes the problem? >>> I don't think I will for existing sites as a BIOS upgrade looks pretty hard to do and I assume cannot be done remotely. >>> >>> Regards >>> Michael Knill >>> >>> On 20/9/20, 12:18 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> Ahhh, very good ... looks like we are on to something. >>> >>> Add it to one/some of your APU2s and let us know how it goes. >>> >>> As far as my Qotom Q190G4N, I initially had to set PHYETH_DISABLE_OFFLOAD to keep it from locking-up with sustained high network traffic but then switched the RAM SO-DIMM with another brand and did not need PHYETH_DISABLE_OFFLOAD anymore. My comments probably got you started adding PHYETH_DISABLE_OFFLOAD. >>> >>> This is a very obscure kernel bug, as such it never got back-ported to Linux 3.16.x . >>> >>> For the APU2, the BIOS could play a role in how it initializes the NICs and whether this kernel bug is triggered. >>> >>> Lonnie >>> >>> >>> >>>> On Sep 19, 2020, at 7:49 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Awesome thanks Lonnie. >>>> Yes its all making sense now. I already have this directive in my template against the Qotom Q190G4U for some reason (should I have?) >>>> I have two Qotoms connected to the problem provider, one had this directive set already and has not failed and one did not (I forgot to change when I changed hardware) which fails. >>>> All my APU's don't have this set so all have problems with this provider. >>>> >>>> I'm thinking we have finally solved this issue. >>>> Thanks so much for your help >>>> >>>> Regards >>>> Michael Knill >>>> >>>> On 20/9/20, 9:29 am, "Lonnie Abelbeck" <li...@lo...> wrote: >>>> >>>> I would try this first >>>> -- >>>> PHYETH_DISABLE_OFFLOAD="tso gso gro" >>>> -- >>>> and see if it fixes the problem. >>>> >>>> If by chance it does fix it, then it would not be needed in AstLinux 1.4.x. >>>> >>>> The PHYETH_DISABLE_OFFLOAD settings disable some of the "offload" features of the NICs in an effort to work around this (somewhat obscure) kernel bug. >>>> >>>> It all kind of makes sense that a particular provider is fragmenting packets in ways others do not, and hits this kernel bug. >>>> >>>> The PHYETH_DISABLE_OFFLOAD setting above is very "safe", only drawback is it slightly reduces network performance near the 1 Gbps level. >>>> >>>> BTW, if traffic shaping is enabled this PHYETH_DISABLE_OFFLOAD setting is already applied to external ethernet NIC(s). >>>> >>>> Lonnie >>>> >>>> >>>> >>>>> On Sep 19, 2020, at 6:09 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Awesome thanks Lonnie. >>>>> >>>>> I will give it a try although I have no idea what it does! >>>>> I assume I can remove this when I go to Astlinux 1.4? >>>>> >>>>> Regards >>>>> Michael Knill >>>>> >>>>> Sent from my iPhone so please excuse my brevity. >>>>> >>>>>> On 19 Sep 2020, at 11:56 pm, Lonnie Abelbeck <li...@lo...> wrote: >>>>>> >>>>>> >>>>>> Hi Michael, >>>>>> >>>>>> Great info! >>>>>> >>>>>> Try this in your user.conf, and reboot. >>>>>> -- >>>>>> PHYETH_DISABLE_OFFLOAD="tso gso gro" >>>>>> -- >>>>>> >>>>>> If my hunch is correct, this kernel fix added in 4.1.17 may be related ... >>>>>> >>>>>> net: preserve IP control block during GSO segmentation >>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/include/linux/skbuff.h?h=v4.1.17&id=abefd1b4087b9b5e83e7b4e7689f8b8e3cb2899c >>>>>> >>>>>> Lonnie >>>>>> >>>>>> >>>>>> >>>>>>> On Sep 18, 2020, at 10:56 PM, Michael Knill <mic...@ip...> wrote: >>>>>>> >>>>>>> Yay some progress on this problem. >>>>>>> >>>>>>> I had my 4th site lock up yesterday. It was a site I moved from one location to another. There were no changes to the Astlinux box at all other than PPPoE credentials but after a couple of hours it locked up. So realistically the only change is the internet provider which is a new one that I am trialling and is the same provider as two of the other sites that are failing. >>>>>>> >>>>>>> As we are also using this provider in our home office, I set up another box this morning and connected the serial port not expecting anything to happen but it locked up and we captured it. Yay! It is attached. >>>>>>> >>>>>>> I'm hoping it will help the resolution of this problem. >>>>>>> >>>>>>> Regards >>>>>>> Michael Knill >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Astlinux-users mailing list >>>>>> Ast...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>>>>> >>>>>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >>>>>> <APU Crash.log> >>>>> _______________________________________________ >>>>> Astlinux-users mailing list >>>>> Ast...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>>>> >>>>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >>>> >>>> >>>> >>>> _______________________________________________ >>>> Astlinux-users mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>>> >>>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >>>> >>>> >>>> _______________________________________________ >>>> Astlinux-users mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>>> >>>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >>> >>> >>> >>> _______________________________________________ >>> Astlinux-users mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >>> >>> >>> _______________________________________________ >>> Astlinux-users mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >> >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2020-10-11 19:43:06
|
Interestingly one of our machines in the office was doing it. Havent bothered to find out why yet.
Decided that I would push up the default conntrack size as per below anyway.
Thanks for all your help guys.
Regards
Michael Knill
On 7/10/20, 5:07 pm, "Michael Knill" <mic...@ip...> wrote:
Thanks guys
Not sure why this would be happening on this system as I have much busier ones that are fine but I will have a look next time it happens.
Regards
Michael Knill
On 7/10/20, 12:23 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
Thanks Darrick,
If you have a very busy (network) system, you can set in your user.conf
--
CONNTRACK=65536
--
or some higher power of 2 ... that will survive a reboot. Though higher values will use more RAM.
BTW, CONNTRACK is a firewall variable.
Lonnie
> On Oct 6, 2020, at 7:19 PM, darricklegacy <dha...@dj...> wrote:
>
> Hi Michael,
>
> I have seen this error on our system from time to time. If you are on a relatively busy network, you could exceed the 16384 value potentially. You can echo a larger value to that setting in /proc/sys/net but it will not survive a reboot.
>
> If you have a relatively small network, Lonnie is on the right track (pun intented). You can check what's in the table by parsing /proc/net and looking at ip_conntrack.
>
> Darrick
>
> On 10/6/20, 5:38 PM, "Lonnie Abelbeck" <li...@lo...> wrote:
>
> Hi Michael,
>
> I have never personally witnessed this error, but I am aware it can happen if the conntrack state table is full.
>
> By default CONNTRACK=16384 which sets the conntrack state table size.
>
> View the number states:
> System tab -> Firewall States
> --
>
> NNN Total Firewall States
> --
>
> Look to see what public TCP or UDP ports are exposed and see if someone might be probing them.
>
> Possibly you have a BitTorrent running internally ? That can create a lot of states.
>
> If you really have a super busy system there is some tuning you can do, but I would look to see if you have some publicly exposed ports that can be firewalled better.
>
> Lonnie
>
>
>
>
>
>> On Oct 6, 2020, at 4:50 PM, Michael Knill <mic...@ip...> wrote:
>>
>> Hi Group
>>
>> For the second morning in a row, my office system has been pretty much unusable with the following in the logs:
>>
>> user.warn kernel: nf_conntrack: table full, dropping packet
>>
>> Is this a DoS attack?
>> Things are fine once rebooted. Surely this wouldn't be the case with a DoS attack?
>>
>> Where should I test next?
>>
>> Thanks all.
>>
>> Regards
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
63 messages has been excluded from this view by a project administrator.
