Ignore my last email sorry. It worked fine when the driver was configured
correctly.
Regards
Michael Knill
From: Michael Knill
Reply to: AstLinux List
Date: Thursday, 15 October 2020 at 11:04 am
To: AstLinux List
Subject: Re: [Astlinux-users] Secondary IP Address
Hi All
It certainly works
List
Date: Thursday, 15 October 2020 at 8:50 am
To: AstLinux List
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
am
To: AstLinux List
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
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.
> On Oct 14, 2020, at 4:10 PM, Michael Knill
> 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 S
Would it be worth turning on UPnP do you think?
Regards
Michael Knill
On 15/10/20, 8:08 am, "Michael Knill"
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
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 poss
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 printe
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
> Am 13.10.2020 um 06:16 schrieb Michael Knill
> :
>
> 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-
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
___
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux
ly-To: AstLinux List
Date: Monday, 24 June 2019 at 8:16 am
To: AstLinux List
Subject: Re: [Astlinux-users] Secondary IP Address on LAN interface
How does this work?
If my INTIF has both 192.168.168.1 and 192.168.168.254 then I assume that any
device on the local LAN could chose to connect to eith
Hi David,
Good thoughts, I don't see a reason you would want to do this except for legacy
migration or such.
But your network understanding of this topic seems correct to me.
> What about a request initiated from Astlinux to an internal LAN device... say
> ping 192.168.168.99 from Astlinux...
How does this work?
If my INTIF has both 192.168.168.1 and 192.168.168.254 then I assume that
any device on the local LAN could chose to connect to either of these IP
addresses and all would be well. So any device on the LAN could ping to
either .1 or .254 and get a reply. Am I correct in thinkin
> Is this ok?
Yes, that should work.
Lonnie
> On Jun 23, 2019, at 4:36 PM, Michael Knill
> wrote:
>
> Sorry Lonnie
> It would be another address in the same subnet as the address on the
> interface.
> E.g. 192.168.168.254/24 and adding via ip a command 192.168.168.1/24.
>
> Is this ok?
>
Sorry Lonnie
It would be another address in the same subnet as the address on the interface.
E.g. 192.168.168.254/24 and adding via ip a command 192.168.168.1/24.
Is this ok?
Regards
Michael Knill
On 24/6/19, 7:30 am, "Lonnie Abelbeck" wrote:
> No it would be another address in the /24 ra
> No it would be another address in the /24 range on the interface.
You might have firewall issues doing that.
Best practice is to have only one subnet off an interface.
If a /24 won't do possibly a /22 will. The 'netcalc' command in AstLinux can
be helpful.
Lonnie
> On Jun 23, 2019, at 3:
Thanks Lonnie
No it would be another address in the /24 range on the interface.
Regards
Michael Knill
On 23/6/19, 11:49 pm, "Lonnie Abelbeck" wrote:
> On Jun 23, 2019, at 12:35 AM, Michael Knill
wrote:
>
> Hi Group
>
> I know there is EXTIP_ALIAS for WAN inte
> On Jun 23, 2019, at 12:35 AM, Michael Knill
> wrote:
>
> Hi Group
>
> I know there is EXTIP_ALIAS for WAN interfaces but how would I put on a
> secondary IP Address for a LAN interface?
> Do I need to use ‘ip addr add’ in rc.elocal?
Hi Michael,
Yes, rc.elocal would be the way to do that
Hi Group
I know there is EXTIP_ALIAS for WAN interfaces but how would I put on a
secondary IP Address for a LAN interface?
Do I need to use ‘ip addr add’ in rc.elocal?
Thnaks
Regards
Michael Knill
___
Astlinux-users mailing list
Astlinux-users@lists.s
20 matches
Mail list logo
