Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 1157 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Installing XG1 on ProtecLi FW2B Loses Keyboard

JimmyJoeBob

I have a case open with ProtectLi (12073) on this, but they assert (and I'm starting to agree) that what I'm experiencing is in the XG code.

There are two problems:
1. The installer assigns the NICs backwards. LAN = WAN and vice versa. This isn't a deal-breaker, but for anyone trying to use XG1 on the FW2B, it could be confusing, and it's definitely a time-waster. Yes, once the UI is available, this can be changed, but again - time wasted.

2. In the physical console (HDMI video / USB keyboard), the keyboard is properly detected and used *during primary installation*, but once the XG code boots normally, the USB keyboard is completely ignored (even numlock, capslock indicators don't change state when the related key is pressed). I use an IOGear 2-port-DVI-D KVM, MS ergo 4000 keyboard, and HDMI-DVI adapter for the FW2B. Connecting the keyboard directly to any of the 4 USB2 or 2 USB3 ports on the FW2B produces *exactly* the same results - nonfunctional keyboard.

Thx,
Jim



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    the installer assigns interfaces which you can change during installation. If you want NIC 1 to be LAN do not connect NIC2 until you have completed the installation. Using a 4 port J1900 based box I did not have any of those issues. Must admit it has  VGA interface and 2 usb ports. The keyboard always works regardless of whether it is the USB2 or USB 3 port it is connected to.

    I have never had great experiences using KVMs on UTM or XG because the port goes to sleep when the KVM isn't i use or changed. Sometimes requiring a reboot to get the keyboard to talk again.

    Ian

    In fact I am not sure why you want to connect a KVM to an XG because after the initial installation you can connect to the console through SSH or the GUI.

  • 0 in reply to rfcat_vk

    Sadly, that's not how it worked. Regardless whether I had the WAN port connected or not, the installer always assigned the ports backwards.

    Like I said - it doesn't matter if I use the KVM or connect to the HDMI / USB ports directly - the keyboard is completely ignored after XG boots up.
    I use a KVM so that I can switch to the physical console if need be without having to give my monitor a reacharound just to move cables.
    The FW2B mounted behind my primary monitor on the supplied VESA mounting hardware.

    The folks at ProtectLi were kind enough to send me a replacement unit, but XG behaved the same on that one.
    I have to admit that until this installation, my XG was always running as a VM, so I never saw any problems like these.

    Thx,
    Jim

Reply
  • 0 in reply to rfcat_vk

    Sadly, that's not how it worked. Regardless whether I had the WAN port connected or not, the installer always assigned the ports backwards.

    Like I said - it doesn't matter if I use the KVM or connect to the HDMI / USB ports directly - the keyboard is completely ignored after XG boots up.
    I use a KVM so that I can switch to the physical console if need be without having to give my monitor a reacharound just to move cables.
    The FW2B mounted behind my primary monitor on the supplied VESA mounting hardware.

    The folks at ProtectLi were kind enough to send me a replacement unit, but XG behaved the same on that one.
    I have to admit that until this installation, my XG was always running as a VM, so I never saw any problems like these.

    Thx,
    Jim

Children
  • 0 in reply to JimmyJoeBob

    Hi Jimmy,

    I have installed XG on a number of different hardware and VM versions. The only failure was on an ASrock MB because they were doing sting thing with the high performance timer.

    I would suggest that the MB BIOS of your device is a bit strange, but if you have been able to instal it and get it going then all is good.

    Ian