Logging all web trafic





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I have fresh Ubuntu 18.04 with all updates. There are two network cards. One for internet connection. The second is to distribute this Internet over a local network.



It is necessary for my to keep all logs of visited sites. From which ip in the local network to which Internet address did someone visit and when (date and time). It is necessary that it works in the background all the time. And automatically started after server reboot. Ideally, it should be logs, automatically shared by day and archived as syslogs.










share|improve this question























  • Too difficult and there is a far more simple method: use the log from the router.

    – Rinzwind
    Apr 4 at 21:01











  • @Rinzwind netfilter/iptables - it is difficuls and bad too?

    – n.osennij
    Apr 4 at 21:07











  • Thing is: if someone has physical access he/she can do -anything- by just rebooting into a live session. But they can not access the router if you keep the password for that safe.

    – Rinzwind
    Apr 4 at 21:15











  • @Rinzwind , physical - it is not important. Only local network

    – n.osennij
    Apr 5 at 7:06











  • What are on about? "physical - it is not important" and "Only local network" are unrelated. This "It is necessary for my to keep all logs of visited sites." is only 100% reliable to do from the log of your router. All other methods you can work around your logging if you know what to do.

    – Rinzwind
    Apr 5 at 7:28


















0















I have fresh Ubuntu 18.04 with all updates. There are two network cards. One for internet connection. The second is to distribute this Internet over a local network.



It is necessary for my to keep all logs of visited sites. From which ip in the local network to which Internet address did someone visit and when (date and time). It is necessary that it works in the background all the time. And automatically started after server reboot. Ideally, it should be logs, automatically shared by day and archived as syslogs.










share|improve this question























  • Too difficult and there is a far more simple method: use the log from the router.

    – Rinzwind
    Apr 4 at 21:01











  • @Rinzwind netfilter/iptables - it is difficuls and bad too?

    – n.osennij
    Apr 4 at 21:07











  • Thing is: if someone has physical access he/she can do -anything- by just rebooting into a live session. But they can not access the router if you keep the password for that safe.

    – Rinzwind
    Apr 4 at 21:15











  • @Rinzwind , physical - it is not important. Only local network

    – n.osennij
    Apr 5 at 7:06











  • What are on about? "physical - it is not important" and "Only local network" are unrelated. This "It is necessary for my to keep all logs of visited sites." is only 100% reliable to do from the log of your router. All other methods you can work around your logging if you know what to do.

    – Rinzwind
    Apr 5 at 7:28














0












0








0








I have fresh Ubuntu 18.04 with all updates. There are two network cards. One for internet connection. The second is to distribute this Internet over a local network.



It is necessary for my to keep all logs of visited sites. From which ip in the local network to which Internet address did someone visit and when (date and time). It is necessary that it works in the background all the time. And automatically started after server reboot. Ideally, it should be logs, automatically shared by day and archived as syslogs.










share|improve this question














I have fresh Ubuntu 18.04 with all updates. There are two network cards. One for internet connection. The second is to distribute this Internet over a local network.



It is necessary for my to keep all logs of visited sites. From which ip in the local network to which Internet address did someone visit and when (date and time). It is necessary that it works in the background all the time. And automatically started after server reboot. Ideally, it should be logs, automatically shared by day and archived as syslogs.







networking server 18.04






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 4 at 19:46









n.osennijn.osennij

1063




1063













  • Too difficult and there is a far more simple method: use the log from the router.

    – Rinzwind
    Apr 4 at 21:01











  • @Rinzwind netfilter/iptables - it is difficuls and bad too?

    – n.osennij
    Apr 4 at 21:07











  • Thing is: if someone has physical access he/she can do -anything- by just rebooting into a live session. But they can not access the router if you keep the password for that safe.

    – Rinzwind
    Apr 4 at 21:15











  • @Rinzwind , physical - it is not important. Only local network

    – n.osennij
    Apr 5 at 7:06











  • What are on about? "physical - it is not important" and "Only local network" are unrelated. This "It is necessary for my to keep all logs of visited sites." is only 100% reliable to do from the log of your router. All other methods you can work around your logging if you know what to do.

    – Rinzwind
    Apr 5 at 7:28



















  • Too difficult and there is a far more simple method: use the log from the router.

    – Rinzwind
    Apr 4 at 21:01











  • @Rinzwind netfilter/iptables - it is difficuls and bad too?

    – n.osennij
    Apr 4 at 21:07











  • Thing is: if someone has physical access he/she can do -anything- by just rebooting into a live session. But they can not access the router if you keep the password for that safe.

    – Rinzwind
    Apr 4 at 21:15











  • @Rinzwind , physical - it is not important. Only local network

    – n.osennij
    Apr 5 at 7:06











  • What are on about? "physical - it is not important" and "Only local network" are unrelated. This "It is necessary for my to keep all logs of visited sites." is only 100% reliable to do from the log of your router. All other methods you can work around your logging if you know what to do.

    – Rinzwind
    Apr 5 at 7:28

















