Probably not your issue but a mistake I made once caused a similar issue.
The ISP provided a /29, the outside interface was configured with all
5 available addresses (4 as aliases). Which could allow me to use
different addresses for different purposes. But in one case I had
natted, in pf, to the interface itself instead of just one address.
Everything worked except for one banking site. Drove me nuts but when
I finally natted to just one address the site worked fine.
My guess is that the round-robin nat nature caused secondary
connections to use a different outbound IP address than the primary
connection creating the failure.
Note to self: don't do this.

Chris

On Wed, Sep 14, 2022 at 10:06 AM Otto Moerbeek <[email protected]> wrote:
>
> On Wed, Sep 14, 2022 at 05:48:22AM -0700, Alton Shaw wrote:
>
> > Thank you Stuart for your suggestion. I tried logging in using the add-on
> > /User-Agent Switcher and Manager/ within Firefox set to Windows 10/Edge but
> > I've received the same response.
> >
> > Note that I've been able to login in to another banking website with
> > OpenBSD/Firefox without issues.
> >
> > I don't know anything about anything but could it be something related to
> > bgpd?  I would like to test the previous version but don't know how to
> > rollback a package without blowing up my system.
>
> Nah, its very unlikely it's bgpd.
>
> What you can try is logging in after clearing cookies and site storage
> or using a private browser window. I have seen browsers adding a
> zillion cookies and generating requests headers that are very big and
> won't make it past the companies firewall unharmed.
>
> Another posibility is that the login process needs third party
> cookies. Try playing with the firefox settings in that area: should be
> under "Privacy and Security".
>
>         -Otto
>
> >
> >
> > On 2022-09-14 01:47, Stuart Henderson wrote:
> > > On 2022/09/13 08:36, Alton Shaw wrote:
> > > >      I am no longer able to log into to my bank using Firefox, 
> > > > Firefox-ESR,
> > > > or Chromium on OpenBSD.  After entering my username and password the
> > > > website responds "/We’re currently having technical issue Please try 
> > > > again
> > > > later./"  The bank's technical supports says that they are not even 
> > > > seeing
> > > > a login attempt at their end. This only happens with the OpenBSD as I am
> > > > able to successfully login on both Windows 10 and Debian regardless of
> > > > browser.  As recently as September 3rd this was not a problem.  I
> > > > regularly run syspatch and pkg_add -u.  Per /var/syspatch the following
> > > > packages were updated on September 3rd: xserver, cron, bgpd, and zlib.
> > > Some websites are fussy about the client user-agent string and won't
> > > let you login (or sometimes access the site at all) with the default ones
> > > used by OpenBSD packages. Try a user-agent switcher extension with various
> > > options (usually best to change the presented OS and not the type of
> > > browser) and see if it helps.
> > >
>

Reply via email to