Forums

Resolved
0 votes
Hi again all,

So I have an issue I did a clean install of community on a mini itx system with a mini pci-e wifi on board similar to a laptop/m.2 port and it works fine other than I can not set up any of it's IP information. I can set it up to broadcast and it can even give out internet in "standalone (no firewall)" mode but the second I throw it into gateway mode it loses all ability to retain DHCP even if I try and force the adapter to assign DHCP. but I think it's because of how it's not showing up properly in "IP Settings"


iw list:
iw list
Wiphy phy0
max # scan SSIDs: 20
max scan IEs length: 425 bytes
max # sched scan SSIDs: 20
max # match sets: 11
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x11ee
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT Max RX data rate: 300 Mbps
HT TX/RX MCS rate indexes supported: 0-15
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (22.0 dBm)
* 2417 MHz [2] (22.0 dBm)
* 2422 MHz [3] (22.0 dBm)
* 2427 MHz [4] (22.0 dBm)
* 2432 MHz [5] (22.0 dBm)
* 2437 MHz [6] (22.0 dBm)
* 2442 MHz [7] (22.0 dBm)
* 2447 MHz [8] (22.0 dBm)
* 2452 MHz [9] (22.0 dBm)
* 2457 MHz [10] (22.0 dBm)
* 2462 MHz [11] (22.0 dBm)
* 2467 MHz [12] (22.0 dBm) (no IR)
* 2472 MHz [13] (22.0 dBm) (no IR)
Band 2:
Capabilities: 0x11ee
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT Max RX data rate: 300 Mbps
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x038071a0):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
TX STBC
SU Beamformee
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180 MHz [36] (22.0 dBm) (no IR)
* 5200 MHz [40] (22.0 dBm) (no IR)
* 5220 MHz [44] (22.0 dBm) (no IR)
* 5240 MHz [48] (22.0 dBm) (no IR)
* 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5720 MHz [144] (22.0 dBm) (no IR, radar detection)
DFS state: usable (for 2707 sec)
DFS CAC time: 0 ms
* 5745 MHz [149] (22.0 dBm) (no IR)
* 5765 MHz [153] (22.0 dBm) (no IR)
* 5785 MHz [157] (22.0 dBm) (no IR)
* 5805 MHz [161] (22.0 dBm) (no IR)
* 5825 MHz [165] (22.0 dBm) (no IR)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* start_sched_scan
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
* add_tx_ts
* Unknown command (121)
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 20 patterns of 16-128 bytes,
maximum packet offset 0 bytes
* can do GTK rekeying
* wake up on GTK rekey failure
* wake up on EAP identity request
* wake up on 4-way handshake
* wake up on rfkill release
* wake up on network detection, up to 11 match sets
* wake up on TCP connection
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 3, #channels <= 2
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports per-vif TX power setting
P2P GO supports CT window setting
P2P GO supports opportunistic powersave setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports static SMPS
Device supports dynamic SMPS
Device supports WMM-AC admission (TSPECs)
Device supports configuring vdev MAC-addr on create.


ip a:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet 11.11.11.11/24 brd 11.11.11.255 scope global enp1s0
valid_lft forever preferred_lft forever
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet 11.11.11.11/24 brd 11.11.11.255 scope global dynamic enp2s0
valid_lft 39742sec preferred_lft 39742sec
inet6 ::1/64 scope link
valid_lft forever preferred_lft forever
4: wlp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq master br0 state DOWN group default qlen 1000
link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet 11.11.11.11/24 brd 11.11.1.255 scope global wlp4s0
valid_lft forever preferred_lft forever
6: br0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff


lshw -class network

*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:01:00.0
logical name: enp1s0
version: 06
serial: ff:ff:ff:ff:ff:ff
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp aui bnc mii fibre 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl_nic/rtl8168e-2.fw ip=10.20.1.1 latency=0 link=no multicast=yes port=MII
resources: irq:38 ioport:e000(size=256) memory:fea00000-fea00fff memory:d0900000-d0903fff
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: enp2s0
version: 06
serial: ff:ff:ff:ff:ff:ff
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp aui bnc mii fibre 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 ip=10.2.3.136 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
resources: irq:40 ioport:d000(size=256) memory:fe900000-fe900fff memory:d0800000-d0803fff
*-network DISABLED
description: Wireless interface
product: Wireless 7260
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlp4s0
version: bb
serial: ff:ff:ff:ff:ff:ff
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.10.0-1062.9.1.el7.x86_64 firmware=17.3216344376.0 ip=10.20.2.1 latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: irq:54 memory:fe800000-fe801fff
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: br0
serial: ff:ff:ff:ff:ff:ff
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=no multicast=yes