Too difficult and there is a far more simple method: use the log from the router.

– Rinzwind
Apr 4 at 21:01





Too difficult and there is a far more simple method: use the log from the router.

– Rinzwind
Apr 4 at 21:01













@Rinzwind netfilter/iptables - it is difficuls and bad too?

– n.osennij
Apr 4 at 21:07





@Rinzwind netfilter/iptables - it is difficuls and bad too?

– n.osennij
Apr 4 at 21:07













Thing is: if someone has physical access he/she can do -anything- by just rebooting into a live session. But they can not access the router if you keep the password for that safe.

– Rinzwind
Apr 4 at 21:15





Thing is: if someone has physical access he/she can do -anything- by just rebooting into a live session. But they can not access the router if you keep the password for that safe.

– Rinzwind
Apr 4 at 21:15













@Rinzwind , physical - it is not important. Only local network

– n.osennij
Apr 5 at 7:06





@Rinzwind , physical - it is not important. Only local network

– n.osennij
Apr 5 at 7:06













What are on about? "physical - it is not important" and "Only local network" are unrelated. This "It is necessary for my to keep all logs of visited sites." is only 100% reliable to do from the log of your router. All other methods you can work around your logging if you know what to do.

– Rinzwind
Apr 5 at 7:28





What are on about? "physical - it is not important" and "Only local network" are unrelated. This "It is necessary for my to keep all logs of visited sites." is only 100% reliable to do from the log of your router. All other methods you can work around your logging if you know what to do.

– Rinzwind
Apr 5 at 7:28










1 Answer
1






active

oldest

votes


















0














Setup a proxy server (squid, apache or nginx) and your loggin is generated automatically.



This is easy and good way. Also you can do this to cache, so bandwith need is reduced.



For setup for eg. squid in ubuntu server:



https://help.ubuntu.com/lts/serverguide/squid.html.en






share|improve this answer
























  • thansk! The main question is - do I need to configure something extra on client machines? Now the client machines are configured - ip address, subnet mask and ip address of the server. After installing the squid (using your link) need I to specify a proxy server on client machines?

    – n.osennij
    Apr 6 at 21:56













  • No. You can serve proxy server via dhcp, so no configuration on client side is not required.

    – Pasi Suominen
    Apr 6 at 22:06











  • By static configuration of the network you need to specify proxy in clients.

    – Pasi Suominen
    Apr 6 at 22:08











  • it is Transparent Proxy? But what about https? dhcp - we can't use it. every client matchine mast have static ip

    – n.osennij
    Apr 6 at 22:16













  • you see only https traffic, not contents. There is reason for S in HTTPS. And yes, squid is transparent proxy.

    – Pasi Suominen
    Apr 7 at 7:19














Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131282%2flogging-all-web-trafic%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Setup a proxy server (squid, apache or nginx) and your loggin is generated automatically.



This is easy and good way. Also you can do this to cache, so bandwith need is reduced.



For setup for eg. squid in ubuntu server:



https://help.ubuntu.com/lts/serverguide/squid.html.en






share|improve this answer
























  • thansk! The main question is - do I need to configure something extra on client machines? Now the client machines are configured - ip address, subnet mask and ip address of the server. After installing the squid (using your link) need I to specify a proxy server on client machines?

    – n.osennij
    Apr 6 at 21:56













  • No. You can serve proxy server via dhcp, so no configuration on client side is not required.

    – Pasi Suominen
    Apr 6 at 22:06











  • By static configuration of the network you need to specify proxy in clients.

    – Pasi Suominen
    Apr 6 at 22:08











  • it is Transparent Proxy? But what about https? dhcp - we can't use it. every client matchine mast have static ip

    – n.osennij
    Apr 6 at 22:16













  • you see only https traffic, not contents. There is reason for S in HTTPS. And yes, squid is transparent proxy.

    – Pasi Suominen
    Apr 7 at 7:19


















0














Setup a proxy server (squid, apache or nginx) and your loggin is generated automatically.



This is easy and good way. Also you can do this to cache, so bandwith need is reduced.



For setup for eg. squid in ubuntu server:



https://help.ubuntu.com/lts/serverguide/squid.html.en






