On 12.10.21 11:27, Oleksandr Kryvulia wrote:
04.10.21 10:33, Volodymyr Kostyrko пишет:
Hello.
First of all, I came here not to agitate for any change, I want to
understand how my configuration is inefficient and how I can do that
better.
I have two outgoing interfaces, if0 and if0. Those are
Hello.
First of all, I came here not to agitate for any change, I want to
understand how my configuration is inefficient and how I can do that better.
I have two outgoing interfaces, if0 and if0. Those are different
internet providers, I even get ipv6 through second one, and that's nice.
I w
0k, I've finally get my hands to this stuff...
I have a host machine (i386) with many i386 clients and one sparc64 all
configured the same way. All i386 client work just fine, while sparc64
one refuses to do so.
This is a config sample:
out0:
new -n -i ng0 SG PPPoE
set auth authname negative
Can't make use of mpd on sparc64. After going up link goes down almost
instantly.
On sparc64(client):
Aug 29 16:32:04 blade mpd: [pppoe0] IFACE: Up event
Aug 29 16:32:10 blade mpd: [pppoe0] PPPoE connection closed
Aug 29 16:32:10 blade mpd: [pppoe0] device: DOWN event in state UP
Aug 29 16:32:10
Hi all.
Roaming recently through whois database i've stumbled upon the
following ip-address notations:
194.134.086.040
212.223.085.184
212.129.243.040
194.134.086.32
... etc ...
Giving this addresses to inet_aton results in exceptions, or address
misspelling due to:
[man inet
