Subject: RARE user and assistance email list
List archive
- From: mc36 <>
- To: Luis Bernal <>, Ana Hermosilla <>
- Cc: "" <>
- Subject: Re: [RARE-users] Freertr at umu
- Date: Fri, 22 Jul 2022 19:53:32 +0200
XD :)
so i see the point, and fully agree with you about the fridays and the
changes... and hopefully we're not in a hurry afterall...
but, on the other hand, i cannot push out a fatal image as the whole
publishing process is fully freerouter hosted, and, an image
first have to be able to serve my homenet (which like a smaller isp than a
homenet), then it have to function out in the
wild at a real isp network (the upgrade servers are hosted at niif, part of
their core, as a pe node) to be able to finally
reach anybody... and finally, right here, we're talking about only + lines in
the commits, so no old functionality removed,
just something new added, and, that new stuff also covered in the 2nd commit
with tests, so, long story short, just type in
the commands on monday or when you feel convenient...
and, anytime if you're a fear that something could go wrong, do it in a
reload in 5 / conf t / xxx / end / reload cancel / write...
alternatively, you can do simply "conf rollback", which, if you lose the
session, will auto-revert without reloading...
(btw the reload in the above is a warm reload, which is some seconds even
with the asic forwarding in place...)
br,
cs
On 7/22/22 19:14, Luis Bernal wrote:
GRRRRRRR
El 22/7/22 a las 19:13, Ana Hermosilla escribi :
okey, NOW he's on cc -.-"
El 22/07/2022 a las 19:13, Ana Hermosilla escribi :
oh, damn, I'm out of the office right now and the connection to the freertr
is throught itself, so I don't know if that's a good idea.
Anyway, we have a written rule of no production changes on Friday afternoons.
Too much vietnam flashes. However, I'll test it monday morning :)
PS: I put n0p in cc, I'm sure he has something to say about changing the
production router on fridays hahaha
El 22/07/2022 a las 17:41, mc36 escribi :
hi,
while the tests ran, i googled you ( :) ) so i bother you further with the
tests i just added:
https://github.com/rare-freertr/freeRtr/commit/16dbd552b306ceb21e29b8a961db57e2f10802ce
you can run it yourself by issuing the following:
wget freertr.org/rtr.zip
unzip rtr.zip
cd src
./c.sh
./tw.sh conn-dhcp04
telnet 127.0.0.1 20001
telnet 127.0.0.1 20002
telnet 127.0.0.1 20003
the first telnet will give you r1's console, where you could debug server
dhcp4/6 or show ipv4/6 arp/neigh eth1
the rest will give you r2 and r3, where you can debug client dhcp4/6 or the
arp/neigh again...
the thing to spot here is that r2 is unable to acquire the address whereas r3
succeeds...
and exactly that is what the test goes for in the final pings and their
expected success rates... :)
ps: the new knob will be out around 19pm today, right before the weekly pub
round of me... :)
br,
cs
On 7/22/22 17:11, mc36 wrote:
hi,
you're welcome.... :)
btw im done with the coding, now i'll add the tests covering the new
functionality...
https://github.com/rare-freertr/freeRtr/commit/6aaafeadcb9d2f4008e49cd84d79120cb3574d03
i wont bother you with that further, the new knob to look for is "forbidden <mac>"
under "server dhcp4/6 xxx"
please note all the following:
- it does not affect the current bindings, just the new ones, asked after
configuring the knob...
- in case of ipv6, it only works in the managed address allocation mode...
- in other words, a node will always have a link local address, and the above
commit does not stop the node from asking the on-link prefix with
icmpv6... (slaac)
br,
cs
On 7/22/22 16:36, Ana Hermosilla wrote:
great!!
thank you so much =)
El 22/07/2022 a las 16:28, mc36 escribi :
hi,
i'm sadly informing you that it's still not possible to do, but, i've just
started adding the feature...
normally it'll arrive by today or at least by tomorrow autoupgrade right to
your box... i'll keep you posted...
br,
cs
On 7/22/22 16:24, Ana Hermosilla wrote:
Hi Csaba,
I'm part of the Computer Science Team at umu (I worked w/ Jordi) and as Luis
is out of the office, he gave me your address to ask you something :)
I'm trying to exclude a mac address from the dhcp server (i.e.. so that the dhcp doesn't serve its requests), but I'm not sure about how could I do that (or if it's supported by freertr).
Is this possible?
Thank you so much.
- Re: [RARE-users] Freertr at umu, mc36, 07/22/2022
- Message not available
- Re: [RARE-users] Freertr at umu, mc36, 07/22/2022
- Re: [RARE-users] Freertr at umu, mc36, 07/22/2022
- Message not available
- Message not available
- Message not available
- Re: [RARE-users] Freertr at umu, mc36, 07/22/2022
- Re: [RARE-users] Freertr at umu, Luis Bernal, 07/23/2022
- Message not available
- Message not available
- Message not available
- Re: [RARE-users] Freertr at umu, mc36, 07/22/2022
- Re: [RARE-users] Freertr at umu, mc36, 07/22/2022
- Message not available
Archive powered by MHonArc 2.6.19.