lspci | egrep -i --color 'network|ethernet':

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
04:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)



so as you can see it should be fine I just don't get why it's not listed in ip settings.
Wednesday, January 08 2020, 05:42 AM
Share this post:
Responses (7)
  • Accepted Answer

    Wednesday, January 08 2020, 08:45 AM - #Permalink
    Resolved
    0 votes
    .... because it was removed from the IP Settings a long while ago. I was not happy about it but was not able to do anything about it.

    There is light at the end of the tunnel but we don't seem to be able to reach the end. A community developer has added back some of the functionality in the version of app-network in clearos-updates-testing. You can install it with a:
    yum update app-network --enablerepo=clearos-updates-testing
    there are some known issues. You cannot set up an External DHCP or Static VLAN properly, and the Speed Test icon does not appear against these external VLAN interfaces. I am not aware of any other issues.

    I have a proposed patch for the external VLAN settings, but have not tried to fix the Speed Test icon. Unfortunately I cannot get the app reviewed.

    If you do install it you will get the basic configuration of Static/DHCP and External/LAN/HotLAN/DMZ. You will have to do all the WiFi configuration manually with wpa-supplicant for external connections. For a LAN AP, there is app-wireless which is basic and gives you 802.11g functionality. After that you have to dig into hostapd. There is also a thread by Todd lewis somewhere where he can set up multiple AP's through the webconfig.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 08 2020, 05:43 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    .... because it was removed from the IP Settings a long while ago. I was not happy about it but was not able to do anything about it.

    There is light at the end of the tunnel but we don't seem to be able to reach the end. A community developer has added back some of the functionality in the version of app-network in clearos-updates-testing. You can install it with a:
    yum update app-network --enablerepo=clearos-updates-testing
    there are some known issues. You cannot set up an External DHCP or Static VLAN properly, and the Speed Test icon does not appear against these external VLAN interfaces. I am not aware of any other issues.

    I have a proposed patch for the external VLAN settings, but have not tried to fix the Speed Test icon. Unfortunately I cannot get the app reviewed.

    If you do install it you will get the basic configuration of Static/DHCP and External/LAN/HotLAN/DMZ. You will have to do all the WiFi configuration manually with wpa-supplicant for external connections. For a LAN AP, there is app-wireless which is basic and gives you 802.11g functionality. After that you have to dig into hostapd. There is also a thread by Todd lewis somewhere where he can set up multiple AP's through the webconfig.


    yes I am trying to set up a LAN WiFi AP but with out DHCP or anything it just does not seem to work at all once the server is put back in to gateway mode.

    so I have to install an experiment to reenable wifi in IP Settings so I can use the wireless ap that is being developed.... that seems ass backwards... lets add wireless but take all ability to control ip addresses for it.


    this is a new server as the old one had wifi ap working fine but they upgraded their hardware and wanted a fresh install since new motherboard and cpu. and now I can not seem to get WiFi app working on LAN side with gateway functionality enabled as there is absolutely no way to add a subnet to the interface.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 08 2020, 06:51 PM - #Permalink
    Resolved
    0 votes
    If you want to configure your WiFi IP settings through the Webconfig, then you have to install the app from updates-testing. Otherwise you can set up the ifcfg-wlp4s0 file manually. the current app-wireless should work in 802.11g mode but it is a command line install. There is not one in development. The third party one has been taken as far as Todd was going to take it. There is an issue sith the start/stop button but otherwise it works. Unfortunately there is no rpm for it you you have to piece it together from Todd's thread. At some point I may see if I can dix the start/stop, but I don't know what is needed to take the app on board and we have little development resource at the moment.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 08 2020, 07:46 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    If you want to configure your WiFi IP settings through the Webconfig, then you have to install the app from updates-testing. Otherwise you can set up the ifcfg-wlp4s0 file manually. the current app-wireless should work in 802.11g mode but it is a command line install. There is not one in development. The third party one has been taken as far as Todd was going to take it. There is an issue sith the start/stop button but otherwise it works. Unfortunately there is no rpm for it you you have to piece it together from Todd's thread. At some point I may see if I can dix the start/stop, but I don't know what is needed to take the app on board and we have little development resource at the moment.


    wait so are you saying ClearOS is ditching WiFi support even though we're now entering the age of WiFi with WiFi 6..... even though they never even finished it...

    there has to be something viable to allow me to use 5Ghz and N and everything as a gateway OS clearly ClearOS doesn't want the community since community usually means Home and Small business and both of those places would like WiFi AP's and considering that consumer grade gateways are garbage and require you to run extra power lines and Ethernet for an extremely bulky device that will just be acting as a WiFi AP seems silly.

    Edit:

    So since I updated the network app, it added the WiFi interface thank you, but now the WiFi interface is no longer usable as the AP Interface... what??? https://i.imgur.com/l4j23Zu.png

    P.S. This domain is running dog slow for some reason.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, January 08 2020, 10:25 PM - #Permalink
    Resolved
    0 votes
    I'm afraid clearos.com is not performing well at the moment. They are trying to look at it, but no success yet.

    WRT WiFi on ClearOS, one thing worth bearing in mind is that a server is rarely in a good place for good signal coverage and the recommended route has always been to use a LAN connected WAP which is much easier to put in a good location.

    The app-wireless that has always been there and still is only has minimal functionality with 802.11g support only. For 802.11n or ac support you've always had to go under the hood and fiddle with hostapd. Ditto for dual radio support. I would like to see Todd's app released into ClearOS but I don't know the mechanism to do that. I thing I have rpm's for it somewhere. I'll try and look them out for you tomorrow.

    Where is your screenshot of an empty dropdown from?
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 09 2020, 12:39 AM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:
    WRT WiFi on ClearOS, one thing worth bearing in mind is that a server is rarely in a good place for good signal coverage and the recommended route has always been to use a LAN connected WAP which is much easier to put in a good location.


    While I can agree there with certain circumstances, mileage does very and the NFP LGBT Org I am working for runs a small night club out of a bar and I have their public network set up using consumer grade routers, however I wanted their staff network to be managed by the clearos system itself as friends I have set that up for at their homes have loved how amazing the signal and strength are for it, and being the staff wifi network is merely for the POS systems and a couple board member cell phones I figured that would be the most logical setup at I installed the gateway above everything which would give it the best coverage for the pos systems :P.

    I also run it from my home and with a nice antenna with a decent cable length it's actually really nice running the WiFi from clearos directly instead of those consumer grade routers with 64MB of RAM.

    Nick Howitt wrote:
    The app-wireless that has always been there and still is only has minimal functionality with 802.11g support only. For 802.11n or ac support you've always had to go under the hood and fiddle with hostapd. Ditto for dual radio support. I would like to see Todd's app released into ClearOS but I don't know the mechanism to do that. I thing I have rpm's for it somewhere. I'll try and look them out for you tomorrow.

    Oh I didn't realize I could actually enable N and AC in hostapd i'll have to dig into that more, I'm still very vanilla with unix systems, I have been toying for over a decade with them on and off but I am definitely not 1337 :P.

    Nick Howitt wrote:
    Where is your screenshot of an empty dropdown from?

    Sorry it's Wireless Access Point menu, ever since I did the update to testing it took my card out of there, it's still listed in hostapd but i can no longer connect to the wifi.
    https://i.imgur.com/tG6KVoW.png
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, January 09 2020, 09:17 AM - #Permalink
    Resolved
    0 votes
    I've stuck the packages I compiled from Todd's code on my website. You need https://www.howitts.co.uk/clearos/ClearOS_7.x/app-wireless-ap-1.0.0-1.devel.noarch.rpm and https://www.howitts.co.uk/clearos/ClearOS_7.x/app-wireless-ap-core-1.0.0-1.devel.noarch.rpm. Download them to somewhere then, from the command line wherever yuo downloaded them to, do:
    yum install app-wireless-ap*
    You may need to remove app-wireless and app-wireless-core first.

    I have no idea why the wireless interface is not showing up with app-wireless. I gave up on wireless on my server as it is in the attic at one end of the house. Useless for coverage. I do have a development box and I may get a chance to look at it but I'm not sure.
    The reply is currently minimized Show
Your Reply