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

Strange problem with 17.0.3 MR3 on intel j1900

Hi all,

Finally got some free time to install SFOS for my home network so i was thinking that a 4 port j1900 with 32SSD will be more than sufficient (several home pc and mobile devices)

Install went smooth...

Connected LAN2 (WAN) to network (another router with DHCP, so double NAT is here)

Connected PC to LAN 1 (LAN) - ip is default 172.16.16.16

After 30 seconds i get internet access (which means that traffic is going with the default settings) on the PC but i cannot access https://172.16.16.16:4444

If i use the console to debug the interfaces i see that IP on the interfaces are fine...

Amy idea what is the problem and maybe where can i find the MR2 iso in order to try to install...

Before trying to install sfos - the same micro PC was running pfsense for a quick test and all of the hardware was fine ...

Please advice any ideas....

This thread was automatically locked due to age.

Parents

0 rfcat_vk over 7 years ago

Hi,

Not sure what happened, post vanished.

Did you enable DHCP as part of your initial setup? Sounds to me like your PC does not have an IP in the range 172.16.16.0/24. Try manually assigning a 172.16.16 address and do not forget to add a DNS.

Ian
Cancel
Vote Up 0 Vote Down

Cancel
0 Vladislav Bidikov over 7 years ago in reply to rfcat_vk

Hi,

dhcp was running fine without any setup (just after the first reboot)

Also tried setting ip to 172.16.16.100 / mask 255.255.255.0, no gateway and standard dns (they are always static on my lan adapter) - the result is the same...

Since i did the first install without ethernet cables connected, did a second reinstall with cables connected... result is the same...

Not sure where to start to debug... did a test install on a vmware... got to the initial web install right away... completely clueless...
Cancel
Vote Up 0 Vote Down

Cancel
0 rfcat_vk over 7 years ago in reply to Vladislav Bidikov

Hi,

I don't think it is a processor issue otherwise you would not be able to access the internet. Can you ping your PC from the console of the XG?

Ian
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 rfcat_vk over 7 years ago in reply to Vladislav Bidikov

Hi,

I don't think it is a processor issue otherwise you would not be able to access the internet. Can you ping your PC from the console of the XG?

Ian
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Vladislav Bidikov over 7 years ago in reply to rfcat_vk

Yes.. ping also works...

Everything works except the SSL on port 4444...

And interesting enough when debugging with telnet - looks like the FW closes the connection 4444 od it's not listening on port 4444...

I'm just puzzled ...
Cancel
Vote Up 0 Vote Down

Cancel
0 rfcat_vk over 7 years ago in reply to Vladislav Bidikov

Hi,

hopefully Flo will come along and provide some assistance.

Ian
Cancel
Vote Up 0 Vote Down

Cancel
0 Aditya Patel over 7 years ago in reply to Vladislav Bidikov

Hi Vladislav ,

Could you assign 80GB of disk space and try again ?Also if you are able to access the console , try enabling the command "console>system appliance_access enable" and try to access from any interface reachable by the host machine.
Cancel
Vote Up 0 Vote Down

Cancel
0 Vladislav Bidikov over 7 years ago in reply to Aditya Patel

Well the mini pc came with 32GB SSD :(

Never had the idea that maybe that could be the problem... since it's a hardware device - attaching a new hdd could be an interesting process...

Can you verify that 80GB Disk is the minimal ???
Cancel
Vote Up 0 Vote Down

Cancel
0 Aditya Patel over 7 years ago in reply to Vladislav Bidikov

Hi Vladislav ,

It is a recommended requirement, the minimum is 20GB but that could have changed so need to verify it. Are you able to access Console of the XG after setup ?
Cancel
Vote Up 0 Vote Down

Cancel
0 Vladislav Bidikov over 7 years ago in reply to Aditya Patel

On the VGA i see the standard console (with attached usb keyboard)...

That is the second way i was able to verify that both interfaces are up (lan has default ip 172.16.16.16, wan has DHCP), DNS is ok and internet connectivity seems ok...

The first way was that if i connect to LAN i get dhcp ip (from range 172.16.16.16) and if i config ip manually also i get ping reply...

I'm looking into the possibility to use a bigger hdd temporally to verify this new moment with a 32GB hdd that is maybe too small ...
Cancel
Vote Up 0 Vote Down

Cancel
0 Vladislav Bidikov over 7 years ago in reply to Aditya Patel

Just to update...

i'm still waiting for a bigger msata SSD to arrive...

In the mean time, i tried the recommendation to activate device management from the console with out any effect...

Also, i went into advanced shell and did a "netstat -nlp" and did not see any process listening on port 4444, while i see almost all other ports fine (23,22, 25, 8009, etc ...)

Anything else i can try while i wait for a bigger HDD ???
Cancel
Vote Up 0 Vote Down

Cancel
0 Ian Rogers over 7 years ago in reply to Vladislav Bidikov

I had a similar issue when I first setup XG on my J1900.

There was only 1 ip address that the admin would initially respond to one IP address, IIRC I needed to set it to 172.16.16.1 for it to work for me.

Once I had done initial setup and moved the main LAN network to the IP addresses I used, I can access from any LAN ip.
Cancel
Vote Up 0 Vote Down

Cancel
0 Vladislav Bidikov over 7 years ago in reply to Ian Rogers

Well what still bugs me i why there i no process listening on port 4444 TCP ...

Even if it's something to do with a firewall ACL port on the XG itself must be in listening state...

Tried a VM install with 40GB HDD - works like expected...
Cancel
Vote Up 0 Vote Down

Cancel