share|improve this answer
























  • thansk! The main question is - do I need to configure something extra on client machines? Now the client machines are configured - ip address, subnet mask and ip address of the server. After installing the squid (using your link) need I to specify a proxy server on client machines?

    – n.osennij
    Apr 6 at 21:56













  • No. You can serve proxy server via dhcp, so no configuration on client side is not required.

    – Pasi Suominen
    Apr 6 at 22:06











  • By static configuration of the network you need to specify proxy in clients.

    – Pasi Suominen
    Apr 6 at 22:08











  • it is Transparent Proxy? But what about https? dhcp - we can't use it. every client matchine mast have static ip

    – n.osennij
    Apr 6 at 22:16













  • you see only https traffic, not contents. There is reason for S in HTTPS. And yes, squid is transparent proxy.

    – Pasi Suominen
    Apr 7 at 7:19
















0












0








0







Setup a proxy server (squid, apache or nginx) and your loggin is generated automatically.



This is easy and good way. Also you can do this to cache, so bandwith need is reduced.



For setup for eg. squid in ubuntu server:



https://help.ubuntu.com/lts/serverguide/squid.html.en






share|improve this answer













Setup a proxy server (squid, apache or nginx) and your loggin is generated automatically.



This is easy and good way. Also you can do this to cache, so bandwith need is reduced.



For setup for eg. squid in ubuntu server:



https://help.ubuntu.com/lts/serverguide/squid.html.en







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 6 at 20:26









Pasi SuominenPasi Suominen

54038




54038













  • thansk! The main question is - do I need to configure something extra on client machines? Now the client machines are configured - ip address, subnet mask and ip address of the server. After installing the squid (using your link) need I to specify a proxy server on client machines?

    – n.osennij
    Apr 6 at 21:56













  • No. You can serve proxy server via dhcp, so no configuration on client side is not required.

    – Pasi Suominen
    Apr 6 at 22:06











  • By static configuration of the network you need to specify proxy in clients.

    – Pasi Suominen
    Apr 6 at 22:08











  • it is Transparent Proxy? But what about https? dhcp - we can't use it. every client matchine mast have static ip

    – n.osennij
    Apr 6 at 22:16













  • you see only https traffic, not contents. There is reason for S in HTTPS. And yes, squid is transparent proxy.

    – Pasi Suominen
    Apr 7 at 7:19





















  • thansk! The main question is - do I need to configure something extra on client machines? Now the client machines are configured - ip address, subnet mask and ip address of the server. After installing the squid (using your link) need I to specify a proxy server on client machines?

    – n.osennij
    Apr 6 at 21:56













  • No. You can serve proxy server via dhcp, so no configuration on client side is not required.

    – Pasi Suominen
    Apr 6 at 22:06











  • By static configuration of the network you need to specify proxy in clients.

    – Pasi Suominen
    Apr 6 at 22:08











  • it is Transparent Proxy? But what about https? dhcp - we can't use it. every client matchine mast have static ip

    – n.osennij
    Apr 6 at 22:16













  • you see only https traffic, not contents. There is reason for S in HTTPS. And yes, squid is transparent proxy.

    – Pasi Suominen
    Apr 7 at 7:19



















thansk! The main question is - do I need to configure something extra on client machines? Now the client machines are configured - ip address, subnet mask and ip address of the server. After installing the squid (using your link) need I to specify a proxy server on client machines?

– n.osennij
Apr 6 at 21:56







thansk! The main question is - do I need to configure something extra on client machines? Now the client machines are configured - ip address, subnet mask and ip address of the server. After installing the squid (using your link) need I to specify a proxy server on client machines?

– n.osennij
Apr 6 at 21:56















No. You can serve proxy server via dhcp, so no configuration on client side is not required.

– Pasi Suominen
Apr 6 at 22:06





No. You can serve proxy server via dhcp, so no configuration on client side is not required.

– Pasi Suominen
Apr 6 at 22:06













By static configuration of the network you need to specify proxy in clients.

– Pasi Suominen
Apr 6 at 22:08





By static configuration of the network you need to specify proxy in clients.

– Pasi Suominen
Apr 6 at 22:08













it is Transparent Proxy? But what about https? dhcp - we can't use it. every client matchine mast have static ip

– n.osennij
Apr 6 at 22:16







it is Transparent Proxy? But what about https? dhcp - we can't use it. every client matchine mast have static ip

– n.osennij
Apr 6 at 22:16















you see only https traffic, not contents. There is reason for S in HTTPS. And yes, squid is transparent proxy.

– Pasi Suominen
Apr 7 at 7:19







you see only https traffic, not contents. There is reason for S in HTTPS. And yes, squid is transparent proxy.

– Pasi Suominen
Apr 7 at 7:19




















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131282%2flogging-all-web-trafic%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How did Captain America manage to do this?

迪纳利

南乌拉尔铁路局