I've got a box with one Intel 82574L based ethernet port and one 82579LM
based ethernet port. One will be hooked up to a 50Mbps wan link, the
other trunked at gigabit speed to a cisco switch (both routing the wan
link, routing some internal vlans, and providing some services).
Both the 82574L and
I've got a supermicro X9SCL-F board with ipmi support, and I'm trying to
use it for the serial console. It shows up as a third com port. After
booting the latest install cd, I run the usual "stty com2 115200" and
"set tty com2", and then boot. The kernel messages show up fine, and
then the output j
ses com2 as a console fine but then userland
borks it. The SOL port works fine as a console when I boot linux on the
box, so either there's an openbsd bug with it or linux must be
implementing some workaround for a problem.
Thanks anyway...
> Paul B. Henson(hen...@acm.org) on 2013.11.2
On Sun, Nov 24, 2013 at 04:13:27PM -0500, Jiri B wrote:
> Supermicro IPMI is crap. Use normal serial console and add a power strip
> which you can manage via ethernet to poweroff/power cycle the server.
Well, I can't say it's the greatest implementation ever, but arguably it
doesn't seem much wor
On 11/24/2013 2:00 PM, Theo de Raadt wrote:
Well, I can't say it's the greatest implementation ever, but arguably it
doesn't seem much worse than on my Sun or IBM servers.
[...]
You just cannot compare this to what Sun did, by (almost always) using
a seperate ethernet port. Probably still crap
On Sun, Nov 24, 2013 at 12:16:52AM -0800, Paul B. Henson wrote:
> com2 at isa0 port 0x3e8/8 irq 5: ns16550a, 16 byte fifo
> com2: console
> [...]
> root on rd0a swap on rd0b dump on rd0b
> erase ^?, werase
>
> Every time, it wedges up at this spot. The console still works
On Sun, Nov 24, 2013 at 04:10:23PM -0800, Paul B. Henson wrote:
>
> I suppose the installer kernel could be fixed the same way, but at least
> for this initial install it's not worth it, I'll just install with the
> kvm head, fix the installed kernel, and then go serial from
On Mon, Nov 25, 2013 at 12:09:33PM +, Stuart Henderson wrote:
> > How come freebsd dynamically detects the correct irq, but openbsd has it
> > hardcoded?
>
> linux and freebsd kernels use acpi to configure isa serial ports, openbsd
> uses static allocations.
Ah, ok; now that I know what's g
On Mon, Nov 25, 2013 at 04:30:36PM +0400, Alexander Pakhomov wrote:
> Both should not load CPU a lot. But that doesn't mean they wouldn't.
> Write here if notice intense interrupts CPU load. My OpenBSD 5.4 amd64
> laptop fail to handle 2 MB/s wifi due to some drivers issues (they
> load CPU up to
On Tue, Jan 21, 2014 at 03:51:23PM -0800, Gabriel Kuri wrote:
> I am running obsd 5.4 as my NAT router. I decided to setup a second obsd
> box and run carp between the two for the external NATed interface (facing
> the ISP). After I setup everything and switched pf to NAT using the address
> on the
I'm trying to get a L2TP VPN working using npppd; I think I'm most of the
way there but packets just aren't quite flowing. I'm not sure why, but I
think I might be missing something or misunderstanding something with pf.
I've got ipsec=YES and isakmpd_flags="-K" in rc.conf.local, and
/etc/ipsec.c
> From: YASUOKA Masahiko
> Sent: Wednesday, February 26, 2014 8:46 PM
> "set skip on pppx0" needs to be improved because npppd may use pppx1,
> pppx2 ...
Once I've got things working, I'm probably going to want to have more
explicit rules rather than skipping; if I understand correctly I can just
> From: YASUOKA Masahiko
> Sent: Thursday, February 27, 2014 5:44 PM
> >> In L2TP/IPsec, "transport mode" IPsec is used instead of tunnel mode.
> >> This means enc(4) is not used. And de-capsulated L2TP packets are
> >> received on the same interface which receives IPsec packet.
> >
> > Hmm, that'
According to the npppd.conf man page:
pool-address address-range | address-mask [for dynamic | static]
Specify the IP address space that is pooled for this IPCP
setting. The address space can be specified by address-range
(e.g. 192.168.0.2-192.168.0.254
After getting the basic functionality of an L2TP VPN working with npppd,
I tried turning on the l2tp-require-ipsec option, as that seemed
desirable; I don't really want an l2tp session set up that's not
encapsulated in ipsec.
However, with that option on, the attempted VPN connection doesn't seem
I'm currently setting up an L2TP VPN with npppd. I've got the VPN piece
working, and can send packets between the client and the openbsd box
running the vpn. However, I'm currently using ospfd for routing between
the rest of the network and the openbsd box, and it doesn't seem to be
pushing routes
On Fri, Feb 28, 2014 at 01:54:13PM -0800, Jeff Goettsch wrote:
> That's a known bug:
>
> http://www.openbsd.org/cgi-bin/man.cgi?query=npppd&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html#end
Ah, I see; I hadn't actually looked at the npppd man page, only the
npppd.conf man page
On Sat, Mar 01, 2014 at 11:23:01AM +0900, YASUOKA Masahiko wrote:
> I'm not sure whether it works. Can you try it by static route?
A static route on the network on the other side of the openbsd box? I'm
sure that would work; when I try to ping a box out in the network from
the vpn client, I can
On Sat, Mar 01, 2014 at 12:56:16PM +0900, YASUOKA Masahiko wrote:
> Currently the parser needs to surrounding the address-mask with double
> quote like below:
>
> pool-address "10.128.120.0/24"
Ah, yes; that's much better:
2014-03-01 15:59:13:INFO: ipcp=IPCP pool dyn_pool=[10.128.120.0/24]
poo
On Sat, Mar 01, 2014 at 01:48:06PM +0900, YASUOKA Masahiko wrote:
> > on the other side? Right now it looks like the client is setting a
> > route to 10.0.0.0/8 across the tunnel, that should actually be
> > 10.128.0.0/16, would setting the netmask in npppd-users fix that remote
> > route? Can I se
On Sat, Mar 01, 2014 at 07:41:10PM +0900, YASUOKA Masahiko wrote:
> I could repeat the problem. ospfd seems not to be able to use routes
> set by npppd. The problem seems to be come from pppx(4)'s behavior of
> its link state.
>
> Using tun(4) instead of pppx(4) avoid the problem.
If I switch
> From: YASUOKA Masahiko
> Sent: Wednesday, March 05, 2014 1:48 AM
>
> "framed-ip-netmask" in npppd-user to set the netmask of the route to
> the PPP link. But it is not to set the client netmask (on iPhone).
>
> AFAIK to set the client netmask, DHCP inform can be used.
Hmm, I thought the VPN cl
> From: YASUOKA Masahiko
> Sent: Wednesday, March 05, 2014 3:20 AM
>
> % ospfctl show fib | grep 128
> *56 10.128.120.0/24 127.0.0.1
> *56 10.128.120.213/3210.0.0.1
Interesting, not only does it show a /24 route, it looks like it has it
marked as valid. Is this with
I set up an L2TP VPN with npppd recently using pppx, and other than some
routing issues with ospfd it works great. I'm trying to add a second VPN
connection, but that doesn't seem to work using pppx.
With this config:
interface pppx0 address 10.128.120.1 ipcp IPCP_admin
interface pppx1 address 10
ces that showed up in ifconfig for the clients, which I guess led
me to believe I didn't have to do anything special to use pppx1 in the
npppd config.
Thanks, and sorry for the noise.
On Wed, Mar 19, 2014 at 02:29:35PM -0700, Paul B. Henson wrote:
> I set up an L2TP VPN with npppd recentl
After successfully setting up an L2TP VPN with npppd and pppx, I tried
to add a second VPN subnet with a different authentication base. I was
working remotely, and after starting npppd in debug mode:
bash-4.2# npppd -d
2014-03-19 14:41:50:NOTICE: Starting npppd pid=32407 version=5.0.0
2014-03-19 1
On Thu, Mar 20, 2014 at 10:22:51AM +0900, YASUOKA Masahiko wrote:
> pppx will be fixed.
Great :). This is a known bug then? Should I just keep an eye on the
changelog for mention of pppx changes to tell when it's safe to try
again?
> You can use tun(4) instead if you want to use multiple interfa
> From: YASUOKA Masahiko
> Sent: Wednesday, March 19, 2014 9:44 PM
>
> > Should I just keep an eye on the changelog for mention of pppx
> > changes to tell when it's safe to try again?
>
> Sorry I cannot understand the point of this question.
Sorry to be confusing; I switched to tun because of th
> From: Jonathan Gray
> Sent: Thursday, March 20, 2014 3:36 AM
>
> The following diff prevents the panic here:
Interesting, given the XXX, it seems somebody was already a little
suspicious of this section :).
>From a cursory glance, it seems pppx_dev_lookup is supposed to return data
about a part
I'm upgrading to OpenBSD 7 and I was happy to see the new support for
/etc/bsd.re-config to allow modified kernels to be automatically
rebuilt. However, one of the changes I need to make is updating the IRQ
on com2, as my bios assigns it a non-standard value 8-/.
I can't figure out how to do that?
Thanks much for the info guys; something to look forward to in 7.1 :).
On 11/30/2021 4:17 AM, Stuart Henderson wrote:
On 2021-11-30, Paul de Weerd wrote:
On Tue, Nov 30, 2021 at 08:46:34AM -, Stuart Henderson wrote:
| On 2021-11-29, Paul B. Henson wrote:
| > I'm upgrading to O
On Tue, Nov 30, 2021 at 11:13:26PM -0500, Nick Holland wrote:
> hint: snapshots that do what you need beat releases that don't.
Granted; or I could just apply that patch to the 7.0 stable source and
copy in the new config binary :). I doubt if there will be any binary patches
that would overwrite
how the booting kernel would know about that yet.
Anyway, just to clarify my understanding, is it expected in 5.0 to be
able to boot softraid root without a custom kernel or using -a? If so,
what am I doing wrong?
Thanks...
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu
metadata and dynamically figure out the root happened after the 5.0
freeze.
Something to look forward to in 5.1 :). Thanks again...
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | hen...@csupomona.edu
California State Polytechni
patches...
#ifdef DIAGNOSTIC
if (scd->sc_in_rep_size != cc)
printf("%s: bad input length %d != %d\n",USBDEVNAME(sc->sc_dev),
scd->sc_in_rep_size, cc);
#endif
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu
SCSI0 5/cdrom
removable
umass1 at uhub1 port 2 configuration 1 interface 0
umass1: American Megatrends Inc. Virtual Floppy Device, rev 1.10/1.00, addr
3
umass1: using UFI over CBI with CCI
scsibus2 at umass1: 2 targets
sd1 at scsibus2 targ 1 lun 0: SCSI0 0/direct
removable
sd1: drive offline
dkcsum: sd0 matches BIOS drive 0x80
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | [EMAIL PROTECTED]
California State Polytechnic University | Pomona CA 91768
nBSD serial console and using BIOS redirection, that didn't work. I also
tried disabling BIOS redirection and configuring explicit OpenBSD serial
console support, but still nothing showed up when I connected to the remote
management console interface. The only thing I haven't tried is physica
0 at sk0 phy 0: XaQti Corp. XMAC II Gigabit PHY, rev. 2
Any suggestions on reducing the interrupt load to the previous levels?
Thanks...
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | [EMAIL PROTECTED]
California State Polytech
I'm trying to setup ospf on a trunk interface. I've had it configured
and working fine on a regular interface for quite some time, and now am
trying to add another neighbor on a trunk interface, and it just shows
the interface as down:
# ospfctl show i
Interface AddressState HelloTi
On Sun, Jun 03, 2012 at 11:04:53AM +, Stuart Henderson wrote:
> Did you create the trunk interface *before* or *after* starting ospfd?
> I have seen ospfd get the wrong state on interfaces created after startup,
> iirc sometimes "ifconfig down+up" helps, sometimes you need to restart
> ospfd.
On Sun, Jun 03, 2012 at 05:12:19PM +0200, Claudio Jeker wrote:
> Is this after a reload of the config or does this also happen when you
> restart ospfd?
It was after a config reload, after following Stuart's suggestion to
restart ospfd everything's working great :). Maybe it would be worth a
note
y try a -CURRENT snapshot, before reporting problems
> you see in 4.6.
After updating the bios I booted the latest 4.6-current kernel, which still
had the problem, so I submitted a bug.
Thanks much for the help...
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating
101 - 142 of 142 matches
Mail list logo